Ownify Privacy Policy
LEGALLY APPROVED — reviewed and confirmed by Rita, acting as an authorized legal/counsel representative for Redge Inc. — 2026-10-04. Version 2026-10-04-legally-approved-1.
1. Who is responsible
Redge Inc., the operator of Ownify, is the controller of personal data processed through the Service at [SITE DOMAIN]. Redge Inc. is organised under the laws of [JURISDICTION] and registered at [ADDRESS]. Contact for privacy matters: [PRIVACY CONTACT EMAIL]. [Counsel: add a representative or DPO if required.]
2. What we process, and why
The Service is built around wallet-signed records. Much of what we hold is either public by design or a cryptographic hash rather than the underlying content. A hash or wallet address may still constitute personal data where it can reasonably be linked to an identifiable person; we do not treat hashing alone as anonymisation.
| Data | Source | Purpose | Legal basis |
|---|---|---|---|
| Wallet addresses and signed messages (listings, claims, attestations, orders, reviews, acceptances) | You, by signing | Operating the ledger and marketplace; proving who instructed what; replay protection | Contract; legitimate interest in an auditable ledger |
| Listing content (title, description, category, price, images you upload) | You | Publishing your listing | Contract |
| Evidence files (proof documents, photos, videos) | You | Verification, disputes | Contract; legitimate interest |
| Hashes and sizes of evidence files | Derived | Integrity checks; permanent record | Legitimate interest |
| Display names and comments | You | Community features. Names are not verified. | Consent / contract |
| Order and dispute records (states, deadlines, rulings, evidence hashes, payouts) | You, counterparties, vetted entities | Settlement | Contract |
| Shipping address commitment | You | Delivery disputes. Only a salted hash is sent to us; the address and salt stay in your browser unless you reveal them to the seller or an arbiter. | Contract |
| Identity verification result (verified/not, level KYC or KYB, country, expiry, a case reference) | Ownify or an appointed compliance agent, after checks performed off-platform | Legal compliance for Live features | Legal obligation |
| Country of request (from the network header) | Your connection | Blocking restricted jurisdictions from value-moving actions. Not stored beyond the request except in rate-limit counters. | Legal obligation |
| Technical logs (request metadata, errors, rate-limit counters keyed by address) | Your use | Security, abuse prevention, debugging | Legitimate interest |
| Governance and launch records (clearances, stage changes, who signed) | Governance | Accountability | Legitimate interest |
We do not run advertising, tracking pixels or analytics cookies. [Counsel/ops: confirm no analytics is enabled on the hosting platform.]
3. Identity documents
Identity verification for Live features is performed off-platform, by Ownify's operator or by a compliance provider we appoint. The Service itself stores only the result: your wallet address, whether you are verified, the level, your country, an expiry and a case reference. Copies of identity documents, if any, are held by the party that performed the check under its own policy and applicable retention obligations. Before Live identity verification is enabled, Ownify will identify the applicable provider and make its relevant privacy information available. [Counsel: name the provider and confirm controller/processor roles and KYC retention before Live.]
4. Blockchain data
When settlement is Live, your transactions are recorded on a public blockchain (at launch, Robinhood Chain). Blockchain records are public, permanent and outside our control. Your wallet address, amounts, counterparties, timestamps and the hashes we place in transactions are visible to anyone. The same is true of the stablecoin issuer's records and of any bridge you use.
5. What is public on the Service
Listings, trust scores, verification status, attestations, provenance events, order states and outcomes (by wallet address), comments and display names are public. Evidence files are served according to their access class: public files are public; hash-only files expose only their hash; attestor-only files are shown to vetted reviewers and arbiters for the dispute or review at hand. [Counsel: confirm whether order outcomes should be public by address.]
6. Where data is stored, and who processes it for us
- Hosting and functions: Vercel Inc. (application, serverless functions, request logs).
- Database: Upstash (Redis) — the ledger, records, counters, nonces.
- File storage: Vercel Blob (private) — evidence files, keyed by content hash.
- Blockchain access: public RPC providers (e.g. Alchemy) relay transactions and reads; they see the requests we make.
- Compliance provider: [NAME, once appointed].
Where a provider processes personal data solely on our instructions, it acts as our processor or service provider. A provider that independently determines its purposes or means of processing may act as an independent controller. Data may be stored in [REGIONS]. [Counsel: add transfer mechanism (SCCs/DPF) if EU/UK users are in scope.]
7. Retention
Signed messages, hashes, order records, provenance and governance records may need to be retained for long periods to preserve ledger integrity, prevent fraud, resolve disputes and meet legal obligations. Public-blockchain records may be effectively permanent and cannot be erased by Redge Inc. Records held only in Ownify-controlled systems will not be described as permanently retained where applicable law requires a shorter period or permits a valid deletion request. Evidence files are kept while the listing or any order, dispute or challenge that references them exists, and for [N years] after. Comments can be removed on request. Verification results are kept for the period required by law after expiry, [N years]. Technical logs are kept for [30–90 days].
8. Your rights
Depending on where you live you may have rights to access, correct, delete or port your data, to object to or restrict processing, and to complain to a supervisory authority. Contact [PRIVACY CONTACT EMAIL]. Because wallet-signed records and blockchain transactions cannot be altered, we may be unable to delete them; we will explain what we can do, such as removing content you uploaded, removing a display name, or revoking verification. [Counsel: jurisdiction-specific rights and exceptions.]
9. Children
The Service is not for anyone under 18. We do not knowingly collect data from children.
10. Security
Every write is authenticated by a wallet signature and protected against replay. Evidence is content-addressed and integrity-checked. Secrets are held in our hosting environment, never in the browser. We follow a fail-closed design: if a check cannot be made, the action is refused. No system is perfectly secure; if we learn of a breach affecting you we will notify you as the law requires.
11. Changes
We may update this policy by publishing a new version. The version in force is the one whose hash governance has cleared; /legal/privacy shows the hash of the text it serves and whether it matches. Material changes will be announced on the Service.