Privacy
Last changed 15 November 2026.
The short version
- Your ledger, your client codes and your session records stay in your browser on your device. They are never sent to us or to anyone else.
- There is no account, no analytics script, no advertising and no tracking on this site.
- If you buy a license, we store five things about the sale: your email address, your license number, a Stripe event number, and two times. Nothing else.
Using the site and the app
The app is a page of code that runs in your browser. Everything you enter is saved in that browser's own storage on your device. No part of it is uploaded. We have no copy and cannot see it. The pages are built so that they cannot connect to any other server: the site's security policy blocks outgoing connections, and an automated test checks it.
We do not set cookies and we do not run analytics. We keep no log of who visits.
The site is hosted by Cloudflare. Like any web host, Cloudflare handles each request for a page, which includes your IP address and browser details, in order to deliver the page and protect the site from abuse. Cloudflare shows us totals only, such as how many requests were served. Cloudflare's own privacy policy covers that handling.
The ledger sits in your browser in readable form. It is protected by your computer's login and disk encryption, not by us. Backup files are encrypted when you give them a passphrase.
If you buy a license
Payment happens on Stripe's own checkout page. Stripe collects your email address and your payment details and handles them under Stripe's privacy policy. We never see or store your card number.
When your payment succeeds, Stripe sends our server a notice. Our server then creates your license key and emails it to you. It stores one row for the sale, with exactly these fields:
| What | Why |
|---|---|
| Your email address, as you gave it at checkout | To send your key, and to send it again if you ask |
| Your license number (for example CC-AB2CD3EF4G) | To identify your license when you write to support |
| The Stripe event number for the payment notice | So the same payment can never produce two licenses |
| The time the license was issued | It sets the date your included updates run to |
| The time the email was handed over for delivery | So a failed delivery is tried again |
Our server does not store your name, your address, your card details or anything from your ledger. Stripe keeps its own record of the payment, which we can see in our Stripe account, as any seller can.
The license email is delivered by Resend, an email delivery service. Resend handles your email address and the message, which contains your key, in order to deliver it. The email has no tracking: we do not record whether you open it or click anything in it.
The license key itself is checked in your browser. Using it sends nothing to us, so we cannot tell where or how often a key is used.
Writing to support
Mail to support@canarycopy.com is forwarded to a mailbox that a person reads. We keep your message for as long as it takes to deal with it and to keep a record of what we told you. Please do not send client names, client codes or session details. We never need them.
Who else handles data
- Cloudflare hosts the site, runs the server that issues licenses, stores the sale rows described above, and forwards support mail.
- Stripe takes payments.
- Resend delivers the license email.
We do not sell or rent anything, and we share nothing with anyone else.
How long we keep it, and deleting it
We keep a sale row for as long as Canary Copy is offered, so that we can re-send a lost key. Write to support@canarycopy.com from the address you bought with and we will tell you what we hold, or delete it. Once it is deleted we can no longer look up or re-send your key, so keep the email it came in.
Health information
Canary Copy never receives your ledger, so we do not hold protected health information for you. A client code together with a date of service can still be health information on your own device. Use codes instead of names, and keep your device encrypted and locked.
Changes
If what we store changes, this page changes first, with a new date at the top.