Your information, explained clearly.
What Oribisoft collects, what becomes public, and how to ask a question about your data.
Effective date:
Who operates Oribisoft
Oribisoft is an independent software discovery project built by Muhammad Rehan. This policy describes information handled through the Oribisoft website. Contact the founder through the channel on our Contact page for privacy questions or requests.
Information you provide
When you create or update an account, we handle your account email, authentication information, display name, username, and any optional bio, avatar, website, or social links you supply. Product submissions include the product name, website URL, tagline, description, category, images, pricing label if supplied, features, intended audiences, open-source information, repository and social links, and launch details. Messages you send to the founder may contain the details you choose to provide. Please do not submit confidential information.
Authentication and account information
Supabase Auth handles email/password authentication, supported Google sign-in, and sessions. Google sign-in can provide basic account information used to initialize your profile. We use account information to identify you, maintain your session, protect access, and connect you to your products and votes. Your account email is not a public maker-profile field.
Public profiles and listings
Your maker username, display name, optional bio, avatar, website, and social links can appear on your public maker page. Published products, supplied media, maker attribution, website links, vote totals, and weekly results are public. Public information may be accessed, indexed, cached, or copied by third parties. Private draft details and review feedback are restricted to the owner and authorized moderators. Choosing Save & Get Badge enables a limited public prelaunch page showing the product name, tagline, and expected launch week. This page is separate from a published listing and is marked noindex; that is not a confidentiality control.
Website auto-fill and imported images
When you request website auto-fill, our server fetches the submitted public website and may fetch a same-site pricing page to suggest product details. You review the suggestions before saving. Selecting an imported image requests that image through our server for validation; accepted images can then be uploaded to Supabase Storage when you save. These requests reach the website or image host, which may keep its own request logs. We do not send your account credentials or session cookies with those outbound fetches. Account-linked request counters help enforce auto-fill and image-import rate limits. Auto-fill does not automatically publish or schedule a product.
Votes, launches, and verification
We store account-linked voting records to enforce one active vote per account per launch and to calculate totals. Weekly voting records and finalized results are kept separately from ongoing lifetime votes. Launch schedules, moderation state, and website-bound badge verification status support the launch rules. A manual verification request fetches the submitted website’s HTML to check the eligible badge and records the result. We do not publish private account details as part of these checks.
Product analytics
When collection is enabled, first-party analytics measure product-page views and website-button clicks. They use a random browser identifier that expires at the next UTC midnight, daily keyed hashes for duplicate suppression and rate limits, and broad referral categories. Product analytics do not store raw IP addresses, account identifiers, browser fingerprints, or full referral URLs. A network address may be processed transiently to produce a daily rate-limit hash. Makers see private aggregate reports for their own products, not individual visitor identities. Provider request logs are separate.
Cookies and browser preferences
Supabase session cookies support sign-in and session refresh. Optional product analytics use a daily first-party identifier cookie and a browser opt-out preference cookie lasting one year. Do Not Track, Global Privacy Control, or opting out disables product analytics collection. The controls below manage this preference for the current browser; allowing analytics does not override browser privacy signals. Blocking session cookies can prevent account features from working.
Service providers and hosting
Supabase provides authentication, database, and file storage. Vercel hosts the application and may process technical request information, such as network addresses, browser details, timestamps, and errors, to deliver and protect the service. Product images and avatars use Supabase Storage; approved public content and its media are intended to be accessible publicly. These providers process information under their own service arrangements and privacy practices. Information may also be disclosed where legally required or reasonably needed to address fraud, abuse, or security issues.
Email and other communications
Any account or security email sent under the authentication provider’s configuration uses your account email. The current application does not provide a password-reset flow, a support form, or a newsletter subscription. Contact through X is handled by X under its own privacy policy. Do not send sensitive account information in a public post.
Retention
Account and product information is retained to operate accounts, listings, launch history, moderation, and security. We do not promise a fixed deletion schedule for these records. Product analytics duplicate-suppression and rate-limit hashes are designed to be retained for at most 48 hours; anonymous daily aggregates, visitor bitmaps, and broad referral categories are retained separately. Provider logs and backups can follow separate retention arrangements. Finalized weekly results are designed to preserve competition history.
Your choices and deletion requests
You can edit the available public profile fields in Settings, manage eligible product content in My products, and use the browser analytics controls below. For access, correction, deletion, or an account-closure request, contact the founder. Requests may require identity verification. We assess them under applicable law and operational requirements; some information may need to remain for security, legal obligations, backups, or competition integrity. There is no automated account-deletion flow or guaranteed completion period advertised here.
Security
The application uses server-side authorization and database access policies to restrict private information and product ownership actions. Avoid sharing credentials and notify the founder if you suspect unauthorized access. No website or storage system can promise complete security.
International processing
Supabase, Vercel, and other services you choose to use may process information in countries other than your own. Processing locations depend on the provider and the service involved. Contact the founder with questions about the providers used for your information or the locations where it may be processed.
Third-party websites
Product websites, maker links, Google sign-in, and social profiles are operated by third parties. Visiting or interacting with them is subject to their own terms and privacy practices. A listing or successful badge check is not a privacy or security endorsement.
Children’s privacy
Oribisoft is intended for makers and people discovering software, and is not directed at children. We do not knowingly seek personal information from children. If you believe a child has supplied personal information, contact the founder so it can be reviewed and addressed.
Changes and contact
We may update this policy as the service and its data practices change. The effective date appears above. For privacy questions or requests, use the founder contact on our Contact page. Your applicable rights depend on the laws and circumstances that apply to you.
Still have a question?
Get in touch with the person building Oribisoft.