Privacy Policy

Last updated: November 10, 2026

On this page

    Introduction

    TheraTales is a service operated by Yevhen Vorobei, a sole proprietorship (“Vorobei TheraTales”) established in Switzerland (“we”, “our”, or “us”). We are committed to protecting your privacy and the privacy of your children. This Privacy Policy explains how we collect, use, and safeguard information when you use our mobile application.

    Children

    TheraTales is made for parents. Its stories are written for children aged 3–8, so a child may listen on a parent’s device, with or without an account. The app never asks a child for anything about themselves. Accounts, purchases and settings are for adults.

    • The child never signs in; every account action is performed by the parent or guardian
    • There is no field anywhere in the app for a child’s name, age, photo, voice, or location
    • The device microphone is disabled, and we use no advertising identifiers
    • Children only listen to pre-produced audio stories

    When the app is used without an account, it sends these technical identifiers: the network address every connection carries, with the address of each file it requests (which shows the story and its language), the standard request headers (app and system version, language) and, only if crash reports are turned on, crash-tracing headers (to deliver stories — Cloudflare), a device check (to protect our servers — Google Firebase App Check), a random purchase identifier kept on the device, with the App Store country, the preferred languages, the device model and system version and the app version, when the store shows prices (RevenueCat), and, only if crash reports are turned on, the crash-reporting identifier of the app installation with crash and error reports and their details, such as the stack trace, the device model, the system and app version, the language and region, and the names of the servers the app contacted before the crash (Sentry). If usage analytics are turned on, the app also sends usage events — such as which screen or story was opened, with a random identifier for that launch of the app and one fixed value that every user without an account shares — to TelemetryDeck, an independent analytics service, through our own relay, so TelemetryDeck does not receive the network address. If crash reports and usage analytics are both turned on, Sentry also records a session, with the same installation identifier, each time the app is opened. Google, RevenueCat and Sentry also receive the network address of each request. Versions of the app before 0.32 start RevenueCat at every launch and on iPhone also send Apple’s identifier for vendor (IDFV); updating the app stops both. Versions of the app before 0.35 send the usage events straight to TelemetryDeck, with the network address, which TelemetryDeck says it does not store, and send Sentry, instead of the server names, the addresses the app requested; updating the app stops both. We use all of this only to deliver the service, keep it secure, fix faults and see how the app is used. We never use it to contact anyone, to build a profile or for advertising, and Cloudflare, Google, RevenueCat and Sentry process it only on our instructions.

    Sentry keeps crash and error reports under its own retention policy. RevenueCat keeps a purchase identifier that was never linked to an account for as long as we provide the service, and deletes one linked to an account after that account is deleted. TelemetryDeck keeps usage events under its own retention policy. Cloudflare and Google keep connection and device-check records under their own terms; we keep no copy.

    Records sent without an account carry no name, email or account, so we cannot find one person’s records and delete them on request. A parent can stop them: in Settings → Privacy, turning off usage analytics stops the usage events at once and Sentry sessions from the next launch, and turning off crash reports stops crash reporting after any report already on its way; deleting the app removes the purchase identifier from the device. Questions: privacy@mytheratales.com.

    Information We Collect

    We collect only the minimal information needed to run the service; what the app sends when it is used without an account is described under Children above:

    • Your account email address. You can create an account with Apple, Google, or an email and password; when you use a password it is stored only as a secure hash managed by Firebase Authentication, so we never see or store your plaintext password.
    • A user account ID (your Firebase user ID), used to authenticate you and to own your purchases
    • If you sign in with Google, your Google account name and profile photo link. We use the name to greet you in the app; the photo link is stored with your account profile and is not currently displayed anywhere. If you sign in with Apple, any name Apple offers is discarded, not stored; the email/password option provides neither.
    • Subscription and purchase status, to deliver and restore paid content
    • Your favorites, playlist and listening progress, so they sync across your devices
    • Local device settings (app language, theme, and your parental-gate PIN), stored on your device
    • The Parent tab’s “This week” summary is put together on your device. For the last seven days the app notes there which stories were played and how far, and works out from it the number of stories, the listening time, the favorite category and the tip shown under “After tonight”. Neither this list nor the summary is sent to us or to any of our providers; the resume position, the usage analytics and the diagnostic reports described in this policy are separate from them. On an iPhone or iPad this list is also part of the device’s own backup, if you use one. The list and the summary are erased from the device whenever the account in use changes — when you sign out, sign in or delete your account — and each time the app is opened without an account.
    • Pseudonymized product-analytics events, and crash diagnostics with automated redaction of the personal data they detect (see “How We Use Your Information” below)
    • Technical data collected by our providers’ SDKs: crash reports and device performance readings such as battery level and free memory (Sentry); delivery and integrity identifiers (a Firebase installation ID, a push-delivery token, and app/device integrity signals used to protect our backend); and purchase data handled by RevenueCat. From version 0.32 of the app, RevenueCat receives it from the moment the app first loads a price to show you, or you buy or restore, until the app is fully closed (leaving it in the background does not close it), and, for up to three days after a purchase you started did not complete (for example, one still waiting for approval), from each app start or sign-in on that account: your account identifier (or, without an account, a purchase identifier created in the app and stored on your device, which is linked to your account if you then sign in), your App Store country, your preferred languages, your device model and system version, the app version, and your purchase receipts. Versions before 0.32 start RevenueCat each time the app is opened, even before you sign in, and on iPhone also send Apple’s “identifier for vendor” — a device identifier shared by the apps of one developer on the same device; updating the app stops both. If you sign in with Google, its sign-in SDK also declares that it may collect a phone number associated with your Google account, coarse location (approximate, derived from your network address), and other usage data. Like any online service, each of these providers also receives your device’s IP address when the app connects to it.
    • Our providers also learn which language you use. The requests the app sends them can carry your device’s language settings, as the requests of any app do. Usage analytics events include the language the app is shown in. Our database (Firebase) and Cloudflare see that language in the address of the catalog and story files the app requests. Sentry’s diagnostic reports include the language your device uses for the app and your device’s region; they can also include its time zone, calendar and clock format, and the names of the servers the app recently contacted (versions of the app before 0.35 send the addresses of the catalog and story files it recently requested instead). Firebase Authentication receives the language your device uses for the app and, on some devices, the device’s region.

    Website Email List

    On our website (mytheratales.com) you can leave your email address to be told once, when an Android version of TheraTales is ready. TheraTales is already on the App Store for iPhone; there is no Android version yet and no date we can give. This list is separate from the app, and your email address is the only thing you are asked to type. Alongside it we keep a short record of the sign-up itself:

    • Your email address, the date you signed up, and the date you confirmed it.
    • Whether the sign-up is waiting for confirmation, confirmed, or unsubscribed — and, if you unsubscribe, the date you did.
    • The single-use code in your confirmation link, and the date that link stops working (seven days after you sign up). The code stays on the record once it has been used.
    • The language you signed up in, which form on the page you used, and a short label naming the version of the consent wording you agreed to.
    • The page of our site you were on when you submitted the form — recorded however you arrived. If another website linked you to us, we also keep the address of that website, whether or not it has anything to do with a campaign: a parenting blog, a search result, a post someone shared. And if the link you followed was a campaign link, we keep what it says about the campaign as well (its five standard “utm” values). Both stay empty when you come to us directly, and the linking website is empty too whenever your browser passes none on. This is how we see which links parents found us through. All of it is read from the page you are on at the moment you submit the form, and none of it is ever stored on your device.
    • We use a double opt-in: after you sign up we send one email asking you to confirm, and we add you to the list only once you click the link in it.
    • We do not store your IP address. It is passed to Cloudflare Turnstile, which checks that the sign-up is not automated, and it is not written to our records. The form sets no cookie that follows you across other websites, and Turnstile does not build a profile of you.

    If you signed up before 21 September 2026, you agreed to something else: at that time the form asked to be told once, when TheraTales became available. TheraTales reached the App Store for iPhone on 18 September 2026. We sent that one message on 7 October 2026, and on 8 October 2026 we deleted every address we held under that earlier consent. None of them is on our list now; what a deletion leaves behind for a short time is described below. We never sent those addresses the Android notice described above, because that is not what they agreed to.

    The legal basis for this email list is your consent (Art. 6(1)(a) GDPR), and you can withdraw it at any time. Every email from this list carries a one-click unsubscribe: a link in the message, and the standard header your mail app uses for its own unsubscribe button. The header button takes effect immediately. The link in the message opens a page with a single button to press — one press, nothing to sign in to and nothing to fill in — because the security scanners that open links before you see them would otherwise unsubscribe you, or cancel your confirmation, without you having clicked anything. Unsubscribing does not erase the record: we mark it unsubscribed and note the date, which is what keeps your address off any later send, and we keep the sign-up and confirmation dates as evidence of the consent you had given. If you sign up again later, that counts as fresh consent: the address stays marked unsubscribed, and the confirmation email is sent a second time, so nothing is sent to you again until you confirm from your own inbox. If you do confirm that fresh sign-up, that click becomes the record: the sign-up date and the consent-wording label move to the moment you confirmed, and the earlier unsubscribe date is cleared — so the dates we keep always describe the consent you are on the list under now. How long we keep it. A confirmed address is kept until the one message it is waiting for has been sent and for 30 days after that, and is then deleted — or, with your fresh consent, moved to our regular mailing list. There is an outer limit as well, because the message you are waiting for depends on an event we cannot date: if it has not been sent within 12 months of the day you confirmed, we delete your address then and send nothing. That does cost you something — you would not get the message you asked for — and we would rather that than hold your address indefinitely for an event we cannot put a date on. If you never confirm, we delete the record 30 days after the confirmation link stops working, and the link is valid for seven days. An unsubscribed record is kept for three years from the date you unsubscribed, because that record is what keeps your address off a later send, and is then deleted. We carry these deletions out ourselves; there is no automatic job doing it for us yet, so treat the periods above as the limits we hold ourselves to rather than as something a machine enforces. Because we cannot give a date for the Android version, we cannot say when that clock will start for an address waiting on the Android notice; and if the Android version is abandoned, we delete those addresses without a further message, because one note when it is ready is all they agreed to receive. That rule is about the Android notice and nothing else: if you signed up before 21 September 2026 you were waiting on a different message, which did not depend on Android. It has been sent and those addresses are deleted, as described above. You do not have to wait for any of this: write to privacy@mytheratales.com and we erase the address outright. A deleted address leaves our list at once. For up to seven days it can still be restored from the recovery history our database provider keeps, and the sending log of our email provider holds it for up to a month. The address is stored by Cloudflare within the European Union; the confirmation and both messages are delivered through Brevo (see Service Providers).

    How We Use Your Information

    We use this information solely to provide and improve our service, and we never show ads to you or your child. Usage analytics are handled by TelemetryDeck, an independent analytics service that receives pseudonymized usage events — a one-way hash of your account identifier (without an account, one fixed value shared by everyone instead), a random identifier for the current session, and events such as playback started or a search performed (never your email, name, or the text you search for) — and does not track you across other companies’ apps or websites. Crash diagnostics go to Sentry, with automated filters that redact the personal data they detect. Crash diagnostics and usage analytics run only with your consent, which you give in the app and can withdraw at any time, and separately, in Settings → Privacy; withdrawing does not affect the lawfulness of processing carried out before you withdrew. When crash diagnostics and usage analytics are both turned on, Sentry also records a usage session each time the app is opened or returns to the foreground. Your favorites, playlist, listening progress, and purchase status are stored in our secure cloud (Firebase) so they follow your account across your devices. Any account-verification and password-reset emails we send are transactional messages needed to operate your account, not marketing. We never sell your information, and we never give it to anyone for their advertising or marketing; apart from the pseudonymized analytics events described above, we do not share your information with third parties.

    Service Providers

    We share data only with service providers that process it on our instructions, never for their own independent use: for the app, Firebase (authentication, database, and functions), RevenueCat (to broker your subscriptions and purchases), Sentry (crash diagnostics), and Cloudflare (content delivery — the stories’ audio, covers, texts and catalog); for the website and its email list, Cloudflare (website hosting, and storage of that email address within the European Union) and Brevo (Sendinblue SAS, France), which delivers the confirmation and then the one message your consent covers — the Android notice, or, for the earlier cohort, the note that TheraTales had become available. Product analytics are handled separately by TelemetryDeck, an independent analytics service rather than a processor acting on our instructions (described under “How We Use Your Information” above). We never sell your data or share it with advertisers.

    Data Storage & Security

    Your account data is stored securely with Firebase, encrypted in transit using HTTPS/TLS and encrypted at rest by our cloud provider. Downloaded stories are stored locally on your device. We implement industry-standard security measures to protect your information.

    Data Retention

    We keep your account data only while your account is active. When you delete your account, your sign-in record, profile details, favorites, playlist, listening progress, and entitlement record are removed. The customer record that RevenueCat, our purchase processor, keeps for us — the identifiers, purchases, store country, languages, device model and app version described above — is deleted too, normally within a day; to do this we send your former account identifier to RevenueCat, even if you never bought anything. If an App Store subscription on that record has not ended — it is still running, paused, or the store may still collect a failed renewal (for up to 60 days) — the record is kept until the subscription ends, so that you can still restore the subscription on a new account, and is deleted then. What remains afterwards is a minimal deletion record keyed to your former account identifier (the deletion date, processing-status flags, and whether a subscription was active and how many stories were purchased — no name, email, or content, though the identifier itself is personal data and currently has no automatic expiry), payment and security records our providers keep for accounting and abuse prevention, a purchase identifier created without an account and never linked to one, which RevenueCat keeps for us for as long as we use its service, and any crash reports and pseudonymized analytics events already sent, which stay with our providers under their retention policies. Because the deletion record keeps your former account identifier, the analytics events already sent can still be linked to it.

    Your Rights

    You have the following rights regarding your data:

    • Request access to the personal data associated with your account
    • Correct inaccurate account information
    • Delete your account and the personal data associated with it, in the app, at any time (Settings → Delete account) — the Data Retention section above lists what remains after deletion
    • Withdraw your consent to crash diagnostics or to usage analytics at any time, and separately, in the app (Settings → Privacy)
    • Object to processing we base on our legitimate interest — the account-security measures (such as email verification and abuse protection)

    If you are in the EU, EEA, or UK, see the section below for additional rights.

    EU, EEA & UK Users (GDPR and GDPR-K)

    If you are located in the European Union, the European Economic Area, or the United Kingdom, the following applies in addition to the rest of this policy. The data controller responsible for your personal data is:

    Yevhen Vorobei, sole proprietor, trading as “Vorobei TheraTales”
    Fabrikstrasse 34, 4123 Allschwil, Switzerland
    Email: privacy@mytheratales.com

    We are established in Switzerland and process personal data in accordance with the Swiss Federal Act on Data Protection (revFADP/nFADP). Where we offer the service to users in the European Economic Area or the United Kingdom, we also comply with the EU General Data Protection Regulation (GDPR) and the UK GDPR respectively.

    We process the personal data of the parent — the adult account holder. When the app is used without an account, the user may be a child; what the app then sends, and why, is described under Children above.

    We rely on the following legal bases:

    • Performance of a contract (Art. 6(1)(b)) — your email, account ID, subscription and purchase status, favorites, playlist, and listening progress, to create your account, provide the app, and deliver and restore your purchases; and the purchase data RevenueCat processes to show you prices and to complete or restore the purchases you ask for, including the steps you ask for before a purchase. No legal basis is claimed for the RevenueCat traffic that versions before 0.32 send when the app is opened: updating the app removes it.
    • Compliance with a legal obligation (Art. 6(1)(c)) — carrying out a request to delete your account or to exercise your other data-protection rights, including sending your former account identifier to RevenueCat so that it can delete its record of you.
    • Our legitimate interests (Art. 6(1)(f)) — account-security measures such as email verification and abuse protection, to keep accounts safe.
    • Consent (Art. 6(1)(a)) — crash diagnostics and usage analytics in the app, each only after you turn it on: the diagnostics with automated redaction of the personal data they detect, the analytics under a one-way hash of your account identifier, or one shared value if you use the app without an account. You can withdraw either consent at any time, separately, in Settings → Privacy. If you join the website email list, we process your email to send the confirmation and then the one message your consent covers — the notice about an Android version if you signed up on or after 21 September 2026, and the one telling you TheraTales had become available if you signed up before that. You can withdraw that consent at any time (one-click unsubscribe, or email us). Withdrawing a consent does not affect the lawfulness of processing carried out before you withdrew, or any other processing.

    You have the right to access, rectify, erase, restrict, and object to the processing of your personal data, the right to data portability, and the right to withdraw any consent at any time. You can erase your account and the personal data associated with it in the app (Settings → Delete account); what remains after deletion is described under Data Retention above. You also have the right to lodge a complaint with your local data-protection supervisory authority.

    We practise data minimization: we collect only the parent’s email and the minimal account data needed to run the service, and the app never asks a child for anything about themselves. Where our service providers store or process data outside the EEA or UK — for example Firebase Authentication, operated by Google in the United States, and RevenueCat, Inc., also in the United States — the transfer is protected by an appropriate safeguard: we rely on the EU–US Data Privacy Framework adequacy decision where the recipient is certified, with the European Commission’s Standard Contractual Clauses (and the UK IDTA) as a backstop; for RevenueCat, the Standard Contractual Clauses in its data processing agreement.

    EU and UK Representatives (Article 27)

    Because we are established in Switzerland — outside the European Union and the United Kingdom — and offer the service to users in the EEA and the UK, we have appointed representatives under Article 27 of the EU GDPR and Article 27 of the UK GDPR. You may contact the relevant representative on any matter relating to the processing of your personal data, as an alternative to contacting us directly.

    Representative in the European Union
    Prighter EU Rep GmbH
    Schellinggasse 3/10, 1010 Vienna, Austria

    Representative in the United Kingdom
    Prighter Ltd
    20 Mortlake Mortlake High Street, London, SW14 8JN, United Kingdom

    A request you make through a representative is handled using the representative’s secure request-management tooling, hosted within the European Union (Hetzner Online GmbH); the representative forwards your request to us to action.

    Contact Us

    If you have questions about this Privacy Policy or our data practices, or wish to exercise any of your rights, please contact us at privacy@mytheratales.com