Privacy Policy
Last updated 9 September 2026
TaleCompiler turns a script into a story you can interrupt. This page says exactly what that involves for your data. It is short because the service collects little.
Who we are
TaleCompiler is an independent project, currently in alpha. For anything on this page, contact crystal.ho@talecompiler.com.
What we collect
- Account. If you sign in with Google we receive your Google account identifier, email address and display name. If you read without signing in, we create an anonymous session with a random identifier and no personal details attached.
- Reading progress. Which line of which story you have reached, and counts of how many times you interrupted and how many lines changed as a result.
- Saved sessions, only if you ask. The “Save progress” box is off by default. With it on, we store the rewritten lines your interrupts produced, alongside the original line. Turning it off deletes what was stored. This is available to signed-in accounts only.
- What you type into a story. Reading alone, the words you type are sent to the model providers below to generate a reply and are not stored by us. In a shared room they are stored with that room, because other members are shown what was said and what the character heard.
- Scripts you upload and the story files generated from them, if you publish a story.
- Rooms. Which rooms you joined, the character you claimed, and the rewrites made while you were there.
- Ordinary server logs kept by our host, including IP address and request times.
What we do not collect
No advertising trackers, no analytics scripts, no third-party cookies, and no payment details — nothing is for sale. We do not sell or rent anything we hold to anyone.
Who else sees it
Writing a story around what you type means sending it somewhere that can write. When you interrupt, we send the model provider your words, the character's current line, and a short slice of the surrounding scene. We send no account details with it — the provider does not receive your name, email or identifier.
- Model providers — Google (Gemini), Groq, and OpenRouter, which is a gateway that passes the request to whichever model host serves it. Each processes the text under its own terms and privacy policy.
- Supabase — database, sign-in and file storage.
- Fly.io — hosting.
- Google — sign-in, if you use it.
These providers are in the United States and elsewhere, so using TaleCompiler means your text is processed outside your country.
How long we keep it
- Anonymous sessions and everything attached to them are deleted about 30 days after they stop being used.
- Saved sessions stay until you untick “Save progress”, which deletes them, or until you ask us to remove your account.
- Stories you publish and their files stay until you delete the story.
- Room comments are deleted with the room.
Your choices
- Read without an account. An anonymous session keeps no personal details at all.
- Leave “Save progress” off, and nothing you do while reading is written down.
- Delete a story you published, which deletes its files.
- Ask us for a copy of what we hold about you, or to delete it, at crystal.ho@talecompiler.com. Depending on where you live you may have a legal right to both; we will honour the request either way.
Children
TaleCompiler is not intended for children under 13, and we do not knowingly collect their information. If you believe a child has signed up, write to us and we will remove the account.
Changes
If this policy changes we will update the date at the top. While the service is in alpha it is likely to change; material changes will be announced on the site.
See also the Terms of Service.