← Back

Privacy

This page collects one thing: the email address you give the newsletter signup. Here is exactly what happens to it.

What we store

Your address, plus four things about the moment you gave it, in the same database row:

• the exact sentence you saw next to the button, in whichever language you saw it
• which of the two languages that was
• what you opted into, at the moment you told us
• the moment you clicked the confirmation link, blank until you do

Rows collected under the older, narrower promise (one email, when Canonry launched) carry two things more: the moment that one email was sent, so that it can never go out twice, and the moment you accepted the newsletter from it, if you did. The send is recorded against the row, not against your address, and asking to be removed deletes all of it together.

Who sees it

Your signup and its confirmation link both go out through Resend, on our own verified canonry.io domain, using a sending key that belongs to this site alone, not to the product. Resend is the only third party that ever sees your address.

What it is for

Occasional email about new Canonry features - that is the whole promise next to the button today, and it is what we record as the scope you agreed to.

This form used to promise something narrower: one email, when Canonry launched. If you signed up before it changed, your row was not quietly rewritten to say you agreed to more - it still records that original, narrower promise. What changes what your row says is you signing up again yourself, at which point you see this page's current copy before you do.

How to be removed

Email privacy@canonry.io with the address you signed up with and we delete the row. There is no self-service unsubscribe link on this site yet - a request by email is the whole process, and it removes the address, the consent record and the confirmation state together, since they are one row.

That is the whole of what this page collects. For how the product itself, accounts, campaign content, the AI providers behind it, handles data, see Canonry's own fuller privacy page: app.canonry.io/privacy. It covers a different thing - what happens once you have an account, not what happens when you type an email address in here.

This describes the newsletter exactly as `migrations/0001_waitlist_signup.sql`, `migrations/0002_waitlist_consent.sql`, `migrations/0003_launch_notification.sql`, `$lib/consent.ts` and `$lib/server/waitlist.ts` define it today. If that changes, this page changes with it.