Privacy policy

Double Factorial AB (organisation number 559422-3512) is the controller of your personal data: we decide why and how it is used.

Blockhusvägen 131, 187 46 Täby, Sweden
info@doublefactorial.com

• Your account. Your name, your email address, and a scrambled form of your password (never the password itself). Whether you have confirmed your email address, and when you accepted the terms. We need these to let you in and to write to you about your account. Basis: running the service you asked for.
• Your stories. The ideas you type, the choices you make, and everything made from them: the text, the pictures and the narration. Basis: running the service you asked for.
• What you have used. A record of each piece of writing, picture and narration made for you, with its size and what it cost us to make. It is how your monthly allowance is counted. Basis: running the service you asked for, and our interest in keeping its costs under control.
• Your subscription. That you subscribe, when your free week and each month start and end, and the amount. Your card number never reaches us: Stripe holds it, or Google if you subscribe in the Android app (section 4). For a subscription through Google Play, we also keep the purchase reference and order number Google gives us, so that we can check the subscription with Google. Basis: running the service you asked for, and the bookkeeping law we have to follow.
• Print requests. If you ask for a printed book: the name and postal address you give for it, how many copies, and any note you add. Basis: answering your request.
• Reports. If you report a story to us: which story and page, what you say about it, and when. Sending a report lets us read that story and see its pictures while we look into it; once we have dealt with the report, we can no longer see them. Basis: our interest in keeping what the service makes safe.
• Security records. When someone asks to reset a password, a record of the request, including where it came from, such as its network address, so that abuse can be traced. Basis: our interest in keeping accounts safe.

We do not ask for your children's names, ages or photographs, and the account must belong to an adult (terms, section 2). Please do not put anything in a story idea that you would not want passed to our AI provider (section 4), such as a child's full name together with where they live or go to school.

Storybook sets two cookies, both needed for the site to work. It uses no advertising, tracking or analytics cookies. The only third-party script is Cloudflare's signup check, on the signup form only and only while it is switched on (section 4).

• storybook_session keeps you signed in. It is set when you sign in and lasts 30 days, or until you sign out.
• storybook_unlocked remembers that you have entered the site passphrase, if the site is asking for one. It lasts 90 days.

Because both are strictly necessary, the law does not require your consent for them, and there is no cookie banner.

The Android app keeps its own copies of these two cookies, in its private storage on your phone, for the same reasons; signing out removes the first. It also keeps one setting (light, dark, or as your phone is set) and the pictures it has shown you, in a cache your phone can clear. It contains no advertising or analytics, and nothing it keeps is backed up off your phone.

We do not sell your data and we do not use it for advertising. A few companies process it for us, only so far as the service needs:

• OpenAI receives your story ideas and the text of your stories, to write them, to check them against our content standards, to draw the pictures and to read them aloud. It processes them for us under a data processing agreement: it does not use them to train its models, and keeps them for up to 30 days to watch for abuse, unless the law requires longer. See OpenAI's privacy policy.
• Stripe takes your payments and sends your receipts. It receives your email address and your card details, which go to Stripe directly and never through us. See Stripe's privacy policy.
• Google Play takes the payments for a subscription bought in the Android app, under its own terms, and sends the receipts. It holds your payment details, which never reach us. It tells us how the subscription stands — whether it is running, when it renews, whether a payment failed — and we tell it which account a purchase belongs to as a scrambled code, never your name or email address. See Google's privacy policy.
• Google Cloud hosts the service — the server, the database, and the stored pictures and narration — and passes Google Play's notices about subscriptions on to us. It is located in the United States.
• Cloudflare, on the signup form only, runs a check (Turnstile) that tells a person from a script. It sees your browser and network address while you sign up, under its own privacy policy. Nothing else on the site loads from Cloudflare.
• Resend sends our emails: confirmations, password resets and notices about your subscription to you, and your print requests to us. It is located in the United States.

We may also have to give information to an authority if the law requires it.

Our servers, and several of the companies above, are in the United States. When your data goes there, we rely on the safeguards those companies provide for transfers out of the EU, such as the European Commission's standard contractual clauses or its adequacy decision for the EU–US Data Privacy Framework. You can ask us for details (section 8).

• Your account and stories stay until you delete your account. Then the account, every story, and the pictures and narration made for them are removed, from your account page, at once.
• A report you send us stays until you delete your account, even if you delete the story it is about: it keeps the story's title, but not its words or pictures.
• Our nightly database backups are kept for 30 days, so deleted data can remain in a backup for up to that long, and is not used for anything else.
• Records of payments are kept for as long as bookkeeping law requires (seven years in Sweden), even after you delete your account.

Story ideas and finished stories are checked by AI against our content standards, before anything is made. A check can lead to an idea being refused. If you think one was wrong, tell us and a person will look at it.

You can ask us, at any time, to:

• show you the data we hold about you;
• correct it (you can change your name and email address yourself, on your account page);
• delete it (you can delete your account yourself, on your account page);
• stop using it, or limit how we use it, where we rely on our own interest for it (section 2);
• give it to you in a form you can take elsewhere. Your account page has a download of everything you have written.

Write to info@doublefactorial.com and we will answer within a month.

If you think we have handled your data wrongly, you can complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, imy.se), or to the data protection authority where you live.

Everything between Storybook and your browser or the Android app travels encrypted (HTTPS), and the app will not connect any other way. Your password is kept only in scrambled form, and so are the links we email for resetting it or confirming your address. You can sign out every other device at once from your account page, and changing your password does the same.

The site serves your stories, pictures and narration to your account alone. When you ask us to print stories, we are sent their titles, summaries and back-cover text; and while we look into a story you report to us, we can read it and see its pictures (section 2). The database, its nightly backups and the pictures and narration are kept in Google Cloud, which encrypts them where they are stored. Only we can sign in to the server, and the keys it uses are kept in Google Cloud's secret store, not in its code.

If your data is ever exposed, we will tell the Swedish Authority for Privacy Protection, and you, as the law requires.

If what we do with your data changes in a way that matters, we will update this page and its date, and write to you before the change applies to you.