Privatliv
Last updated November 18, 2026. Written in plain language on purpose. “We”, “us” and “Author Beta” mean the operator of this website; “you” means anyone who uses it.
Our promises, in short
- We don’t sell your information. Not to advertisers, data brokers or anyone else.
- We don’t sell users. Readers aren’t a product we sell to authors, and authors aren’t a product we sell to anyone.
- We don’t share your information, except the minimum the few services that run the site need to do their job (listed below), or when the law makes us.
- No big tech, no tracking. Our pages load nothing from other companies: no ads, analytics, tracking pixels, social media widgets, outside fonts or outside scripts. Your browser enforces this with a security rule we send on every page that only allows our own website. Our site is delivered through Cloudflare (listed below): it passes our own pages and files to you on our behalf, it isn’t something extra your browser loads, and we use none of its analytics or tracking.
- Your book and your notes are encrypted in your browser. We can’t read them.
- No AI on private work. We never use manuscripts, notes, feedback, reviews or anything you write here to train or feed AI. No AI service reads your manuscript unless you choose Full AI for a Writing Desk book (see below). AI tools are optional, off until you turn them on, and never open your work by themselves: the AI Writing Assistant and the AI help in the blog, newsletter, marketing and Name Studio send only what you type or paste into their own box, after a preview showing exactly what will go and to which service; AI Artwork sends only the picture description you approve. Full AI is your choice: for one Writing Desk book at a time, and only with your own AI account, you can let the AI panel read the parts of that book you tick (such as the open chapter); each request is previewed and goes from our server to your AI service, which handles it under its own terms. Beta reads can never use it. We don’t store what you send or what comes back (only counts), and we don’t store generated pictures: each is held for 24 hours so you can download it or place it on a cover, then deleted. The private parts of the site (the reader, Dashboard, accounts, the API) are closed to every AI crawler and agent, and manuscripts and notes are encrypted. Public pages, such as author pages, book pages, published reviews and open beta listings, can be read by search engines and AI assistants like any public web page; our robots.txt asks them not to use those pages to train AI models.
What we keep
- Your handle, email address and password (stored as a one-way hash). We don’t ask for your real name.
- Your encryption key, locked with your password and with your recovery code. We can’t unlock it.
- For authors: your books and your readers’ feedback, encrypted in the browser so we can’t read them; book and chapter titles, word counts and beta settings, which aren’t encrypted.
- For readers: which betas you joined, your reading progress and ratings, and your notes and answers (encrypted so only you and the author can read them). Your reading progress is private. The one exception is a count: once at least 3 readers have finished a book, its author’s page can show how many readers finished it. It’s a number only, never names or handles. Your reader badge (how many betas you’ve joined and how many you completed, plus earned tags such as “Finisher”) is shown to the authors of rounds you join or wait to join, never with your email or the titles you read. It appears beside your published reviews only if you turn that on in your settings. Your badge record also sets your reader level, which we use automatically to send new-beta emails to higher levels a day earlier, to order waiting lists (higher levels first), and to let authors open a round only to readers of a chosen level. Authors still decide who reads their book.
- Things you choose to make public: author pages and book pages (pen name, photo, bio, links, covers, descriptions, series, store links), how you design them (theme, fonts, colours and images), beta listings, and reviews. Public things aren’t encrypted, because they’re meant to be seen, including by search engines and AI assistants.
- Images you upload (covers, photos, page images): we resize them and save them in an efficient format (WebP), which also removes hidden details stored inside photos, such as the camera used and the GPS location where it was taken. We keep only the cleaned copy.
- If you ask to be told when the paid plans open: that you asked, and when, so we can send you that one email.
- Basic security records: sign-in times, and which chapters were opened from which device, kept for 30 days. IP addresses are stored only as scrambled codes.
- Your signed-in devices and security activity (sign-ins, password and two-step changes): the browser and system (like “Chrome on Windows”) and a shortened address (like 203.0.113.x), so you can spot anything you don’t recognise and sign it out in Settings → Security. Kept for a year.
- If you turn on two-step sign-in: the key shared with your authenticator app, encrypted, and your backup codes, stored only as one-way hashes. Your app works out the codes on your phone; no one else is involved.
- If our emails to you bounce or you mark them as spam: your address and the reason, so we stop writing to it until you ask us to try again.
- A record of what the site owner does in the owner console (for example refunds, takedowns, name decisions and account changes), so every decision can be checked later.
- Payment records: what you bought and when, any refund, the time you ticked the box to start straight away, and the billing country Stripe tells us (only so we can apply the right to withdraw in the EU, EEA and UK). Card details stay with our payment processor; we never see them.
Who handles data for us
Only these services, and only for the purpose named:
| Tjeneste | What it does | What it gets |
|---|---|---|
| Our web host (Verpex) | Runs the server and database | The site’s stored data, including the encrypted books and notes it can’t read |
| Cloudflare | Delivers the site quickly and protects it from attacks. Every visit passes through it on the way to our server | Your IP address and the pages and files you request, as they pass through. Your books and notes stay encrypted, so Cloudflare can’t read them. We use no Cloudflare analytics, tracking or scripts |
| Buffer | Optional automatic posting, only if you connect your own Buffer account in Marketing | Only the posts you approve and send: their words, picture and time. Never your manuscript, your readers or your email address. Buffer’s own terms cover your Buffer account |
| Groq, Cloudflare Workers AI, OpenAI or Anthropic | Optional AI writing help, only if you turn AI on for your account and choose to send something. Free Layer uses our connection; My API uses your own account with that service | Only the text you typed or pasted into an AI box and approved in its preview, with the instruction for the task. Never your manuscript, subscribers or account details. Each service handles it under its own terms, linked in every preview. We keep only counts |
| Pixabay, Art Institute of Chicago, The Met, NASA, ambientCG (Image Library) | Free pictures for covers, searched from inside Cover Studio | Only the search words you type. Searches and downloads go from our server, so these services never see your address or account. The picture you choose is held on our server for 24 hours while your browser copies it into your encrypted project |
| SendFox (author newsletters) | Holds each author’s subscriber list and sends their newsletters, only if you subscribe to an author’s news and confirm | Your email address, the author’s list you joined, and the newsletters sent to you. We keep only a scrambled fingerprint of your address and a record of when and where you agreed; the author never sees your address |
| Bluesky or your Mastodon server | Optional automatic posting, only if you connect your own account in Marketing | Only the posts you approve and send: their words and picture. Never your manuscript, your readers or your email address. Your account’s own service and its terms cover what happens there |
| Bluesky or your Mastodon server | Optional automatic posting, only if you connect your own account in Marketing | Only the posts you approve and send: their words and picture. Never your manuscript, your readers or your email address. Your account’s own service and its terms cover what happens there |
| Stripe | Card payments and refunds, only when you buy promotions or a plan | Your payment details and email, entered on Stripe’s own checkout page |
| SendFox | Our newsletter, only if you tick “Email me Author Beta news”; and, if we switch it on, delivering the site’s own emails | Your email address and handle for the newsletter; for site emails, the address and the message being sent |
| Email providers | Delivering emails to your inbox | The email itself, as with any email |
The share buttons on beta pages are plain links: nothing from Facebook, X or anyone else loads on our pages, and nothing is sent to them unless you click a button and choose to post.
Emails
We send emails you need (confirmations, password resets, beta updates) and, if you turn them on, a daily email and new-beta alerts. Every optional email can be switched off in your settings, and you can choose which genres new-beta alerts cover. Now and then we may email an important service notice (for example a change to these terms, a security matter or planned downtime), and the site may show a short notice at the top of the page. Readers’ notes and authors’ notes to readers are never put into emails.
Our mailing list. If you tick “Email me Author Beta news”, we add your email address and handle to our mailing list at SendFox, which sends our newsletters. Nothing else about you, your books or your reading goes there. Untick the box in your settings, use the unsubscribe link in any newsletter, or delete your account, and you’re unsubscribed.
Blog comments. If you comment on a blog here, we keep the name, email address and comment you give, and a scrambled form of your internet address to stop spam. Our own spam check (no outside service) looks at the comment’s text, links and email domain; a blog’s author can trust or block a commenter on their blog, which we record against a scrambled form of the email (and, for blocks, of the internet address). Your name and comment show under the post once the blog’s author approves them; your email address is never shown publicly, and only the blog’s author (or we, for our own blog) can see it, to reach you about your comment. The author can delete your comment at any time, and so can we; ask us and we’ll delete it.
Blog view counts. Blogs count how many times each post is read, without cookies and without tracking you across pages or sites. To count each reader once a day we keep a scrambled code made from your internet address, the post and the date; it can’t be turned back into your address and is deleted after two days. Authors see only totals.
Authors’ newsletters. If you subscribe to an author’s news on their page, we email you once to confirm; if you don’t confirm within 48 hours, the request is deleted. Once you confirm, your address goes to that author’s list at SendFox and our copy is deleted; we keep a scrambled fingerprint (so we can count and honour unsubscribes) and a record of when, where and what you agreed to. The author sees how many people subscribe, never who. Authors who use their own mailing service (such as Mailchimp, Kit, MailerLite, Brevo, beehiiv or their own SendFox account): the sign-up form says so and names the service, and once you confirm, your address goes to that author’s own list there, and our copy is deleted. The author then holds your address and manages that list under the service’s terms and their own. Every newsletter has an unsubscribe link, and nl.php works too.
Free copies and review copies. If you claim a free book or an advance review copy from an author, we keep your name and email address (the email encrypted) so we can email you your download link and make your copy. Your copy carries your name and a short code, so the author can trace a copy that’s shared without permission. The author sees your name, part of your email address and how many times you downloaded. If the author deletes the offer, the list goes with it.
Author Links pages. An author’s links page counts visits and clicks per day, by where visitors came from (a tag in the link, or the name of the referring site) and by type of device. No cookies are set, and no address or visitor profile is kept. If the author adds a video or a booking calendar, that service (YouTube in privacy-enhanced mode, Vimeo without tracking, Calendly or Cal.com) loads only on that page, under its own terms.
Writing to an author (Author Mail). If you email an author’s Author Beta address (or reply to their newsletter), the message and your address are stored encrypted and the author sees your name, never your email address, not even in what you wrote; when they write back, or write to you again, we send it without showing your address to them or to anyone else on the message. We keep the message for up to a year, or until the author deletes it (longer only if the author stars or labels it), and your name and the scrambled address in the author’s contacts so they can reply. Attachments are removed, pictures in your message aren’t loaded until the author chooses to see them, and we never add tracking to authors’ mail.
Spam protection for Author Mail. Incoming mail is checked by our mail server’s spam filter (SpamAssassin); clear spam goes to the author’s Spam folder and borderline mail to a Quarantine they review, both deleted after 30 days. Authors can block a sender (their mail is then not stored at all) or mark them as spam or safe. Outgoing author mail has daily and hourly sending limits and a cap on people per message; links may be checked against the Spamhaus domain blocklist and messages scanned by a spam filter before sending, and anything flagged is held for our review rather than sent. Automatic replies are sent at most once every four days per person and never to automated or bulk mail. These checks use your message only to decide whether it’s spam.
Plans. If you press “Tell me when it’s ready” on the plans page, we send you one email when it opens, and nothing else about it. You can take yourself off that list on the same page.
Cookies
We use three first-party cookies, all strictly necessary, and nothing else: ps_sess keeps you signed in during a visit, ps_rem keeps you signed in between visits if you ask us to, and ab_fb is a random marker that says this browser has already used a free round, free promotions or demos. None of them is used for advertising or analytics, or read by anyone but us.
Because the site is delivered through Cloudflare, Cloudflare may also set a strictly necessary security cookie (such as cf_clearance or __cf_bm) if it needs to check that a visit isn’t an automated attack. These are used only for security, aren’t used for advertising or to follow you to other sites, and expire within hours to a day.
Fair use of free rounds
Each person and each book gets one free first round. To keep it fair without tracking anyone, when you claim something free we keep one-way scrambled fingerprints of your email address, the browser marker above, your internet connection and, for a free round, the opening of your manuscript (made in your browser). They can’t be turned back into your address, connection or text, they’re only compared with each other, and connection fingerprints are deleted after 30 days. Accounts linked to a main account don’t get a free first round: linking uses it up, and unlinking doesn’t restore it. A Free account that has used its free round can only be linked on a paid plan, and a linked account refunded back to Free after using its free round is unlinked. If a free round is refused by mistake, tell us and we’ll sort it out.
When the law requires it
We disclose information only when we’re legally required to (for example, by a valid court order), to protect someone from serious harm, or to enforce our terms against someone who has broken them, such as giving an author the evidence that a reader leaked their book. Where the law allows, we’ll tell you first. Because books and notes are encrypted and we hold no key, we couldn’t hand over their contents even if asked.
How we protect it
Encryption in your browser for books, notes and answers; HTTPS for everything; passwords stored only as one-way hashes; optional two-step sign-in with any authenticator app (required for the site owner); a list of your signed-in devices with “sign out everywhere”; scrambled IP codes; strict browser security rules; limits on sign-in attempts; the private parts of the site closed to AI crawlers and agents; and hidden details, such as GPS location, removed from every uploaded image. No system is perfectly secure, and we can’t promise yours never will be breached, but we do everything within our ability to protect it.
How long we keep things
Manuscript text: until 30 days after your last round closes, or until you delete it. Notes and feedback: until the author deletes them. Reading logs: 30 days. Your security activity: one year. Database backups: each nightly backup is kept for up to 14 days, encrypted, then deleted; it never contains manuscript text, so something you delete leaves our backups within that time too. Fair-use fingerprints: 30 days for connections, up to 3 years for the rest. Uploaded images: until you replace or remove them, when the file is deleted. The plans waiting list: until we send that email or you take yourself off. We keep no backups of manuscripts beyond our host’s routine short-term server backups, which hold only the encrypted copy.
Your choices and rights
You can see and change your details in Settings, download everything we hold about your account in one file (Settings → Security → Download my data), download your books’ feedback (authors: Export), and delete your account at any time. When you delete it, your books and every copy of their keys are deleted, your profile and reviews are erased, and notes you left on other authors’ books stay with those books under the name “Former reader”. To ask what we hold about you, or for anything else, email ma@kirkeby.us. Depending on where you live you may have further rights (for example under the GDPR or California law); we’ll honour them.
Children
Author Beta isn’t for anyone under 16. If we learn that someone under 16 has an account, we’ll close it.
Changes
If we change this policy in a way that matters, we’ll tell you by email or on the site before it applies.