Talesake Privacy Policy

Talesake LLC | Effective October 23, 2026

Our promise to you

This Privacy Policy explains what information Talesake collects, why, who we share it with, and the choices you have. It covers the Talesake app at app.talesake.com, and our related services (the "Service").

1. Who we are

Talesake LLC is a Nevada limited liability company in Henderson, Nevada. We are responsible for the information described here. Contact us anytime at [email protected].

2. Where your stories live

Your recordings, photos, recipes, diary entries, and other stories ("Your Content") upload automatically to your family's Talesake account at full original quality. That account copy (your cloud copy) is the main copy; your device keeps only a small cache that clears itself, and you can download or export everything anytime with Download all. Stories stream from your account, and downloading them to your device is optional.

Encryption and recovery. Your Content is encrypted in transit and at rest. This is standard encryption, not end-to-end encryption: we keep a protected recovery copy of your family's key so we can help a Keeper restore the family's stories after losing devices, a spare key, or the recovery card. We check that a request really comes from the Keeper before we help. Nobody at Talesake watches your family's videos unless your family asks us to (for example, for support) or the law requires it, for example to act on a child-safety report. Investors never have access to your stories. Losing your Keeper code (spare key) or recovery card does not mean losing your stories.

Greetings. Greetings are private by default (only Keepers see them unless you share them) and are backed up to your account like every other story.

What the cloud copy can hold. Besides stories shared with Family Pass holders, the Keeper can choose to back up recordings privately; private backups are visible only to Keepers, never to Family Pass holders. Your account also keeps your storytellers' names and photos, chapter progress, story requests, diary and app settings (such as the AI host voice), so a new device signed in by a Keeper can restore them. All of it is encrypted in transit and at rest. Each family gets 50 GB. At 50 GB, new uploads need Premium or an extra storage add-on. With Premium, older videos move to lower-cost cold storage at 50 GB (still encrypted, and you can still watch and download them), and past 100 GB extra storage add-on blocks are needed (see our Terms).

Restoring from your own download. You can rebuild your library on a new device from the file Download all my stories made. This happens entirely on the device; nothing is sent to us.

3. How the AI host uses your answers

1. The device records video and audio and uploads them to your Talesake account.
2. The device decides when an answer is finished.
3. The audio of that answer is sent to Google's Gemini API on its paid tier (Google's "Paid Services"). With it we send a short text note so the host can ask a good next question and say names correctly: the name your storyteller goes by, the names of family members already saved in your account with their relationship and what they call the storyteller, the chapter title, the question just asked, and the other questions in that chapter.
4. Gemini writes the next question and lists the people the storyteller mentioned in that answer. A Gemini voice then speaks the question. The question and the names of the people mentioned come back to your device; the names are added to your family's list of people, which you can edit.
5. Talesake does not get or keep a transcript of the answer from the AI host. We do not store the audio we sent, the note, or the question on our servers; our logs keep only counts, timings and error codes.
6. Video is never sent to the AI host.

Our AI provider: Google. The AI host, the setup voice guide, the help chat and (when it launches) story search use Google's Gemini API, paid services. Under Google's Gemini API terms for paid services, Google does not use the prompts or responses we send, including your family's audio and names, to train its models or improve its products, and it processes them under its data processing terms as our service provider. Google logs prompts and responses for a limited time, only to detect and prevent abuse of its service and for any legally required disclosures, and it may store them briefly in any country where it operates. If Google or any other AI provider plans to change how it handles your data, or if we change AI providers, we will tell you before the change happens.

AI questions are labeled AI on your device. Real recordings are labeled Real. You can turn the AI host off in Settings; the app then uses the device voice and pre-written follow-up questions, and nothing is sent to Google for the AI host.

The setup voice guide

If you choose the voice guide during setup, the audio of your spoken answers to the setup questions (like names and what your family calls each other) is sent to Google's Gemini API on its paid tier so the guide can understand you and fill in the setup screens. What the guide heard is shown to you to check before anything is saved, and we do not store the audio. The same Google terms apply as for the AI host. Video is never sent. You can skip the voice guide and type instead.

3a. The help chat

The help chat is AI. It answers questions about using Talesake only from our own help articles, and it is labeled AI. It never sees your recordings, video, family details, codes or keys.

When you ask a question, the text you type (and up to two earlier questions from the same chat, so follow-up questions make sense) is sent to Google's Gemini service on its paid API tier, together with the help articles that match it. Gemini writes the answer. We do not keep questions the help chat answers. For rate limits we keep a random help-device number and a scrambled (hashed) network address for up to one day, and we use Cloudflare Turnstile to check that the chat is used by a person.

Questions the help chat cannot answer. When the help chat cannot answer a question, we keep that question for up to 90 days so we can see which help articles are missing, then it is deleted automatically. With it we keep a general topic (such as "story length limits"), the date and time, whether it was asked on the Keeper's device or on a phone, and whether it came from our test site. We do not keep a device number, network address or family account with it. During the pilot we keep the question text with contact details such as email addresses, phone numbers, long numbers and links removed. When Talesake launches more widely, we plan to also remove people's names as best we can, or keep only the general topic. Removal is automatic and may not catch everything, so please do not type private details into the help chat.

Please do not type codes, passwords, or private details into the help chat. If you choose Talk to a person, what you write in the help form (which may include the question you asked the chat) is sent to us as a support message.

3b. Story search (planned, not yet available)

A future version of Talesake will let your family search its own stories. To make that work, the audio of your stories will be transcribed automatically, and search will use those transcripts together with chapter and question titles. No person reads or watches anything to build search. Transcription will be done by Google's Gemini API on its paid tier, the same provider and terms as the AI host: Google does not use your family's audio or transcripts to train its models, and keeps prompts and responses only for a limited time to detect abuse and meet legal requirements. Only audio is sent. Video is never sent. Transcripts are stored in your Talesake account like your other stories and are labeled AI. We will update this section and tell you before story search is turned on.

4. Information we collect

We use no third-party analytics, crash-reporting or advertising tools in the Talesake app. Our own usage counts are described in Section 4b.

4b. Our own usage counts

Talesake keeps its own simple usage log on our servers (for example: the app was opened, a setup step was finished, a story was recorded or shared, a request was sent or answered, an invite was opened). Each record says what happened and when, with a random family id and the person's role (such as Keeper or family member). It never contains your stories, recordings, names, questions or answers. We use it to fix problems and to understand whether Talesake is helping families. Individual usage records are deleted automatically after 90 days. This log is never sent to Meta, Apple, Google or anyone else.

A Keeper can turn usage counts off in Settings ("Share usage stats (not linked to your name)"). After that we record nothing for the family except, once each, the date the family first shared a story and first sent a story request, so our totals of active families stay correct.

Pilot codes. If your community, care home or another partner gave you a pilot code and you enter it, we save it with your family and use it only to count pilot families separately in this same report.

4c. "How did you hear about us?"

During setup we may ask, optionally, how you heard about Talesake (for example, Facebook or Instagram, a friend or family member, a search, a nursing home or community). Skipping it changes nothing. We use your answer only to measure which of our marketing works, and we look at it only in totals. It is kept on our own servers with your family's account, never used to target ads, and never sent to Meta, Apple or any other company.

4d. Where you came from, invites, emails, gifts and marketing permission

Where you came from. When a family is set up, we save how it found Talesake: the campaign tags in the link (for example utm_source), an ad click id if the link had one, whether it was set up in the app or on the web, and any gift, tester, referral, invite or pilot code. We use this only in our own reports, to see which of our marketing works. We do not send it to Meta, Google or anyone else. We store ad click ids only and delete them after 90 days.

Invites. When a Keeper or family member creates an invite, we keep the invite code, which family member created it (any storyteller name in an invite is stored encrypted), when, and how many times it was opened and used to join, so the family can see whether an invite worked and we can count families that joined through invites. The people you invite are not added to any mailing list.

Emails you ask for. If a family member gives us an email address and turns on "my request was answered" emails, we use that address only for those emails. They never contain your stories, questions or names, and every one has a one-tap link to stop them. You can turn them off or remove the address in the app.

Gifts. When someone gives a gift we keep the gift details (plan, the recipient's first name, the giver's name and message, the delivery date and the giver's email if they give it) to make the gift card and let the recipient redeem it. Gift codes do not expire. Gift purchases are sold through Stripe, as described in our Terms.

Gift and tester codes. For each gift or tester code we keep the plan, whether and when it was redeemed and which family redeemed it. Tester codes (given to friends, family and early testers) are labeled as tester codes so tester families are counted separately from paying and gift families in our reports.

Marketing permission. If your family offers a clip for Talesake's marketing, we keep a record of that permission (names of the people who agreed, the clip description, where and how long it may be used, and any withdrawal). It is separate from using Talesake, and anyone can withdraw it at any time.

4e. Proof of permission recordings

Permission note. When a storyteller records the permission note, Talesake saves a consent record on our servers so the family can later show that permission was given. The record holds the storyteller's internal id (not their name), the family, the date and time, which version of the permission wording was used, how long the recording is, about how long the wording takes to read, whether the whole text was shown on screen (or scrolled to the end), the device type and the app version. It also holds a fingerprint of the video file (a SHA-256 hash). The hash shows whether a file is exactly the one that was recorded. Nobody can rebuild the video from it. The permission note is stored in your account, encrypted like your other stories, so it survives if the device is lost. Staff do not watch it except as described in Section 2.

Tester marketing answer. If a storyteller in a tester family records the optional marketing answer, the family is choosing to send that clip to our team, who will watch it to confirm the answer. The card says so before recording. We keep the same kind of record and hash for it.

These recordings and records cannot be deleted from the app, by trash clean-up, or when old cloud copies are removed. Re-recording adds a new version and keeps the earlier one. Withdrawing marketing permission ("Turn off" in Settings) is saved with its date, and the recording stays as the record of what was agreed and when. If a family closes its account, the consent records and backups are kept as described in Section 8.

5. How we use information

• To run your account and family access, and send invitations you ask us to send.
• To confirm the Family Keeper's email, help you if you lose your spare key, warn you if your recovery card is used, and send receipts. If you lose your spare key and recovery card, we can help you restore access after checking that you are the Keeper.
• To store your stories in your Talesake account and help you restore them.
• To power the AI host, as described in Section 3.
• To process payments, renewals, shipping, and returns.
• To send service messages, such as renewal reminders, security notices, and storage reminders.
• To keep Talesake safe, fix problems, and prevent abuse.
• To understand how Talesake is used and which of our marketing works, through our own usage counts, the optional "How did you hear about us?" answer, where-you-came-from details, and invite, gift and tester code counts (Sections 4b to 4d). Only in our own reports, never for ads.
• To send "request answered" emails to people who turn them on.
• To follow the law.

We will only send marketing emails if you choose to receive them, and you can stop them anytime. We do not send marketing emails today.

6. What we never do

• We never sell your information or Your Content.
• We never mine Your Content or use it for advertising.
• We never use Your Content to train AI, and we do not let our providers do so.
• We never send your video to the AI host.
• Nobody at Talesake watches your family's videos unless your family asks us to or the law requires it (Section 2), and investors never have access to them.
• We do not show ads, and we do not use third-party analytics or advertising trackers. We never send your usage counts, where-you-came-from details or ad click ids to Meta, Google or any other ad company.

7. Who we share information with

We share information only with providers that help us run Talesake, under contracts that limit how they use it.

We use Cloudflare Turnstile to protect our service from bots. Turnstile's use of data is described in Cloudflare's Turnstile Privacy Addendum: https://www.cloudflare.com/turnstile-privacy-policy/.

We may also share information:

• When the law requires it. We respond only to valid legal process. We can only provide what we hold: this can include your stories as well as account information. We will tell you first unless we are legally barred.
• To protect people. For example, reporting apparent child sexual abuse material to NCMEC as required by law.
• If Talesake is reorganized or sold. Any new owner must keep the promises in this policy.
• With your permission.

8. How long we keep information

• Account details: while your account is open, then deleted within 90 days of closing, except what we must keep.
• Unfinished sign-ups: a sign-up link works once and expires after 30 minutes. Every sign-up record, finished or not, and the email in it, deletes itself 24 hours after it starts. Once your family is set up, your email is kept with your account.
• Stories after you cancel: kept for good on a free view-only plan, with no end date, so your family can keep watching and exporting them. If Talesake ever shuts down, we will email you at least 90 days before and give you a one-click export of every story as plain MP4 files (see our Terms, Section 16, and talesake.com/promise).
• Billing records: as long as tax and accounting laws require.
• Consent records and permission recordings (Section 4e): kept while the account is open and, after it closes or permission is withdrawn, for as long as needed to prove consent. They are not removed by trash clean-up or the removal of old cloud copies.
• Technical logs: 30 days, unless needed for security.
• Usage records (Section 4b) : deleted automatically after 90 days.
• Ad click ids (Section 4d): deleted after 90 days. Other where-you-came-from details, invite counts and gift and tester code records: while your account is open. Gift codes do not expire, so an unused gift code's record (plan, who it is for and from, and the email addresses given) is kept until it is redeemed.
• Marketing permission records: while the permission is in effect and, after it is withdrawn, for as long as needed to prove consent.
• Help chat questions it could not answer : up to 90 days, then deleted automatically. Questions it answered are not kept.
• Backups: deleted data may stay in our backups for up to 35 days.

9. Cookies and similar tools

We use only the cookies and local storage needed to sign you in, remember your settings, and keep the app working offline. We do not use advertising or analytics cookies, pixels or trackers from other companies. The app may hold a few usage counts in your browser's local storage until it sends them to our own servers (Section 4b); nothing is shared with other companies. We honor Global Privacy Control signals, although we do not sell or share data for advertising in the first place.

10. Your choices and rights

• Download: use Download all anytime to get everything at full quality.
• See and correct: view and fix your account details in settings, or ask us.
• Delete: a Keeper can delete any story, or the whole account. You can also email us.
• Delete a story: a Keeper can delete any story from your account at any time.
• Stop sharing a story: a Keeper can stop sharing any story with Family Pass holders at any time; it stays in your account as a private backup.
• Leave a family: a Family Pass holder can leave at any time.

How to make a request

Email [email protected] with "Privacy request" in the subject. We will check that the request is really from you, usually by confirming through your account email. We will respond within 45 days. You may use an authorized agent where the law allows. We will never treat you differently for using your rights.

A note on shared family content. Stories belong to the Family Keeper. If a Family Pass holder or a person who appears in a recording asks us to delete something, we will help connect them with the Keeper. We will usually leave the decision to the Keeper unless the law requires otherwise.

11. Privacy rights by state

Some states give you extra rights. We give these rights to all users, wherever they live.

California

Under the California Consumer Privacy Act, as amended, California residents may ask to know, access, correct, and delete personal information, and to opt out of its sale or sharing. We do not sell or share personal information, as those terms are defined, and have not done so in the past 12 months. We do not use sensitive personal information to infer characteristics about you. The categories we collect are in Section 4, the purposes in Section 5, and who receives it in Section 7.

Nevada

Nevada residents may ask us not to sell their covered information. We do not sell it. You may still send a request to [email protected].

Other states

Residents of states such as Colorado, Connecticut, Virginia, Texas, Oregon, and others may have similar rights to access, correct, delete, and get a copy of personal information, and to appeal our decision. To appeal, reply to our response with "Appeal" in the subject.

12. Children

Account holders, Family Keepers, and Family Pass holders must be 18 or older. Talesake is not directed to children under 13, and we do not knowingly collect personal information from them.

Children may appear in family recordings, or watch stories with a parent or guardian who holds a Family Pass. That content belongs to the family and is stored in the family's Talesake account. If you believe a child has given us personal information directly, contact us and we will delete it.

13. Keeping information safe

We protect information with encryption in transit and at rest, a protected recovery key, limited staff access, and careful choice of providers. No system is perfectly secure. If a security incident affects your personal information, we will tell you as the law requires.

14. Where we operate

Talesake is based in the United States and offers the Service in the United States. Information is processed in the United States and wherever our providers operate.

15. Changes to this policy

If we make an important change, we will tell you by email or in the app at least 30 days before it takes effect. We will never change our promise about selling, mining, or training AI on your stories without your clear consent.

16. Contact us

Talesake LLC, Henderson, Nevada

Email: [email protected]

Questions? Write to the Talesake team at [email protected] or use Get help.