Who Owns Privacy

What this page covers

This summary describes information used by the current Who Owns application. Public browsing does not require an account. Founder account and payment actions use the information needed to provide those services.

Accounts and sign-in

When you use founder features, the authentication service processes your sign-in email, account identifier, and session information. The app uses these to sign you in, protect your founder pages, and associate your work with your account. Authentication session cookies are stored by your browser; public browsing does not need a founder session.

Founder and product information

Founder submissions can include product names, descriptions, website or demo links, category, country connection, review attestations, founder display details, and market-specific claim pitches. This information supports review, account pages, publication, and claim workflows.

Founder sign-in email, private review details, and contact fields are not shown publicly by default. Contact email or phone is public only when the founder provides it and enables the matching public-contact setting.

Public products, countries, and sharing

Approved and published products may show their public product information, selected media, category, founder display name, origin-country information, and market pitch. Country pages show the current platform holder, next displayed price, protection state, and public claim history. Product maps and share pages use the public product and claim information made available by the app.

Making a product private hides or masks identifying public information under the app's publication rules. Claim events remain in platform history; public visibility follows those rules. When you share a link to another service, that service receives information according to your action and its own privacy practices.

Payments

For a payment attempt, the app records transaction details such as the founder, product, country, amount, currency, payment status, and provider references needed to verify settlement or reconcile a refund. When a checkout is initialized, the founder email, amount, currency, and transaction reference are sent to Paystack. Payment processing may also involve the provider's own services.

The application database does not store full payment-card numbers. Do not send card details to support.

Service providers and technical information

The application uses Supabase for authentication and database-backed product and claim services, and Paystack for payment processing when enabled. Hosting and service providers may generate request, operational, or security logs. This project does not define a separate analytics profile or a fixed log-retention period; provider logging and retention depend on the deployed configuration.

Use and retention

Information is used to operate accounts, review and publish products, show public country positions, verify payments, prevent invalid claims, and help resolve support requests. The application does not publish a fixed retention schedule or provide a self-service account-deletion control. Historical claim records are retained as platform history.

Questions or requests

For a privacy question or a request about account or product information, visit Help. The available public contact details are shown there.