What data we collect and keep
Plain answers about what Finchproof records, why, and what we deliberately leave out. As of October 26, 2026.
The short version
- We never sell data. Not yours, and not the data about visitors to your website. We don't use it for advertising, and we don't share it with anyone for their marketing.
- About you, we keep only what it takes to run your account.
- About visitors to your website, we keep what it takes to prove who collected your work: when they came, what they took, what they called themselves and where they came from.
- We leave out what evidence doesn't need: what people type into forms, cookies, logins, search terms, and the details of checkout, sign-in and account pages.
About you, the account holder
| What | Why |
|---|---|
| Your email, name or studio, website, what you make, and any note you send when you sign up | To review your sign-up and contact you |
| Your password, stored only as a scrambled one-way code | To sign you in. We can't see or recover your password. |
| The websites you connect: domain, where the site is hosted, and the code that proves you own it | To protect them |
| Your settings, including any license terms and contact you choose to publish, and any licensed AI partners you record (the company and dates only, never your deal's terms) | The features you switch on |
| For copyright registration help: author and claimant names, which works are yours, registration numbers | To group your works and remind you of deadlines |
| When you accept our Terms of Service: your email, which version you accepted, the Privacy Policy version shown with it, the time, and your network address. These records are never changed. | To show which terms you agreed to, and when |
| Problem reports you send: your message, the portal page you were on, and your email | To fix what went wrong and reply to you |
| Evidence packages you create | So you can download them again |
| A copy of each email we send you. One-time sign-in and password links are removed from the copy once it's sent. | To check emails arrive |
| For each failed sign-in to the portal: the time, and one-way fingerprints of the account and the network address (never the email or address itself), kept for a day | To slow down and notice password guessing |
| If you came from one of our Meta ads: the ad's click code and your browser's description, kept for 30 days | To tell Meta which ad led to a sign-up (see below) |
No payment details: we don't take payments yet. When we do, card details will go straight to the payment processor and never reach our servers.
About visitors to your website
Every visit to a protected website passes through Finchproof, and we record it. That's how we can show later who collected your work. For each visit we keep:
| What | Why it's needed |
|---|---|
| The date and time, and the page requested | What was taken, and when |
| The visitor's network (IP) address | To check that a visitor calling itself, say, GPTBot really comes from OpenAI's published addresses, and to spot scrapers pretending to be people |
| How the visitor describes itself (its browser or crawler name) | The name a crawler gives is what the evidence quotes |
| A short list of technical details: preferred language, accepted formats, the networks it came through, and crawlers' identity signatures | To tell automated programs apart, and trace one that hides behind another service |
| A fingerprint of what we sent back, an exact copy of any page, feed or image we marked, and one copy of each page and image as your site published it | So a marker found later can be shown on the exact page that carried it |
| Which visitor group received which markers | So a marker points back to one visit |
What we deliberately don't keep
- Anything typed into forms, including passwords and messages.
- Cookies and login headers. Other technical headers are noted by name only, without their contents.
- Checkout, sign-in, account and admin pages pass through untouched, and we record only which page it was, not the details in its address.
- Personal details in web addresses on other pages: values that look like emails, one-time links, tokens, order numbers or search terms are removed before anything is stored.
- Pages seen by people signed in to your site. A visitor whose browser carries a cookie your site gave out at sign-in gets your page unmarked, and we never copy it, so pages showing someone's own details never enter the record. To tell those cookies apart from the ones your site gives every visitor, we keep a one-way fingerprint (never the cookie itself) of each cookie your site hands to visitors who aren't signed in, and forget it after 7 days. Cookies that only count visits or remember a cookie-banner choice (such as Google Analytics) don't say anyone is signed in.
- A second copy. Our servers don't keep their own log of visits; the evidence record is the only one.
We can't reliably tell people from automated programs, so the same rules apply to every visitor. You're responsible for telling your own visitors, in your privacy notice, that a service records visits to protect your content.
About AI companies
To find your markers, we ask AI products questions and keep their answers, and we scan public web archives. This involves no personal data: we send page addresses and our own questions, never anything about your visitors.
How long we keep it
| What | How long |
|---|---|
| Visitor records and marked pages | As long as they may be needed as evidence. The record is sealed so nobody, including us, can quietly change or delete single entries; that's what makes it usable in court. We're setting a fixed retention period with our attorney and will publish it here. |
| Your account details | While your account is open. Ask us to close it at any time. |
| Failed sign-in counts | One day, stored only in scrambled form |
| Meta ad click codes | 30 days |
| Daily backups | 14 days |
| Server system logs (no visitor records) | 14 days |
How we keep it safe
- Everything travels over encrypted connections (HTTPS).
- Passwords are stored only as scrambled one-way codes, and we refuse passwords known from public data breaches.
- Sign-in, setup and reset links work once and expire, and repeated wrong passwords are slowed down.
- The portal runs no third-party code or trackers. Its only cookie keeps you signed in.
- Our server accepts administrator access only with a cryptographic key, never a password, and its data files are readable only by the Finchproof service.
- Each site owner sees only their own sites' records.
Who else handles it
Only companies that run part of the service for us, and only what they need:
| Who | What for | What they receive |
|---|---|---|
| Hetzner (servers in Ashburn, Virginia, USA) | Hosting and storage | Everything on this page, stored on our server |
| Postmark | Sending our emails | Your email address and the message |
| Google Workspace | Our email inbox | Emails you send us |
| OpenRouter and the AI companies it connects to | Our test questions | Page addresses and our questions; nothing about visitors |
| Have I Been Pwned | Checking for breached passwords | The first 5 characters of a scrambled code of your new password; never the password |
| Meta (only if you came from one of our Meta ads) | Knowing which ads bring sign-ups | When you sign up and when your first site is protected: the ad's click code and your browser's description. Never your email, name or website. finchproof.com runs no Meta code and sets no Meta cookie. |
| OpenTimestamps | Public timestamps for our records | Fingerprints only; nothing readable |
Evidence packages go wherever you send them: your attorney, a court, or anyone you choose. We disclose data otherwise only when the law requires it.
Questions
Email adam@finchproof.com. You can ask what we hold about you, or ask us to correct or delete it. Visitor records can't be edited one by one (see above), but we'll tell you what we hold and limit how it's used.