Privacy

What we collect

Your account

An email address, which identifies the account and receives sign-in, password-reset and verification mail. A password, stored only as an Argon2 hash. A random account token that binds App Store purchases to the account. A timestamp recording that you confirmed being 13 or older — no birth date is collected. The devices you are signed in on: a device name, a token hash, and created and last-used times.

Reference recordings and transcripts

The recording you upload as a voice reference, plus the transcript of the words you spoke. Together they let the speech engine clone that voice when you ask for audio. They are kept until you delete the voice or your account.

Document text

Text you upload or paste to be read aloud. It is the input to generation, and it is kept until you delete the document or the account.

Generated audio

The audio the service produces for you, kept so you can play it back and download it, until you delete it or the account.

Billing and usage records

A usage ledger (characters per generation, timestamps) to enforce your allowance; idempotency records, so a safe retry never charges you twice; your subscription state and verified Apple transactions (transaction ids, product, dates, account token) to grant Pro; and Apple server notifications, stored as a type and a hash of the signed payload, with no account link.

Security and operational records

One-use password-reset and verification tokens, stored hashed and valid for 1 hour and 7 days respectively. Activity events — sign-ins, assets created or deleted, generation outcomes, small details such as titles and error text — kept for 365 days to run the service, investigate abuse and answer support requests. Server logs with IP addresses, request paths and job ids, kept for 30 days. In-memory rate-limit counters (IP address and email address) that vanish on restart.

We do not collect location, contacts, advertising identifiers, analytics or crash-reporting data, or payment card details — Apple handles payment. We never ask for your birth date.

Where it is processed and who processes it

The app server and its database run on Amazon Web Services in the United States (Oregon region). Cloudflare provides DNS, TLS and proxying in front of the site and API, and processes traffic and IP addresses on its global network.

Reference recordings, document texts and generated audio are stored in Google Drive on the operator's account, on Google's global infrastructure. You do not connect your own Drive.

For every voice you create, the reference recording and its transcript are sent to the operator's speech engine, which runs on the operator's own machine in mainland China, reached over an encrypted Tailscale link. For every generation, the text being read is sent to that engine, and it returns the audio. Tailscale carries only the encrypted link between the servers — coordination metadata, not your content.

Password-reset and verification email is sent through Resend in the United States. Payments and subscription notifications go through Apple, which processes them under Apple's own privacy policy.

Because the speech engine is in mainland China, and Google, Cloudflare and Resend run United States or global networks, your data is transferred to countries other than your own — but only as described in this policy.

No model training

Reference recordings, document text and generated audio are not used to train any model. The speech engine performs zero-shot cloning at generation time from the reference you supplied; nothing is retained for training.

How long we keep it

Content is kept until you delete it or delete your account. Reset and verification tokens expire after 1 hour and 7 days and are useless afterwards. Activity events are kept for 365 days; server logs for 30 days. A database backup made by hand before a schema migration is kept for at most 7 days. Text sent for generation becomes a job on the speech engine; how long the engine host keeps its job artifacts is outside this app's control. Apple notification records (a hash, with no account link) are deleted after 730 days.

How to delete it

You can see and delete everything through the app. Deleting a voice, a document or an audio removes its stored file. Deleting your account — in the app, on the web or through the API — removes every row and every stored file, and cancels queued jobs; apart from short-lived migration backups (at most 7 days), there are no backups that could reintroduce deleted content. What remains: the speech-engine voice registration described below, activity events (365 days) and server logs (30 days). Deleting your account does not cancel an App Store subscription.

You can also delete your account from any browser, without the app, at the account deletion page.

One honest exception

When a voice is created, its reference is registered with the self-hosted speech engine, which exposes no unregister operation: deleting the voice or the account removes it from our storage, but that engine-side copy remains, keyed by an opaque per-account identifier and containing no email or account data.

Children and teens

MyVoiceTale is for people aged 13 and older and is not directed at children under 13. We do not knowingly collect data from children under 13; if we learn that we have, we delete the account. A parent who believes their child has an account can contact the support email below.

Your choices and rights

You can access, correct and delete your data: content through the app, and everything at once by deleting your account in the app or at the link below. You can also write to the support email below with any request about your data. We do not sell or share your data for advertising, we do not track you, and there is no analytics or crash-reporting SDK in the apps.

Changes to this policy

If this policy changes, the updated text is published on this page with a new effective date.

Contact

The service is operated by Zhou Guangyong.

Questions and requests about your data go to [email protected].