We build tools for protecting your rights — so we try hard not to collect your data in the first place. Most of what our tools do happens locally, in your browser.
Last updated: September 3, 2026
The short version: we only receive personal data you deliberately give us (a waitlist email, a scan query, a verification document, or a work you register with us for review). Document generation and file fingerprinting happen entirely in your browser. We don't run advertising trackers, we don't sell data, and our analytics are cookie-free.
ChapterIP ("we", "us") operates chapterip.com, enterprise infrastructure for licensing creative works, location, and image & likeness in the AI age. For anything in this policy, contact info@chapterIP.com.
When you join the waitlist or submit a form, the details you enter (typically your name and email) are delivered to us by Formspree, our form processor. Forms are protected by hCaptcha, which processes limited technical data to tell humans from bots. We use your submission to respond to you and to tell you about ChapterIP tools and pilots; we don't share it beyond the processors named here.
The One Form runs in your browser. Files you attach as work specimens are fingerprinted (SHA-256) locally on your device — the file itself is never uploaded to us; only the fingerprint is embedded in the documents the tool generates for you. Typed or pasted work text is fingerprinted the same way and is not saved to your device's storage. Your form progress is kept in your browser's local storage so you can pick up where you left off; clearing your browser data removes it.
When you run a scan, the name (and optional photo) you provide is sent to our server, which queries public search services on your behalf — DuckDuckGo, and where needed Serper, Tavily, and Google Cloud Vision for reverse image search. We do not store your scan queries or uploaded photos; they are processed transiently to produce your results. The scan endpoint accepts requests only from our own site.
To verify an address at building level, the address you enter is sent to public geocoding services (OpenStreetMap Nominatim, the US Census Bureau geocoder, postcodes.io, and Photon). If you submit an ownership document (deed, utility bill, or similar), it is delivered to our review inbox via Formspree, reviewed manually by our team, and used only for that verification. The emailed one-time-code option, when active, sends a code to the email you provide via our email provider and stores nothing server-side.
When you register a written work, likeness, or location, the files you upload and the details you type (title, description, licensing preferences, and for locations an address) are stored in our submissions store on Cloudflare (R2 object storage), together with a SHA-256 fingerprint of each file that we recompute on our own servers. Every registration is reviewed by a member of our team before anything is published. You receive a receipt code, and, if you give us an email address, a receipt email sent through Resend; decisions and occasional reminders about your registrations arrive the same way. Quick Drop registrations can be made without signing in — the receipt code is then the only key to that record, so keep it.
Originality screening. Written works are compared with previously registered works and with public-domain texts using content fingerprints (hashes of short word sequences), not by sharing your text. A small sample of short, distinctive phrases may be searched on the public web through Serper or Tavily to find already-published copies. Where enabled, passages and rendered page images are processed by Cloudflare Workers AI, on Cloudflare's infrastructure, for paraphrase detection and text recognition. Results are shown to you as counts and verdicts; other creators' works are never identified to you, and yours are never identified to them.
Photos. Photos in likeness and location registrations are sent to Google Cloud Vision, which returns two things: whether copies of the photo already appear on the public web, and content signals our reviewers use — whether a face is present and how many, safe-search ratings, descriptive labels, and dominant colours. We keep those signals as counts and ratings only; no facial geometry from this check is retained. They are prompts for a human reviewer, never automatic decisions.
Face registry (likeness registrations). When our team approves a likeness registration, the faces in its photos are enrolled in a private face registry we operate on Amazon Web Services (Amazon Rekognition). The registry exists for one purpose: to tell whether a face submitted later already sits in it under another registration, which is how we detect duplicate or impersonating registrations. It is not identity verification, it is never searched against any external database, and it is never used to identify people in third-party content. Face templates are deleted from the registry when a registration is withdrawn or an approval is revised. Because face templates are biometric data under some laws, by submitting a likeness registration you consent to this enrollment; you can withdraw that consent and have the template removed at any time by contacting us.
Location addresses. Addresses are verified with the geocoding services described under Location verification and compared with previously registered addresses to detect the same property being registered twice.
Staff and creator sign-in uses Google Sign-In. We receive your verified email address and profile name from Google and keep a short-lived session cookie (12 hours) on your device. Your email links you to your registrations and is where receipts and decisions are sent; it is never shown to other users. In Studio you choose a permanent handle and a display name, which are the public identity other creators see. Messages you post in community channels and direct messages are stored so participants can read them, and older messages roll off as channels fill.
The territory hint on the registration form comes from Cloudflare's estimate of your country. It is advisory, never stored, and never used to block anything.
Videos you process with SplatBack are reconstructed entirely in your browser — the footage never leaves your device. The embeddable viewer and scene composer load 3D files from URLs their owners host; we store none of that content.
We use Cloudflare Web Analytics, which is cookie-free and does not track you across sites. We set no advertising or tracking cookies. Your dark/light theme preference is stored in your browser's local storage, on your device only. hCaptcha may set its own cookies on pages with protected forms, strictly for bot detection.
The site is served by Cloudflare, which processes IP addresses and technical request data to deliver and protect the site. All traffic is encrypted (HTTPS, with HSTS). Security researchers can reach us via security.txt.
Where GDPR or similar laws apply: we process form submissions and verification documents on the basis of consent (you chose to submit them); we process registrations, their screening results, and account data on the basis of contract (providing the registration and review service you asked for); we process face templates in the face registry on the basis of your explicit consent, given when you submit a likeness registration and withdrawable at any time; we process technical request data on the basis of legitimate interest in operating and securing the site.
Form submissions are retained for as long as needed to respond to you and operate the waitlist. Verification documents are used for the review and not kept longer than needed for it. Scan queries and SplatBack footage are not stored at all. Registered works, their fingerprints, screening results, and review decisions are kept while the registration is active, because the record is what evidences your provenance claim; withdraw a registration and its files, and any face templates enrolled from it, are deleted. Community messages are capped per channel and older ones roll off. Emails we send you are delivered through Resend and are not kept by us beyond the provider's delivery logs.
You can ask us at any time what data we hold about you, ask us to correct it, or ask us to delete it — email info@chapterIP.com and we'll act on it. If you're in the EU/EEA or UK, you also have the right to lodge a complaint with your supervisory authority.
Our processors (Cloudflare, Formspree, hCaptcha, Google, Amazon Web Services, Resend, and the search providers) are primarily US-based and process data under their own published safeguards, linked above.
Our services are not directed at children under 16, and we don't knowingly collect their data.
If this policy changes materially, we'll update this page and the date at the top.