Privacy Policy
1000 Lives
Last Updated: 2026-09-29
Data Controller:
GigaDuck OÜ
Tornimäe tn 5, 10145 Tallinn, Estonia
Registry code: 17501858 (Estonian Business Register)
Email: privacy@gigaduck.ai · General: info@gigaduck.ai
This policy covers the 1000 Lives app for iPhone and Android, the website 1000lives.app, and the 1000 Lives waitlist on it. 1000 Lives is published by GigaDuck OÜ (“we,” “us,” “our”).
Overview
1000 Lives is a language-learning app built around spoken stories. You speak to characters in the language you are learning; AI turns your voice into text, writes the characters’ replies, reads them aloud, and illustrates the scenes. To do that, 1000 Lives runs a small backend of its own and uses specialist AI providers. This policy explains exactly what that means for your data.
Key points:
- Your account is just an email address and a few answers. You sign in with a one-time code sent to your email. We also ask for your name, age, languages, and, optionally, your gender, so the characters can speak to you properly.
- Your voice is transcribed, not kept. A recording is sent for speech recognition and turned into text. We do not save your recordings on our servers, and we never use your voice to identify you.
- Your stories are saved to your account — the conversations you have, the Lives you create, and the phrases you save for Practice — so you can come back to them.
- AI providers process what you say to make the app work. They act on our instructions, and we ask our text provider to avoid services that store or train on your data (Section 5).
- No advertising, no tracking, no analytics tools in the app.
- You can delete your account in the app at any time. That deletes your profile, stories, conversations, saved practice, and generated images.
- Our database is hosted in the EU (Ireland).
1. The Website and the Waitlist
The website
1000lives.app has no advertising and no tracking. It sets no cookies of its own and uses no tag manager, advertising or tracking cookies, fingerprinting, or third-party embeds. Fonts, images, the film, and our own page scripts are served from 1000lives.app.
Hosting. The site is served by Cloudflare (Cloudflare, Inc.), our hosting and content-delivery provider, acting as our processor. Cloudflare processes your IP address and technical request data to deliver and secure the site. It gives us aggregate traffic figures and, for a short rolling period (on our current plan, up to seven days for sampled request data and up to 24 hours for blocked security events), sampled request records that can include the requested URL, IP address, browser details, and time. Cloudflare may set a strictly necessary security cookie if it has to challenge a request. We keep no separate copy of this traffic data.
Visitor counts. We use Cloudflare Web Analytics, a cookieless measurement tool from our hosting provider, to see how many people visit which pages and how fast they load. It sets no cookies, stores nothing in your browser, and does not identify or fingerprint individual visitors; we see only aggregate figures. Cloudflare may add a small measurement script (from static.cloudflareinsights.com) to the pages it serves; a content blocker stops it without affecting the site.
The waitlist
If you join the waitlist before launch, we collect:
- the email address you enter;
- the time you gave consent; and
- the version of this policy shown with the form.
We use this only to email you about 1000 Lives early access and launch. The waitlist does not create an app account, does not subscribe you to anything else, and sends no automatic confirmation email. Submitting the same address again updates its consent time instead of creating a second entry. We do not store your IP address or browser details in the waitlist.
The form sends your address from your browser to our backend at Supabase (Section 5). As with any web request, our hosting providers process your IP address and technical request data to deliver it and protect the service against abuse.
You can withdraw your consent, or ask us to correct or delete your address, at any time by emailing privacy@gigaduck.ai. We may need to confirm the address is yours before acting.
2. Your Account
To create an account, 1000 Lives asks for:
| Data | Why |
|---|---|
| Email address | To sign you in with a one-time code and to contact you about your account |
| Name | So the characters can address you |
| Age | 1000 Lives is for adults (Section 13), and age helps the stories fit you |
| Gender (optional: male, female, or prefer not to say) | Many languages change their grammar depending on who is spoken to; this lets the characters address you correctly and pick a matching voice when your own lines are read aloud |
| Native language and the language you are learning | To run lessons and stories in the right languages |
| Settings | Speaking speed, difficulty, reading aids, correction preferences, narrator and tutor voice, and optional learning notes you write for each language |
You can change these in Profile. Your answers during sign-up are kept on your device until your account is created, then saved to your account.
3. Voice, Transcripts, and Conversations
Recording. 1000 Lives uses your microphone only while you are recording — when you press to speak, or to dictate an idea or a question. You decide when a recording starts and stops.
Speech recognition. Each recording is sent from the app to our backend, which forwards it through OpenRouter to a speech-recognition model (currently Voxtral, by Mistral AI) and receives the text back. We do not store the recording on our servers. On your device, a recording exists only for the session it belongs to. We do not create voiceprints or use your voice to identify you.
Character replies. Your transcribed words, the recent conversation, and the story context are sent to an AI text model through OpenRouter to write the character’s reply. To personalise the conversation, these requests can also include your name, age, gender (if you gave it), your languages and level, and your learning notes.
Speech. The text of each line to be spoken — the character’s reply, narration, or a suggested phrase — is sent to a text-to-speech provider (currently Inworld AI), which returns audio. Spoken audio may be kept on your device so you can replay it.
Learning help. Translations, corrections, suggestions, grammar explanations, and answers from the coach are produced the same way: the relevant text is sent to the AI text model and the result is returned to you.
What is saved. The transcripts of your conversations, the characters’ replies, and related story details (for example, what happened in a chapter and how it ended) are saved to your account so you can resume a story, continue it in a new chapter, and review it in Practice.
Please don’t say or type sensitive information about yourself or others — such as health details, financial information, or passwords — in a story. 1000 Lives doesn’t need it, and anything you say is processed as described above.
4. Your Stories, Progress, and Saved Practice
- Lives you create. When you describe a story idea (typed or spoken), we save your idea and the story that is generated from it — title, characters, chapters, and the look you chose.
- Story history. We keep a record of the Lives and chapters you have played and when, so the app can show your library and pick up where you left off.
- Saved practice. Words and phrases you choose to save are stored with their translation, explanation, and the sentence they came from.
- Story images. Images generated for your Lives are stored at unlisted, hard-to-guess web addresses so the app can load them quickly. They are not listed or searchable anywhere, but anyone who has an image’s exact address could open it. They are deleted with your account (Section 11).
- Usage limits. To prevent abuse and control costs, we keep counters of how often an account requests story ideas and images. They contain no story text. Per-account counters are deleted after two days; the record of images made for a particular story is kept with that story and deleted with it.
1000 Lives does not build a learning profile about you, run scheduled reviews, or rank you against other people.
5. Who Processes Your Data
We use the following providers to run 1000 Lives. They process data on our behalf and under our instructions (as our processors), unless marked otherwise.
| Provider | What it does | Data it receives |
|---|---|---|
| Supabase (Supabase, Inc.) | Our backend: account sign-in, database, file storage, and server functions. Our project is hosted in the EU (Ireland). | Everything saved to your account (Sections 2–4) and the waitlist (Section 1); sign-in emails are sent through it |
| OpenRouter (OpenRouter, Inc.) | Routes our AI requests to the model that handles them | Your recordings for transcription; the text sent for replies, learning help, and story writing; descriptions used to create images |
| AI model providers reached through OpenRouter — currently OpenAI (text), Mistral AI (speech recognition), and Recraft (images) | Run the AI models | The same data OpenRouter forwards for that request |
| Inworld AI (Inworld AI, Inc.) | Text-to-speech | The text to be spoken |
| Google (Google LLC) — backup only | Text-to-speech and image generation if we switch to it as a backup | The text to be spoken, or image descriptions |
| fal (Features and Labels, Inc.) — backup only | Image generation if we switch to it as a backup | Image descriptions |
| Cloudflare (Cloudflare, Inc.) | Hosts 1000lives.app and counts visits without cookies | Technical request data from visiting the website (Section 1) |
| Google Workspace (Google LLC) | Our email | Messages you send us, and the emails we send to the waitlist |
For text requests, we ask OpenRouter to route only to providers that do not collect or store your data for their own purposes, such as training. This is a routing setting, not a guarantee that no provider keeps any data; each provider’s own retention terms apply. We may change which model or provider handles a task. Before we use a provider not named in this section, we will update this policy.
App stores. Apple (App Store) and Google (Google Play) distribute the app and, if 1000 Lives offers purchases, handle payment. They act as independent controllers under their own privacy policies. We do not receive your payment-card details. The stores give us sales reports (for example, purchase date, price, and country) and aggregate statistics such as download counts and anonymised crash reports.
We do not sell your data or share it with advertisers.
6. Data on Your Device
The app keeps some data on your phone: your sign-in session, settings, the answers you give during sign-up, a small copy of your library so it loads quickly, cached images, and cached spoken audio. Signing out removes your account’s library copy and cached private images from the device; deleting the app removes everything it stored.
7. What We Don’t Collect
- No advertising identifiers, tracking, or fingerprinting.
- No analytics or crash-reporting tools in the app. Apple and Google give us aggregate statistics about the app, as described in Section 5.
- No precise location, contacts, or photos.
- No voice recordings kept on our servers.
When you delete your account, we keep only a daily count of how many accounts were deleted. It contains nothing about you.
8. Why We Process Your Data (Legal Bases)
| Processing | Legal basis (GDPR Art. 6(1)) |
|---|---|
| Keeping the waitlist and emailing you about early access and launch | (a) consent — you can withdraw it at any time |
| Running your account and the app: sign-in, transcription, conversations, speech, images, learning help, saving your stories and practice | (b) contract — providing the service you asked for |
| Using your name, age, gender, languages, and learning notes to personalise conversations | (b) contract — these answers exist to shape your lessons; gender is optional |
| Usage limits, security, and preventing abuse | (f) legitimate interest — keeping the service safe, available, and affordable |
| Serving and securing the website, and counting visits in aggregate | (f) legitimate interest — delivering a fast, safe website and knowing how many people it reaches |
| Sales records and accounting, if you make a purchase | (c) legal obligation — accounting and tax law |
| Answering privacy requests | (c) legal obligation — the GDPR itself |
Your right to object. Where we rely on legitimate interest, you can object at any time on grounds relating to your particular situation by emailing privacy@gigaduck.ai. We then stop unless we have compelling grounds that override your interests, or the data is needed for legal claims.
AI in 1000 Lives creates stories, speech, and feedback for you. It does not make decisions about you that have legal or similarly significant effects.
9. International Transfers
Our database is hosted in the EU (Ireland). Some of our providers are based in, or process data in, the United States and other countries outside the EU/EEA — including Supabase for support and operations, OpenRouter, the AI model providers it routes to, Inworld AI, Google, fal, and Cloudflare. Where data leaves the EU/EEA, it is protected by the safeguards in each provider’s data-processing terms: the EU–U.S. Data Privacy Framework where the provider is certified, or the European Commission’s Standard Contractual Clauses. You can ask us for details at privacy@gigaduck.ai.
10. How Long We Keep Data
- Waitlist: until the early-access and launch emails are complete, and no later than 90 days after 1000 Lives publicly launches. We delete an address earlier if you withdraw consent or ask us to.
- Account data, stories, conversations, and saved practice: for as long as you have an account. Deleting your account deletes all of it (Section 11).
- Voice recordings: not stored on our servers. The speech-recognition request is handled under the provider’s own retention terms.
- Usage-limit counters: per-account counters two days; per-story image records as long as the story exists.
- Sign-in sessions: while you are signed in, our authentication system (Supabase) keeps a record of your sign-in session, including the IP address and device/browser information it was started from, and a security log of sign-in events. Session records are removed when the session ends or you delete your account; the security log is kept for a limited period to protect accounts against misuse.
- Technical logs: our hosting providers keep server logs for a short period. Our own server code is written so that it never logs your recordings, transcripts, conversations, or sign-in tokens.
- Backups: our database provider keeps backups for a limited period. Deleted data can remain in a backup until that backup expires; it is not restored into the live service.
- Purchase records: as long as accounting and tax law requires (in Estonia, seven years).
11. Deleting Your Account
Go to Profile → Account → Delete account and confirm. This permanently deletes your account, profile, settings, stories, conversations, saved practice, and the images generated for your Lives. Images are removed right away, with a final clean-up pass within a few hours to catch anything still being created at the moment you deleted. Deletion cannot be undone.
If you can’t use the app, email privacy@gigaduck.ai from the address on your account and we will delete it for you.
Deleting your account does not cancel a store subscription, if 1000 Lives offers one; manage that in your App Store or Google Play settings.
12. Your Rights
Under the GDPR you have the right to access your personal data, to correct it, to have it erased, to restrict or object to its processing, and to receive it in a portable format (portability). Where we rely on consent, you can withdraw it at any time; this does not affect processing before the withdrawal. Much of your data can be viewed, changed, or deleted directly in the app. For anything else, email privacy@gigaduck.ai. We respond within one month, and exercising your rights is free. We may ask you to confirm your identity first.
Complaints. If you think we have handled your data wrongly, please contact us first — we read and answer. You also have the right to complain to a supervisory authority. Our lead authority is the Estonian Data Protection Inspectorate:
Andmekaitse Inspektsioon — Tatari 39, 10134 Tallinn, Estonia · info@aki.ee · +372 627 4135 · aki.ee
If you live or work in another EU/EEA country, you may instead complain to the supervisory authority there.
13. Minimum Age
1000 Lives is for adults aged 18 and over, and the app does not let anyone under 18 create an account. The waitlist is also for adults. If we learn that someone under 18 has given us personal data, we delete it. If you believe this has happened, email privacy@gigaduck.ai.
14. Changes to This Policy
We will update this policy when 1000 Lives changes in a way that affects your data — for example, if we introduce purchases or let you connect your own AI account to pay for your AI usage. We will change the “Last Updated” date and publish the new version at 1000lives.app/privacy. If a change is significant, we will tell you in the app or by email before it takes effect.
15. Contact
Privacy: privacy@gigaduck.ai
Data Controller: GigaDuck OÜ, Tornimäe tn 5, 10145 Tallinn, Estonia · Registry code 17501858 · General: info@gigaduck.ai