Privacy Policy
Effective: 2026-10-26 · Last updated: 2026-10-26
Operated by: Eidetic LLC, a Texas limited liability company ("we," "us")
Contact: [email protected]
The short version
You upload a few photographs of someone you love: a child, a partner, a grandparent, a pet. We use them to draw an illustrated character sheet, a picture of them as a storybook character. Once you lock that sheet, pages are drawn from the sheet, not the photographs, and the photographs are deleted 30 days after that first lock. Until then they are read again only if you ask for a fresh sheet or a fresh description, or when a tale draws a new outfit.
We also write a few lines about how the person looks from the photographs: the first time you add them, if you have not typed a description yourself, and again whenever you ask for a fresh one. Those words are not deleted with the photographs. They stay with the character until you change them or delete the character.
You can also add photographs to one tale: a person, a place, an outfit, a favorite toy. Those are sent along each time that tale's pictures are drawn, and they are deleted 30 days after the pen last worked on that tale.
- We do not use anything you upload to train AI models. Not ours (we don't have any) and not our providers'.
- We delete the photographs 30 days after you first lock a character's sheet, automatically. You can delete them sooner, yourself, at any time.
- We don't sell your data. We don't run ads. There are no third-party trackers or analytics scripts in this product.
- You can delete your account yourself, from your account page, and it takes effect immediately.
The rest of this document is the detail behind those sentences. It is longer than the short version because the short version is worth checking.
1. Who this policy is about
TuckABook is for families. The account holder is an adult. Children do not have accounts of their own: no email address, no password, nothing they can upload. A guardian may create a reader seat for a child (a first name and a PIN the guardian chooses), which opens the household's finished books for reading and nothing else. A reader seat cannot upload photographs, cannot create or change anything, has no mailbox of its own, and exists entirely inside the guardian's household; the guardian can remove it at any time.
The people and pets in your stories appear here as subjects: their photographs, their names, and the traits you write about them. They can be children or grown-ups. When we say "your information" below, we mean both your own account details and everything you provide about the people and pets in your stories.
You must be 18 or older to hold an account, and you must be the parent or legal guardian of every child whose photograph you upload. Do not upload photographs of other people's children. Before you upload a photograph of a grown-up, get their OK.
2. What we collect
2.1 Information you give us
| What | Why | How long we keep it |
|---|---|---|
| Email address and name | Sign-in, receipts, service emails, and an optional reminder when you leave a draft book unfinished | Until you delete your account |
| Photographs of the people and pets in your stories (up to 5 per character) | Drawing that character's illustrated sheet | Deleted 30 days after you first lock the sheet (see §4) |
| Photographs you add to a tale (a place, an outfit, a toy, a person), and the line you write about each | Drawing that tale's pages and cover, and telling the story what the photograph means | The photographs are deleted 30 days after the pen last worked on that tale (writing, drawing, narrating or a fix). The line you wrote stays with the tale |
| What is written about a character: name, age, personality notes, outfit, and appearance details, whether you typed them or we wrote them from the photographs | Making the character look and behave like them in the story | Until you delete the character or your account |
| Story premises and the books you create | The product | Until you delete them or your account |
| Feedback you send us through the in-app form | Fixing what's broken | See §4.3. This one survives account deletion, de-identified |
2.2 Information we generate
Character sheets, page illustrations, cover art, narration audio, and the story text itself. These are created from your inputs and stored with your account.
We also keep operational records of each AI call: which model ran, how long it took, how much it cost, whether it failed. These records contain no prompts, no story text, and no images.
2.3 Information collected automatically
- A session cookie, so you stay signed in.
- A visitor cookie (
nl_vid), stored for one year, which lets us count how many distinct people opened a shared book link. It is a random identifier. It is not linked to an advertising profile, and it is not shared with anyone. - Standard server logs (IP address, timestamp, and requested URL), kept for operational and security purposes.
- In-app product events, for example "a book was finished," "a share link was viewed." These record what happened and when.
There are no third-party analytics, advertising, or tracking scripts anywhere in this product. No Google Analytics, no Meta pixel, no session recorders. We looked, because we wanted to be able to write this sentence.
2.4 What we deliberately strip
When you upload a photograph, we immediately re-encode it before storing anything. That process removes the embedded metadata, including GPS coordinates, camera serial numbers, and timestamps. The original file is never stored. What we keep is a resized copy, at most 2048 pixels on its longest edge.
3. Where a photograph actually goes
This is the part most policies leave vague, so here is the whole path.
- You upload it. It travels over an encrypted connection to our server.
- We normalize it: rotate, resize, strip metadata, re-encode.
- We store it on our own server infrastructure, in private storage. Only you can retrieve it. Photographs are never visible to other members of your household, never included in a shared book link, and never included when a character is published.
- We send it to an AI provider when one of these jobs is done. A job can be done more than once: each time a sheet is drawn, and each time a description is written.
- Drawing the sheet. Google (Gemini) draws the character sheet from your photographs.
- Writing an appearance description. This happens the first time you add photographs, if you have not typed a description yourself, and again whenever you ask for a fresh one. OpenAI or Anthropic (Claude) reads the photographs to write it.
- Checking the sheet. Google (Gemini) compares the finished sheet with the photographs, to see that it really looks like them. If Google is unavailable, Anthropic or OpenAI does it.
- You lock the sheet. From here on, pages are drawn from the sheet, not the photographs. Every page illustration is drawn from the locked character sheet, previous pages, style references, and any photographs you added to that tale itself. Until they are deleted, the photographs are read again only if you ask for a fresh sheet (a redraw, a fresh start, a change from your notes, a new look) or a fresh description, or when a tale draws a new outfit sheet for someone in it. Each of those sends the photographs to the providers in step 4 again.
- The photographs are deleted 30 days after the first lock.
Photographs you add to a tale take a shorter path. They are normalized and stored the same way (steps 1 to 3). They are sent along when that tale's pages, its cover and its spot fixes are drawn, so they go to the company that draws the picture. They are deleted 30 days after the pen last worked on that tale.
The providers, named
We use these companies to run the AI features, take payments and send email. They are the only third parties that receive anything you provide.
Which company does which job is a setting we can change, and when one company is unavailable the work goes to the next one. So this table says what each company can receive, not only what it receives on an ordinary day.
| Provider | Can receive | Their commitment |
|---|---|---|
| Google (Gemini) | Photographs: it draws the character sheet from them and checks the finished sheet against them. Photographs you add to a tale, when it draws a page. Also what is written about a character, premises and story text, the drawings we make, and the story text it reads aloud. | We are on Google's paid API tier. Under those terms Google does not use prompts or responses to improve its products, and there is no human review of content. |
| OpenAI | Photographs, when it writes an appearance description, checks a sheet against them, or draws a character sheet or a new look from them. Photographs you add to a tale, when it draws a page, a cover or a fix. Also what is written about a character, premises and story text, when it writes a story. Scene descriptions and the locked character drawings, when it draws or checks a page. Story text for narration, when Google is unavailable. | OpenAI's API terms say it does not use API content to train its models unless the customer opts in. It may keep API content for up to 30 days to check for abuse. |
| Anthropic (Claude) | Photographs, when it writes an appearance description, and when it checks a sheet because Google is unavailable. Also what is written about a character, premises and story text, when it writes or helps with a story. | Anthropic's commercial terms state it may not train models on customer content. |
| OpenRouter, which passes the request to Black Forest Labs (FLUX) | What is written about a character, scene descriptions and the drawings we make, only when the companies ahead of it fail to make a drawing. No photographs in an outage: a drawing that carries a photograph is not passed on. It fails instead, and takes no ink. | Each works under its own published terms. |
| ElevenLabs | Story text only, for narration, when Google and OpenAI are unavailable. | Does not train on API content by default. |
| xAI (Grok) | Story text only, for narration, as the last resort when Google, OpenAI and ElevenLabs are all unavailable. | xAI does not train on API inputs or outputs. API requests are retained encrypted for 30 days for abuse detection, then deleted automatically. |
| Stripe | Your name, email, and payment details when you subscribe or buy a bottle of ink. We never see or store your card number. | Stripe is the payment processor; its own privacy policy governs. |
| Resend | Your email address and the emails we send you. Feedback you send through the in-app form reaches us by email, so it passes through Resend too. | Email delivery only. |
None of these providers is permitted to use your photographs, your family's information, or your stories to train an AI model. We may change which company does which job, or add a new one. We update this table before any change goes live, and we tell families before a new company receives photographs.
4. How long we keep things, and how you delete them
4.1 Photographs delete themselves
The first time you lock a character's sheet (the moment you tell us the drawing looks right), a 30-day clock starts. Locking again later, after a redraw or a fix, does not restart it. When it expires, we delete the source photographs: the attachment, our record of it, and the stored file. The appearance description is words, not a photograph, and it is not deleted with them: it stays until you change it or delete the character.
This runs automatically. It is not a manual cleanup someone has to remember.
What this means for you: after the photographs are gone, that character's sheet can no longer be regenerated from scratch. You can still edit the existing sheet, still write new books with that character, still read everything you've made. But a fresh redraw would need fresh photographs.
One exception, and it's in your favor: if the same photograph is attached to a second character, or to a tale, it survives until that one's window expires too. We won't break one character's sheet to hit a deadline on another's.
Outfit photographs for a specific look stay with that look until you delete the look, the character, or your account (and any admin bake-off test copies are deleted with the account).
4.2 What you can delete yourself, right now
| Action | What it removes |
|---|---|
| Delete a photo (on the character, or in your photo library) | The photograph and the stored file, immediately, unless another character, a look, or a tale still uses it |
| Remove a companion | Takes them out of your library. Finished books keep their existing artwork so they still read. Removing starts the 30-day deletion clock on their reference photographs, which are deleted on the date shown under their name in Removed (unless something else still uses one). Their illustrated sheets and any look's outfit photographs stay so you can put them back until you use the option below |
| Permanently erase a companion | The character, their sheet, their icon, and their photographs, files and all |
| Delete your account | Everything in §4.3 |
4.3 Deleting your account
You can delete your account yourself, from your account page. There is no waiting period and no recovery window: when it's done, it's done. You can preview exactly what will be removed before you confirm.
Deleted immediately: your account and sign-in records, every character, sheet, photograph and book, all page images and narration audio, your photo library, your household (if you were its only member), any children's reader seats in the household (if you were its only guardian), quota records, and anything you'd joined a waitlist for.
Kept, and here's why:
- Billing records: your Stripe customer and subscription rows. We are required to keep records of money that changed hands. These contain identifiers and amounts, not card numbers. Deleting your data at Stripe is a separate request; write to us and we will make it.
- AI cost logs, with your identity removed. We keep which model ran, how long, and what it cost, so we can understand our own economics. Your user ID is erased, and so are the free-form fields that could echo a name.
- Product events, fully de-identified: the fact that "a book was finished" on a date, with no link to you.
- Feedback you sent us, detached from your identity. Your device details are erased. We keep the message itself, because it usually describes a bug we still need to fix. If your feedback contained a family member's name and you want it removed, ask and we will delete it.
- Your household, if other members remain in it. Their libraries are theirs.
Two honest caveats:
- Backups. Our database is backed up nightly and those backups are kept for 7 days. Deleted data persists in encrypted backups until they roll off.
- Published characters. If you published a character to the in-app marketplace and another family imported it, their copy (the illustrated sheet, not your photographs) stays with them after you delete your account. Your photographs are never copied when a character is published. If you don't want this, don't publish.
5. Sharing a book
When you create a share link, anyone holding the link can read that book. That's the point: it's how grandparents see it.
Two things you should know before you send one:
- A share link is a capability, not a login. Anyone the link is forwarded to can open the book. We do not check who they are.
- Revoking a share link stops new visits, but does not reach copies already taken. If someone opened the book and saved an image, or bookmarked a direct image address, that saved copy keeps working after you revoke the link. We are telling you this plainly rather than implying that revocation is a recall. Treat a shared book like a photo you texted someone: once it's out, it's out.
We are working on making revocation complete. Until this section says otherwise, it isn't.
Linking your own AI assistant
On the Family plan, a grown-up can link their own AI assistant (such as Claude or ChatGPT) to TuckABook. Nothing is linked unless you sign in and tap Yes.
- What it can read: your cast (names, descriptions, sheets, and the reference photographs you added), your books (story words, pages, pictures and links), your photo library and your shelves. It never gets your password or your payment details.
- What it can do: what you ask it to. Write and change story words and storyboards, make book drafts, add photographs to your cast, and, when you ask, draw, narrate or write with TuckABook's AI, which uses your pen's ink the same as in the app.
- What it keeps: what it reads is sent to that assistant's company and kept under its own terms and your settings there, not ours. On our side we keep the assistant's name, the day you linked it, and its sign-in tokens (stored only as a scrambled hash).
- How you stop it: Account, Linked assistants, Disconnect. It is cut off at once. We also email you each time an assistant is linked, so a link you didn't make doesn't go unnoticed. Deleting your account removes every link.
6. How we protect information
- Encrypted connections (HTTPS) everywhere.
- Photographs are stored in private storage and served only through an authenticated proxy that checks, on every request, that you own the file. There are no public links to a photograph.
- Household isolation: every new account gets its own private household. Members of one household cannot see another's library.
- API keys and secrets live in server environment configuration, never in the app you run.
No system is perfectly secure, and we won't pretend otherwise. If we discover a breach affecting your information, we will tell you.
7. Children's privacy
TuckABook is a product for families. It is not directed to children, does not accept accounts from children, and collects nothing directly from a child.
Everything we hold about a child, we hold because a parent or guardian provided it. You can see it, correct it, and delete it at any time using the controls in §4.
If you believe a child has created an account, contact us at [email protected] and we will remove it.
8. Your rights
Wherever you live, you can ask us to:
- See what we hold about you and your household
- Correct anything inaccurate
- Delete your account and its contents. You can do this yourself, immediately (§4.3)
- Export your books and artwork
- Object to a specific use, or ask us to restrict processing
Depending on where you live, some of these are legal rights and some are simply how we operate. We don't distinguish: you get them either way. Write to [email protected]. We aim to respond within 30 days.
We do not sell personal information, and we do not share it for cross-context behavioral advertising. We never have.
9. Where data lives
Our servers are in the United States. Our AI providers process requests in their own regions. If you use TuckABook from outside the US, your information is processed in the US.
10. Changes
If we change how we handle your information, particularly anything in §3, §4 or §5, we will update the date at the top and notify account holders by email before it takes effect. We will not quietly broaden what we do with photographs of your family.
11. Contact
Eidetic LLC
Pearland, Texas, United States
[email protected]
TuckABook is a product of Eidetic LLC. "TuckABook" is a brand name; the legal entity is Eidetic LLC.