Privacy

In short

In short: we store what it takes to send you the newsletters you asked for and to make the ones you make; we count visits without cookies and without storing an IP address.

What we store: your account, or a guest account while you try making a newsletter; the newsletters you make and what producing them takes; what you subscribe to and what was sent; visits to our public pages; the request log; and any mistake report you send.

What we do not store: no advertising profile, no IP address in the record of a visit. No card and no payment details. We do not sell, rent or trade your address.

Who else gets any of it: the companies named below.

How long we keep it: a visit goes after 90 days, the request log after 14 days, an unconfirmed address after 48 hours, and a guest account goes 30 days after it was last used. Everything else stays until you ask us to delete it.

Where to write: [email protected].

When you read a public page

In short: no cookie unless you choose our new design, no IP address in the record of a visit, nothing from another company; the server in front of the site keeps a request log for 14 days.

A public page sets no cookie, and nothing loads from any other company. While we test a new design, a link can switch you to it. If you open it, one cookie holds only which design to show, for a year.

The record of a visit holds no IP address: which page, when, which newsletter, issue or story, where the visitor came from and whether you came from the Share link in our mail. Visitors are told apart by a code remade every day; nobody is followed from one day to the next.

The same visit is also sent to PostHog: a page, a press, a turn of the chat on the Inspiration page, a step of signing up, of subscribing or of starting a newsletter, a sign-in, your answer about mail from Kurzia, a newsletter going live or changing who may read it. A page also notes which design of the site you were shown. Never your address, and nothing you typed except the chat's own short draft of the newsletter you asked it for. If you make an account that day, from the same browser and connection, that day's id is joined to your account. We hold that to see which pages bring readers, on our legitimate interest.

If you press Start or Start this newsletter without an account, PostHog names you from then on by your guest account's id, joined to that day's id and later to your account. If you never make an account, those events stay in PostHog under an id that names nobody; our purge does not reach them. We send a guest's events to see where starting a newsletter goes wrong, on the same ground.

The server in front of the site logs every request: the full IP address, the page, the time and what your browser sends, without cookies, passwords or sign-in codes. We keep it for 14 days at most, to keep the site secure and stop abuse, on our legitimate interest; only the operator can read it.

To stop one place sending too many requests, the server counts them for an hour or a day under a code made from your IP address; the count holds no address.

If you report a mistake in an issue, we keep the issue, the story you chose, what you wrote and when, on our legitimate interest in correcting what we publish. Not your email address, not your account and not your IP address.

When you subscribe

In short: your address, your choices and what was sent to you, held on your consent, which the unsubscribe link in any issue withdraws.

Until you confirm, the address you give is held apart from the accounts, with your choices, so an address nobody stood behind never becomes an account.

Once you have confirmed, we store the subscription: which newsletter, the hour and the weekday you chose, the secret in your unsubscribe link, and where it came from. We hold it on your consent, given by pressing a button on the confirmation page, and withdrawn by the unsubscribe link in any issue.

When you confirm a subscription, or put a newsletter of yours live, we ask whether Kurzia may write to you beyond your newsletters, unless you have answered before. Either answer goes through. We keep your answer, the words you were shown, where and when you answered, and every later change. We hold it on your consent.

We store the record of each delivery: which issue went to which subscription, when, and what the mail provider reported back afterwards, which includes your address; and which mails welcomed you, and when. If you mark an issue as spam, you are unsubscribed. If your address refuses our mail, your subscription is paused. We hold these records on our legitimate interest in finding failures.

When you create an account

In short: your name and address, your sign-ins and one session cookie, held to give you the account you asked for.

Your account holds your name, your email address, a picture link if you add one, and whether it is an admin. A password, if you set one, is stored in a form that cannot be turned back into what you typed. If you choose Continue with Google, Google tells us your name, your email address and your Google account's id, and we keep nothing else it sends. We do not see your Google password.

Each sign-in: when it started, when it expires, the IP address it came from and the browser it used. A sign-in link or an address confirmation: the address it was sent to, and a code that works once. A share link you make is kept with your account.

Signing in sets one session cookie, and so does pressing Start or Start this newsletter without an account. An admin's sign-in sets a second. Choosing our new design adds one more.

We hold the account on the contract between us, and the sign-in records on our legitimate interest in finding failures. If we block an account, it keeps when and why, on our legitimate interest in keeping the service from being misused.

One admin can read the whole database. Every action they take on an account, a subscription, a delivery, a run or a newsletter is written down with who took it and why.

While an admin helps you by viewing the service as your account, their browser holds a few more cookies; each such view is recorded with the reason.

When you make a newsletter

In short: the newsletter, its brief, sources, runs, issues and the conversations that steer it, held because producing it takes them, never used to train a model.

Press Try it now, answer the first question and press Start, or press Start this newsletter on a newsletter we suggest. Either press makes you a guest account and sets a session cookie, which the service you asked for needs. When the interview has written what your newsletter will be about, we ask you to make an account. The sign-in link we mail you names the newsletter and the guest account, nothing of yours, and lasts two hours. A guest account and everything under it is deleted 30 days after it was last used. A newsletter that moved to your account stays.

A newsletter you made: its name, its address on the site, your author blurb and strapline; its brief, the standing instruction the writer works from, kept as versions rather than overwritten; its schedule; and any sponsor's slot in it.

Before a brief is saved, a model call checks that it does not target a person or pose as a brand's own. A brief the check refuses, or cannot answer for, is not saved. It is written to the service's own log, so a person can look at it.

Its sources, their weight and every rating or ban, with the reason. Its runs, with what each source returned. Its issues: the subject, the text as sent, the stories in it, the links they cite and a note each time one was rewritten to keep it in our own words. Its research: what it reads, how much each way of reading found and how much of it was used, the searches run for it each night with what they returned, the rules learned for it, the gaps you told us about, and what each issue measured about itself.

The interview that started it and the conversations that steer it: every message you and the agent wrote, each change the agent proposed and whether you approved it, and which step the interview reached. Each model call it caused: the model, the cost and the call's id; not the prompt, not the answer.

We hold all of it on the contract between us: producing the newsletter you asked for takes it. We do not use your brief or your conversation to train a model.

Before a newsletter you made can be read by anyone else, we look at it. We keep when you last asked, who approved it and when, what was approved and, if we refused, the reason we gave you. We hold that on our legitimate interest in showing later how it was decided.

Companies that process the data

In short: each is given only what its job takes, and keeps its copy under its own terms.

Resend, in the United States, sends every mail and reports back what became of it. It is given the address, the subject and the message.

Turso holds the database, on AWS in eu-west-1, Ireland: everything we store ourselves.

PostHog, in its European Union region, eu.i.posthog.com, is given the events above, each naming an account id, a guest account's id or, for a visitor who has not signed in, an id that changes every day; never your IP address or your email address: any event with an @ anywhere in it is dropped before it is sent.

Anthropic and OpenRouter, both in the United States, run the models that research and write the issues, given the newsletter's brief, what its sources published and what you wrote in an interview, a steering conversation or the chat on the Inspiration page.

Brave, in the United States, runs most of the searches an issue is built from, given the search text built from the newsletter's brief. Brave keeps a query for up to 90 days as its own, not as something it handles for us.

Exa, in the United States, runs some of the searches that look for new sources for a newsletter, given the search text built from the newsletter's brief.

Algolia, in the United States, runs the Hacker News searches, given keywords taken from the newsletter's brief.

Cloudflare, in the United States, stands in front of the site and forwards mail sent to [email protected]. It sees every request on its way to us.

Sentry, in its European Union region (ingest.de.sentry.io), holds the errors the service runs into, with your account id when you are signed in. It is never given your IP address, and email addresses are removed before anything is sent. We do not send it what you write: not a brief, not a conversation, not a report of a mistake. A newsletter's name is on some of its records. So is a source's website name or a picture address you gave. And when sending something fails, the error we record can quote part of what was being sent. Sentry loads nothing in your browser.

Google, in the United States, signs you in if you choose Continue with Google, giving us your name, your email address and your Google account's id. Google Workspace, run by Google, receives the operator's mail: a request to look at a newsletter, with the author's name and address, and a mistake report, with what the reader wrote.

Hetzner rents us the server the site runs on, in Helsinki, Finland. It holds the running service and the request log, not the database.

Nobody else is given anything.

How long it is kept

In short: visits, unconfirmed addresses, guest accounts and the request log go by themselves; everything else stays until you ask.

Four things are deleted by a purge that runs once a day: a page visit older than 90 days; an address that never confirmed, within about a day and an hour of its 48 hours being up, and every confirmation mail we sent to that address is deleted with it; a guest account 30 days after it was last used; and the count of chat turns and newsletter starts from one place, once its day is over. A confirmation that was used is deleted a week after it was used. The request log drops anything older than 14 days by itself.

Nothing else is deleted on a schedule.

If you ask us to delete your data, we delete your account and your sign-ins, your subscriptions and the delivery records under them, the newsletters you made, and every answer to mail from Kurzia given for your address. If your account was blocked, the block goes with it. The record of what an admin did, and why, is kept even then. Issues already mailed stay in the inboxes they were sent to.

A newsletter you made comes down within seven days of your request. If other people read it, it is deleted only after we have taken those readers off it, and until then we cannot delete your account.

To have a mistake report deleted, tell us the issue and what you wrote; it holds nothing that says who sent it.

Your rights and contact

In short: one address for everything, an answer within a month, and Datatilsynet if you think we have this wrong.

Kurzia is run by Usenestor.com ApS, CVR 45225240, Søstien 1, 3460 Birkerød, Denmark, the data controller for everything on this page.

You can ask to see what is held about you, to have it corrected or deleted, to get it in a file you can take elsewhere, to have us pause using it while something is in dispute, and to object to the uses that rest on our legitimate interest.

Where a use rests on your consent, you can withdraw it whenever you like: the newsletters, with the unsubscribe link in any issue; mail from Kurzia itself, with its stop link or by writing to us. When you write, we record your no as your answer, with the date, and it stays your answer until you give a new one yourself.

Write to [email protected]; there is no separate privacy address. We answer within one month.

If you think we have this wrong, you can complain to Datatilsynet, the Danish Data Protection Agency, or to the supervisory authority of the country you live in.

Changes appear here, with the date it was last updated at the top; we do not mail a notice. The terms are at /terms.