Privacy
Privacy Policy
This policy describes the information ORYNT processes, why it is used, and the choices available to you.
Effective October 15, 20261. Information we collect
When you sign in with GitHub, we receive account information needed for authentication, such as your stable GitHub user ID, username, display name, avatar, and email when GitHub provides one. We store your ORYNT profile, submitted listing details, discoverer attribution, verified repository-management relationships, ownership-verification challenge records, votes, bookmarks, comments, replies, collections and creator notes, reports, feature suggestions, grouped notification read status, membership status, basic security or operational logs, and the versions and time of your legal acceptance.
2. Public repository information
For submissions, search, synchronization, and ownership checks, ORYNT retrieves public GitHub metadata including repository and owner identifiers, repository name, description, URL, default branch, topics, language, license identifier, star and fork counts, issue count, update dates, and archived or fork status. ORYNT may store a limited, sanitized plain-text excerpt from a public README to improve discovery. It does not store complete README HTML, repository source, or source archives. For organization claims, ORYNT checks whether the signed-in GitHub user has an active organization-owner role before checking the temporary public verification file. ORYNT does not request access to private repositories.
3. Billing information
Polar processes checkout, payment methods, invoices, tax information, and billing portal activity. ORYNT receives identifiers and subscription details needed to provide access, such as plan, status, billing interval, amount, currency, renewal period, and founding-discount status. ORYNT does not store full payment-card numbers.
4. How information is used
We use information to authenticate users; distinguish community submitters from verified repository managers; match personal repositories to their GitHub owners; process ownership claims; publish and search listings; provide votes, bookmarks, collections, member discussions, replies, and grouped repository notifications; count collection views and saves; review reports and feature suggestions; manage memberships; prevent abuse; troubleshoot the service; understand product performance; and comply with legal obligations.
5. Service providers and disclosures
ORYNT uses Supabase for authentication and database services, GitHub for identity and public repository metadata, and Polar for billing. Information is shared with these providers only as needed to operate the service. We may also disclose information when required by law, to protect rights and safety, or as part of a business transfer subject to appropriate safeguards.
6. Public information
Approved repository listings, their descriptions, categories, keywords, languages, vote totals, community-submission status, discoverer username, and linked GitHub identities may be visible publicly. A published collection exposes its title, description, repository list, creator notes, creator identity, and aggregate view and save counts until the owner unpublishes it. Discussion comments, replies, author usernames, repository-owner badges, and owner-pinned status are visible to paid members. Ownership-challenge tokens, private collections, individual vote choices, notification read status, reporter identities, and private owner responses are not included in public responses.
7. Retention
We retain account and service data while your account is active and as reasonably needed for the purposes described here. Security, billing, moderation, repository-management, attribution, ownership-claim, and webhook records may be retained longer for fraud prevention, accounting, dispute resolution, continuity of listings, or legal compliance. Removed or unlisted repositories may leave limited audit, attribution, management, activity, or backup records for a reasonable period.
8. Security and international processing
We use access controls, row-level database security, server-side authorization, and signed billing webhooks to protect data. No system is completely secure. Our providers may process information in countries other than your own, subject to their contractual and legal safeguards.
9. Your choices and rights
If you are a verified repository manager, you can edit, refresh, or unlist that repository’s ORYNT listing. Community submission alone does not provide those management rights. You can remove bookmarks, manage billing, cancel membership, and sign out from your account. Depending on your location, you may have rights to access, correct, delete, restrict, or export personal information and to object to certain processing. We may need to verify your identity before responding.
10. Cookies, updates, and contact
ORYNT uses essential authentication cookies required to keep you signed in and protect requests. Details are available in our Cookie Policy. Optional advertising and analytics cookies are not currently part of the service. We may update this policy as ORYNT develops and will revise the effective date when changes are material. For privacy requests, contact the ORYNT operator through the support contact shown in your account, Polar purchase receipt, or the product’s published support channel.