Last updated: 7 October 2026
TalePatch makes personalised picture books for children and their families using AI. A parent or legal guardian creates and controls the account. This policy covers the TalePatch app and talepatch.com, including information children enter while making stories.
Who we are
TalePatch is operated by Apex Forge Tech Inc., 9811 203 Street, Langley, British Columbia V1M 3E3, Canada. We are responsible for the personal information described here. For privacy questions or requests about your child's information, contact our privacy contact at privacy@talepatch.com, call +1 778-917-3968, or write to the address above.
The short version
- A parent or legal guardian must consent and be verified before TalePatch collects anything about a child.
- Story ideas, the reader's age and any story name the child picks leave the device so our providers can write, illustrate, check and narrate the book. A reader's own name is saved to your account, never sent to a provider.
- Readers and books are stored on your device and in your account, so the same readers and books appear on every device you sign in on. Creating a book needs the internet, and so does opening it for the first time on another device.
- We do not sell personal information or use family stories for advertising or to train our own AI models. We do not display ads in the current app.
- You can request access, correction, deletion or an end to further collection of your child's information. Account deletion is available in the app and at talepatch.com/delete-account.
Parents and children
Accounts are for adult parents and legal guardians. Children use the app with their supervision. The mobile app uses a parent password for parent settings, purchases and page reports. This control helps restrict access; it does not verify a person's age or relationship to a child.
Before TalePatch collects any information about a child, a parent or legal guardian reviews our parental notice in the app, consents to it, and is verified — either through Kids Web Services, which emails the parent a link to a payment-card check, or with a signed form our team reviews. Until verification is complete, TalePatch collects nothing about the child, and the free library can still be read together. Consent can be withdrawn at any time in Settings → Parental consent. Accepting these documents, verifying an email address or setting a parent password is not, by itself, parental consent. Contact us if you believe information was collected without the required parental permission.
Children do not have public profiles, chat or a public posting feature in TalePatch. Please use nicknames and pretend story names. Do not include addresses, phone numbers, email addresses or other people's full names in story ideas. Our filters remove some detected contact details before AI story processing, but cannot detect every personal detail and do not prevent the original submission from reaching our server.
Information and purposes
| Information | Purpose and destination |
|---|---|
| Parent email, password, account ID and optional display name | Account creation, sign-in, management and recovery through Supabase. Passwords are sent securely to the sign-in service and stored there as hashes. Sign-in is email and password only; we do not offer Google or Apple sign-in. |
| Purchase identifiers, tokens or receipts, plan, dates and transaction records | Our payment verification service and Supabase use these to apply subscriptions and page credits, handle store notifications and prevent purchase replay. Google Play or Apple processes payment; we do not receive card or bank details. |
| Usage and allowance records | Supabase stores book/page usage, reservations and records of reaching an allowance limit. These run the allowance and help us understand demand and plan limits. |
| Reader first name or nickname, age and colour | Stored on the device for the reader picker and greetings. Adding a reader is a parent-gated action. The reader's name is not sent to our server or our providers. Age goes with story requests so the writing suits the reader. |
| Optional story name | A parent may give a reader a story name: the name they star under when they choose to be the hero. It is stored on the device and, when the child picks it, sent with the story like any other answer. Our server also sends it to our voice provider to make a spoken clip the app plays while a story is being made. A nickname works well. |
| Story choices and ideas, including transcribed speech, and generated stories | Our backend and AI providers use these to write, check, illustrate and narrate books. This includes derived picture prompts, character references, page text and generated media. Private server working records support recovery after interruption. |
| Optional microphone input | Offered only if you turned it on when giving consent. The device's speech-recognition service processes audio and returns text to TalePatch. It may send audio to its provider, such as Google or Apple; the app does not require recognition to happen only on the device. Our story backend receives the transcript, not the microphone recording. Deny microphone permission and type or use the available choices instead. |
| Parental consent and verification | We keep a record of the notice version you consented to, the choices you made, how you were verified and the result, a Kids Web Services transaction identifier or a form code, and a hashed copy of the account email. Kids Web Services receives the parent's email address and the child's country to run its check; a signed form is reviewed by our team. |
| Optional page reports | Supabase receives the account ID, book/page identifiers, reason, note, page text and available image reference and generation details so we can investigate. A report identifier and reason may appear in logs and Sentry alerts. |
| Book share links ("Send this book") | Creating a share link is a parent-gated action. The link opens an unlisted preview page showing the book's cover and first page, with the child's name blanked out; anyone with the link can view it. Deleting the book or revoking the link removes the preview. If the link leads to a new reader's signup, we may attribute that signup to the sender to apply a referral reward. |
| Support and privacy messages | Our email services receive your address and the information you send so we can reply and handle requests. Avoid sending children's personal details unless needed for the request. |
Diagnostics and website information
Sentry receives crash/error reports, device and app information, session information and sampled performance traces to diagnose reliability problems. Reports can contain activity breadcrumbs, request metadata, error messages and identifiers such as a book identifier. The app and backend remove credentials, email addresses, and the names, story text and book titles they recognise before a report is sent; this is not a guarantee that all free text is removed. Backend reporting disables request-body and local-variable capture. Crash reporting and Sentry performance sampling are separate from the app's optional diagnostics preference.
Hosting and security logs can contain IP addresses, request paths, timestamps, browser/device information and account or request identifiers. Railway hosts the story backend, Supabase hosts account/database services, and Vercel hosts the website. Cloudflare provides domain/DNS services. Infrastructure handling a request can process connection information.
Website sessions use cookies to maintain sign-in. Account forms send information through Vercel to Supabase; the signed-in dashboard requests account and allowance information.
The current app's optional usage/performance preference controls additional local diagnostics and, when accepted, a small set of usage events sent to our server so we can understand which features are used — for example, that the plans screen was opened, which is linked to your account, or that a library book was opened, which is counted without linking it to your account. Its Firebase upload integrations are disabled. It does not stop account, story, allowance, security or Sentry processing. We do not request location, contacts, camera access or a child's photo library in the story-making flow, and do not use advertising identifiers for advertising.
Providers and transfers
| Provider | Information and role |
|---|---|
| Supabase | Authentication, account data, parental consent records, purchases, usage, reports and, when configured, generated media storage. |
| Railway | Story requests, private recovery records, generated media and backend logs. |
| AI story services: Anthropic, OpenAI, Replicate, Runware and Alibaba Cloud (Model Studio, Singapore and United States) | Story inputs, reader age, any story name used, story text, picture planning, reference pictures and generated pictures, to plan and write the story, paint its pictures, narrate it and time its words, speak the story name, and check that story ideas, text and pictures are suitable. Which of these companies does each job can change from book to book, for example when one is busy or a better model becomes available. Before a company not listed here receives a child's information, we ask for parental consent again. |
| Kids Web Services | The parent's email address and the child's country, to verify the parent or legal guardian. |
| Sentry | Diagnostics described above. |
| Vercel and Cloudflare | Website hosting and domain/network services described above. |
| Account-email and support-email providers | Parent email addresses and service/support messages. |
| Google and Apple | Device speech recognition and app-store billing. |
We send information to providers to deliver and secure these features. Their processing, retention and any independent use also depend on the applicable service terms and settings. We do not promise that every provider has identical retention or model-training terms. Contact us for information about the providers handling your request.
Information can be processed outside Canada, including in the United States and Singapore, where local authorities may have lawful access. Applicable privacy obligations and required transfer arrangements continue to apply. We may disclose information when legally required or necessary to protect safety, and in a lawful business transfer subject to applicable privacy protections.
Retention and deletion
| Records | Current retention and deletion behavior |
|---|---|
| Readers and books in your account | Kept until you delete the book, the reader or the account. Deleting a reader deletes their books. Each device also keeps its own copy of what was opened on it until you delete it there, remove the account's stories in the app, or uninstall (subject to device backup behavior). Settings are stored locally. |
| Server pictures and narration | Kept while the book is in your account's library. When you delete a book the app asks our server to delete them at once, and the retention sweep (every six hours) removes anything left behind. Media for a book that was never saved to an account becomes eligible for deletion after 14 days without a new or replaced file; character reference images of such a book after 30 days. Spoken story-name clips become eligible after 30 days. Deletion occurs on a later successful sweep, not at the exact age threshold. |
| Private story recovery records | Job records are reusable for six hours and draft checkpoints for 24 hours. Expired files are pruned when later generation writes occur; physical deletion can take longer during inactivity. |
| Book share links and previews | The preview and its picture copy are removed when the sender deletes the book or revokes the link. The storage sweep also removes any leftover picture copy for a link that is gone, within about one sweep interval. |
| Parental consent records | Kept while we rely on the consent and for 24 months after it is withdrawn or replaced, or the account is deleted, so we can show what was agreed. A scheduled job then deletes them. |
| Account, purchase, usage and report database records | Retained for account functionality and removed through account deletion. Additional operational records are cleaned up separately; failed cleanup can require follow-up. Stores retain their own transaction records under their policies. |
| Logs, diagnostics, email and provider backups | Separate provider retention and deletion processes apply. These are not all erased by deleting an account. Contact us to request review or deletion of information that remains. |
Your account's library is what lets a book open on another device; it is not a backup of a device, and a book you delete is deleted from the account and from our server. Account deletion removes the account's readers and books at once; media, recovery files, logs or backups follow the processes above and any necessary follow-up. We do not retain children's information for an unrelated future purpose.
Your choices and rights
- Review or obtain a copy: view readers and books in the app on any device you sign in on; contact privacy@talepatch.com for other server-held information about you or your child.
- Correct: remove a reader and add them again with the right details, or change your display name on the website; contact us for other corrections.
- Delete: to remove one reader and the books made for them, choose Remove a reader on the reader picker. To delete the account, open Parent settings on the reader picker, enter the parent password, then Account → Delete account; on the website use Delete your account. Contact us if you cannot sign in or want particular child information removed.
- Withdraw consent: in Settings → Parental consent. New stories stop and nothing more is collected about your child; a story already being made finishes or fails on its own; information already stored stays until you delete it or its retention period ends. Removing a reader or withdrawing consent does not by itself remove information already sent to providers; contact us and we will ask them. Some features cannot work without the information needed to provide them.
- Cancel payments separately: account deletion does not cancel a Google Play or Apple subscription. Cancel through the store to prevent renewal.
We check that requests come from someone entitled to act for the account or child. Applicable law may provide access, correction, deletion, consent-withdrawal, objection, restriction or portability rights. Contact us first with a privacy concern. You may also complain to the Office of the Information and Privacy Commissioner for British Columbia, the Office of the Privacy Commissioner of Canada, or your local supervisory authority, as applicable.
Where European or UK law applies, the basis for each use must reflect its purpose: providing the parent's account/service, consent where required for children's information, security interests where permitted, or a legal obligation. A contract with a parent does not remove separate children's-privacy requirements.
Security and changes
We use encrypted connections, protected account sessions, restricted server access and signed media links. No system or parental gate guarantees against all access or disclosure.
We update the date above when this policy changes. Material changes require appropriate notice; where new permission is legally required, it must be obtained before changed collection or use. Continued use alone does not replace required parental consent.
Contact
- Operator: Apex Forge Tech Inc.
- Post: 9811 203 Street, Langley, British Columbia V1M 3E3, Canada
- Telephone: +1 778-917-3968
- Privacy: privacy@talepatch.com
- Support: support@talepatch.com
- Account deletion: talepatch.com/delete-account