Privacy policy
Last updated: 2026-11-19
Controller
Pascal Lindenau, Forddamm 7, 12107 Berlin, Germany. Use the contact address below for privacy requests. Competent supervisory authority: Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59-61, 10555 Berlin, Germany. Web: https://www.datenschutz-berlin.de/
Stories, AI and digital books
Stories, recordings and photos are stored on your device and in your private iCloud. Selected text, context and photos pass through our service when you use AI or create a digital book. OpenAI processes text for the requested AI features. We do not promise immediate deletion or zero provider retention.
We store book manuscripts and the original story text used to create them on our server so you can edit and remake your book. Generated PDFs are removed from the book service after seven days.
Apple operates iCloud and device services. You decide which stories to share. Only upload material you are entitled to use, including information about other people.
Accounts, purchases and gifts
Sign in with Apple supplies an Apple identifier and, when shared, an email address. Our backend stores account, session, transaction, access-right and redemption records. Stripe processes web payments. We store purchase references and amounts, not full payment-card details.
For gifts we process the buyer email, recipient details and personal message supplied by the buyer. Resend handles purchase and gift email delivery. A recipient email is sent only when the buyer selects that option. Gift recipients can contact us about data supplied by the buyer.
For a printed book we process the delivery name, postal address, email and phone number entered in the app. We send them with the book file to our print partner Lulu Press, Inc. in the USA, which prints the book and hands it to the post. The shipping country chosen at checkout is stored with the purchase.
Waitlist and website
The waitlist stores your email, chosen printed edition, who the book is for, language, consent and signup time, plus confirmation delivery status. Resend receives the address and message for delivery. You can withdraw launch-update consent through the unsubscribe link or by contacting us.
Waitlist checkout pageviews store language and selected printed edition without an IP address in that table. Abuse protection temporarily uses IP addresses. Hosting systems may keep request logs. Essential browser storage supports sign-in and site functions.
Every page of this website uses Revtrail, our own analytics service, which we run on Cloudflare Workers. Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA, processes the data for us under its data processing addendum with EU standard contractual clauses. Cloudflare is also certified under the EU-US Data Privacy Framework. Revtrail records the page address, referrer, UTM parameters, browser, operating system, device type, country, region and city derived from the IP address, clicks on marked buttons and outbound links, and time on page. For a visit from a Meta ad, it also records Meta's click ID from the link and your user agent, and deletes both 28 days after the visit. It does not store the IP address. We combine the IP address and your user agent with a salt that changes every day into a hash, so a visit cannot be linked to the same person on another day. Without your consent, Revtrail sets no cookies and stores nothing else on your device, so it needs no consent under section 25 of the German TDDDG (formerly TTDSG). The legal basis is Article 6(1)(f) GDPR, our legitimate interest in understanding which pages and channels work. We keep the raw data for up to 24 months.
When you pay on this website, checkout sends the Revtrail ID of your visit to Stripe with your order. Stripe reports the payment to Revtrail with its amount, currency, your email address and your name. Revtrail links the payment to that visit, so we can see which pages and ads lead to a purchase. The legal basis is again Article 6(1)(f) GDPR.
Ad measurement with Meta
We advertise on Facebook and Instagram. On your first visit, a banner asks whether we may measure which ads bring visitors and purchases. We do what this section describes only after you choose Accept. If you decline or make no choice, no Meta code loads and Revtrail stays cookie-free. We store your choice in the cookie tmys_consent for 12 months. It holds only that choice, and we need it to respect your choice.
After you accept, Revtrail stores a random visitor ID in the cookie rt_vid, for up to 12 months after your last visit, and a session ID in the cookie rt_sid, for 30 minutes. The cookies rt_consent and rt_mkt record your consent for 12 months. This lets us link a purchase made days after an ad click to that click.
The Meta pixel then loads from Meta's servers on every page of this website. It sets the cookie _fbp, a browser ID, and, if you came from a Meta ad, the cookie _fbc with the ad's click ID. Both last up to 90 days. The pixel tells Meta each page you view here. Your browser connects to Meta directly, so Meta also receives your IP address and details about your browser. We use the pixel for page views only.
When you start a checkout or buy, Revtrail sends the event to Meta from its server, through Meta's Conversions API. For a purchase it sends the order value, currency, order number and product. Each event can carry the address of the page, the Meta click ID from the ad link, the browser ID from the _fbp cookie, your browser's user agent and, as SHA-256 hashes, your email address, your country and city, and the customer number from our payment provider. Revtrail sends no IP address. It deletes the user agent, the click ID and the browser ID 28 days after the visit, and the browser ID at once when you withdraw your consent.
The recipient is Meta Platforms Ireland Ltd., Merrion Road, Dublin 4, Ireland. We and Meta are joint controllers for collecting the data on this website and passing it to Meta (Article 26 GDPR). Our agreement is Meta's Controller Addendum: https://www.facebook.com/legal/controller_addendum. You can exercise your rights with us and with Meta. Meta then uses the data under its sole responsibility, for example to show and improve ads, and may link it to your Facebook or Instagram account. Meta's privacy policy: https://www.facebook.com/privacy/policy. Meta may transfer data to Meta Platforms, Inc. in the USA and is certified under the EU-US Data Privacy Framework.
The legal basis is your consent under Article 6(1)(a) GDPR, and for the cookies and the pixel also section 25(1) of the German TDDDG. You can withdraw your consent at any time with the Privacy settings link at the bottom of every page. Withdrawal takes effect for the future. We then delete the cookies rt_vid, rt_sid, rt_consent, rt_mkt, _fbp and _fbc in your browser, and Revtrail sends Meta nothing more about your visits. Meta processes data it has already received under its own privacy policy.
App usage events
The iPhone app sends usage events to Revtrail, our own analytics service on Cloudflare Workers. An event records which screen opened, which onboarding step you reached, when an offer or payment screen appears, and when a payment starts, finishes, is cancelled or fails, with the kind of purchase and nothing about your card. It also records a completed App Store purchase of the PDF, whether you allowed or denied the microphone, speech recognition and notification prompts, and that you recorded a story, your book was assembled or its PDF was ready. What you say or write stays out of it. Story text, recordings, photos, names, addresses, book titles and gift messages never leave the app this way. Each upload also carries the app version, the iOS version, the device model, the language and region setting, and an install ID. The install ID is a random number the app creates each time it starts and keeps only in memory, so every launch gets a new one. The app stores nothing for analytics on your device, sends no advertising identifier and does not track you across other apps or websites.
When the app starts, it asks Apple for an Apple Ads attribution token and sends it to Revtrail. Revtrail passes the token to Apple, which answers whether the install came from an Apple Ads campaign. A completed App Store purchase reaches Revtrail as Apple's signed transaction record, which holds the product, the price, the currency, the date and a purchase identifier our app derives from your account. Our backend also passes Revtrail a copy of Apple's server notifications about the purchase, for example a refund. Revtrail derives your country, region and city from the IP address of each request and does not store the IP address. Cloudflare, Inc. processes this data for us under its data processing addendum with EU standard contractual clauses and is certified under the EU-US Data Privacy Framework. The legal basis is Article 6(1)(f) GDPR, our legitimate interest in seeing where people leave onboarding and what they buy. We keep the raw data for up to 24 months.
Partner programme
Websites and blogs can join our partner programme. For each partner we store the name of the site, the contact's name and email address, the language, the partner's discount code, the date they joined and whether the account is active. To sign in, a partner asks for a link by email, and Resend delivers it. We store only a hash of the link. It works once, for 15 minutes. After sign-in, the cookie tmys_partner keeps the partner signed in for 30 days. The cookie is strictly necessary, so it does not wait for consent. To stop misuse, we count sign-in requests per IP address and per email address for 15 minutes.
We pay commission once a month by bank transfer or PayPal. For this we process the bank details or PayPal address the partner gives us, and we record each payout with its amount, currency and date. A bank transfer goes through our bank. A PayPal payout goes through PayPal (Europe) S.à r.l. et Cie, S.C.A., 22-24 Boulevard Royal, L-2449 Luxembourg.
If you buy with a partner's code, we store with your payment which code you used. For each sale the partner sees the date, the country, the edition, the amount paid and their commission. The partner never sees your name, email address or delivery address.
The legal basis for partner data is the partner agreement (Article 6(1)(b) GDPR). Payout records are accounting records that tax law requires us to keep (Article 6(1)(c)). We record which code a buyer used so we can pay partners what we owe them, which is our legitimate interest (Article 6(1)(f)). We keep partner data while the partnership lasts and until we have paid the last commission. We keep payout records for eight years.
Purposes, legal bases and retention
We process purchase and account data to fulfil the contract under Article 6(1)(b) GDPR, and required accounting records under Article 6(1)(c). Waitlist updates rely on consent under Article 6(1)(a). Security processing can rely on legitimate interests under Article 6(1)(f). AI features and book writing run when you ask for them and rely on the consent you give in the app before any text leaves your device (Article 6(1)(a)). Passing a present to its recipient serves the buyer's interest and ours in a present that arrives (Article 6(1)(f)). Hosting, abuse protection, error diagnostics and usage analytics rest on our legitimate interest in running a secure, working service and in seeing which pages and screens work (Article 6(1)(f)). Stories can mention other people and sensitive topics. We process such content only because you chose to send it, and you must have the right to share it.
We use these providers to run the service. Each one receives only the data it needs for its task. OpenAI processes the text, context and photos you send for AI features and book writing, and we ask it not to store the responses. Stripe processes web payments. Resend sends purchase, gift, waitlist and withdrawal emails. Apple provides Sign in with Apple, App Store purchases, push notifications and iCloud. Lulu Press, Inc. prints and posts the books. Cloudflare, Inc. runs our analytics and stores finished book files in data centres in the EU. Our servers and databases run on a rented server in Frankfurt am Main, Germany, operated by Hostinger. Where a provider processes data in the USA, we rely on its certification under the EU-US Data Privacy Framework or on EU standard contractual clauses. Write to us for a copy of the safeguards that apply. We keep account, purchase, gift and book data while your account exists. We delete generated reader PDFs after seven days. We delete uploaded photos waiting for a book, and AI proposals for a book structure or a rewritten passage, after 24 hours. We delete the delivery address 120 days after the book ships. When you delete your account in the app, we delete your stories, manuscripts, books and photos. We keep records of payments and invoices for eight years because tax law requires it. A receipt that proves an account deletion holds only a hash, and we delete it after 30 days. Sign-in sessions last up to 365 days. We keep waitlist records until you withdraw consent or the launch emails are finished. OpenAI, Stripe, Resend and Lulu keep data under their own terms for the periods they state.
Purchase and account information is needed to process purchases. Optional gift details and waitlist signup are voluntary. Without required information we cannot provide the corresponding service.
Your rights
You may request access, correction, erasure, restriction and portability where the GDPR provides these rights. You may object to processing based on legitimate interests. You may withdraw consent at any time without affecting earlier lawful processing. You may complain to a supervisory authority, including in your country of residence or work.
Contact us using the address below. We normally answer within one month; the GDPR permits extensions in specified cases. App export and deletion controls help manage local and iCloud content. Account deletion does not replace any legal duty to retain transaction records. We do not use AI to make decisions producing legal or similarly significant effects about you.
Contact: support@tellmeyourstoryapp.com