Privacy Policy
Last updated: [DATE]. Controller: [LEGAL ENTITY NAME], [ADDRESS]. Contact: [PRIVACY EMAIL].
What we store about account holders
- Account: name, email address, a salted scrypt hash of your password (never the password), when you accepted these terms, and whether your email is verified.
- Sessions: a hash of your session token and its expiry, kept in an HTTP-only cookie on your device. We use no advertising or analytics cookies.
- Works you register: the original image, audio or video file, the protected copy, fingerprints computed from it, the rights settings you chose and any labels you wrote. If you offer a work for AI-training licenses, its labels, title and your name are shown to AI services integrated with the registry, and the file is delivered to those that buy a license.
- Your activity: a signed audit trail of actions on each asset, the notices and license offers you create, and ownership evidence you submit.
What is public
Each asset has a public provenance record showing your name as registrant, the registration time, the image fingerprints and your rights settings. It contains a hash of your email address, not the address itself. Anyone can upload a file to the Identify page to see whether it matches a registered asset; a match shows the asset title and registrant name. If you turn on open licensing for an asset, its public page also shows your listed prices. The controlled image URL is public unless you restrict it.
What we store about other people
- Detected and reported uses: the public web address where a matching file was found or that a registrant reported, the page title, a copy of the matching file (or the examined part of it) and page as evidence, and a contact email address if one was published on that page.
- People who request a license: the name, email and intended use they enter on a work's public page.
- Notice recipients: the email address a notice was sent to and the notice text.
- People who dispute a notice: the name, email, explanation and evidence link they choose to give.
- Licensees: the payer email returned by the payment processor.
- Identify lookups: the uploaded file is compared and then deleted; it is not kept.
Who we share data with
Platforms and AI services that integrate with the registry send it files to check and receive the matching work's title, registrant name and permissions; they may report back the address where a work appeared. Otherwise, only the providers the operator has enabled: [PAYMENT PROCESSOR] for license payments; [EMAIL PROVIDER] to deliver notices and account email; [REVERSE IMAGE SEARCH PROVIDER], which receives the protected copy of an image to search for matches; [HOSTING / STORAGE PROVIDER]; and public domain-registration (RDAP) services, which receive a website's hostname when you look up its abuse contact. We do not sell personal data.
How long we keep it
Account and asset data is kept until you delete the asset or your account, which removes the files, evidence, notices and audit trail for those assets. Expired sessions and used sign-in links are purged automatically. [BACKUP RETENTION PERIOD.]
Your choices
You can delete any asset or your whole account from the app. To access, correct or export your data, or to object to processing, contact [PRIVACY EMAIL]. If you received a notice and want your details removed, use the same address. [RIGHTS UNDER GDPR / CCPA AND HOW TO COMPLAIN TO A REGULATOR — to be completed by counsel.]
Security
Passwords are hashed, session tokens are stored only as hashes, state-changing requests are restricted to this site's origin, sign-in is rate limited, and the registry signing key can be encrypted at rest. No system is perfectly secure; we will notify affected users of a breach as the law requires.