Berkay Bakışoğlu ("we", "us", "our") operates the Umay mobile application ("Umay", the "App"). This Privacy Policy explains what information the App collects, why, how it is stored, who processes it on our behalf, and the choices and rights you have.
Umay is designed to be set up and operated by a parent or guardian (an adult). It lets a parent record a short sample of their own voice, creates a synthetic ("cloned") version of that voice, and uses it to narrate a curated library of classic children's stories. Children listen; the account, the voice, and the settings belong to the adult.
If you do not agree with this Policy, please do not use the App.
We collect very little, and we keep most of it on your device. Your child's name and any photos you add stay on your phone or tablet and we never upload them. We do include a coarse age range (for example, 5-7) in usage analytics to understand which age groups use the App; see Section 3.5.
Your voice is the sensitive part. To narrate stories in your voice, we send a short recording of your voice to a processing service that builds a voice model. This is treated as biometric data under some laws. We explain this fully in Section 4 and ask for your consent before recording.
We do not sell your data, show third-party ads, or track you across other apps and websites.
You can delete everything — your account, your voice, your voice model, and all local data — from inside the App at any time (Settings → Account).
We use a small number of trusted service providers (Apple, Supabase, Modal, Adapty, Cloudflare, PostHog, and Sentry) listed in Section 7.
This Policy applies to the adult account holder who downloads and sets up Umay. By using Umay you confirm you are at least 18 years of age and that you are the parent or legal guardian of any child for whom you create a profile.
Umay is designed and intended to be set up and operated by an adult. Although children listen to the stories, they do so under adult supervision, and the App is built so that child-related information such as the name and photos stays on the device under the parent's control and is never sent to us; only a coarse age band is used in analytics (see Sections 3.5 and 5). We do not seek to collect personal information from children online.
The following is created and stored locally on your device. Apart from the coarse age band described in Section 3.5, it is never transmitted to our servers:
You can edit or delete any of this at any time within the App. Deleting a child profile removes that child's stored details and photos from the device.
If you buy an Umay subscription, the purchase is handled by Apple through the App Store and managed by our subscription provider (Adapty). We and Adapty receive your subscription status (for example, active, expired, in free trial) and a transaction/anonymous identifier. We never receive or store your credit-card or payment details — those stay with Apple.
If the App crashes or hits an error, we collect crash and error diagnostics through Sentry to help us fix bugs. This is enabled only in released builds. We have configured Sentry not to attach personally identifying information (such as your IP address), and session replay (screen recording) is turned off. Diagnostics may include device model, OS version, app version, and a technical stack trace.
To understand how the App is used and improve it, we collect product-analytics events through PostHog (US cloud). These events record actions such as opening the App, viewing a screen, starting or finishing a story, and steps in the setup and subscription flows, along with technical context (platform, app version, and coarse session timing). Once you sign in, these events are linked to your account identifier so we can measure the experience across your sessions; before you sign in they are tied only to a random analytics identifier. Where you have entered a child's age, a coarse age band (for example, 2-4, 5-7, or 8+) is attached to these events so we can understand which age groups use the App; we never attach your child's name, birthdate, or photo. We have not enabled automatic screen-content capture or session replay, and we do not use this data for advertising or to track you across other apps or websites. The App collects no advertising or cross-app tracking identifiers and makes no App Tracking Transparency request.
Because narrating in your voice is the core feature, we explain this in full.
What we collect. When you choose to create a narrator voice, you record a short audio sample of yourself speaking. With your action and consent, that recording is transmitted to our voice-processing pipeline.
What we do with it. The recording is sent over an encrypted connection through our gateway to a voice-cloning service (Modal), which produces a voice model (a small data file that represents the characteristics of your voice). That model is later used to generate story narration audio in your voice.
Where it is stored.
Why this matters legally. A voice sample used to create a model that can reproduce or identify your voice may qualify as biometric data or a voiceprint under laws such as the Illinois Biometric Information Privacy Act (BIPA) and comparable state and international laws, and as a special category of personal data under the EU/UK GDPR (Article 9). These laws generally require us to:
Your control. You may delete any voice you created at any time (Settings → narrator voice → delete), and you may delete your whole account (Section 8). Deleting a voice removes the voice model file from Modal and the associated audio from cloud storage. You should only record your own voice, or the voice of someone who has consented to be recorded. Do not record a child's voice or anyone who has not agreed.
Umay is rated 4+ and is designed to be operated by a parent or guardian. It is not submitted to Apple's Kids Category. While the stories are enjoyed by children, the App is built so that children are not asked to provide personal information to us online.
United States — COPPA. The Children's Online Privacy Protection Act governs the online collection of personal information from children under 13 by operators of child-directed services. Umay keeps the child's name and photos on the device and does not transmit them to us; the only child-related value that reaches our analytics is a coarse age band tied to the adult account, which is not a name, contact detail, photo, or persistent identifier of the child. The parent sets up and controls the App, controls what (if any) child information is entered, and can delete it at any time.
EU/UK — GDPR-K (children's data). Where the GDPR applies, the lawful basis, transparency, and minimization principles in this Policy apply. Any account is created by an adult. We do not knowingly create accounts for children, and the age of digital consent (13–16 depending on the member state) is not relevant to data we never collect.
No knowing collection from children. We do not knowingly create an account for, or collect server-side personal information from, a child. If you believe a child has created an account or that we hold a child's personal information, contact us at berkaybakisoglu@gmail.com and we will delete it.
| Data | Purpose | GDPR legal basis (where GDPR applies) |
|---|---|---|
| Voice sample + cloned voice model | Provide the core feature: narrate stories in your voice | Explicit consent (Art. 6(1)(a) + Art. 9(2)(a)) |
| Account identifier / sign-in | Create and secure your account; sync your voice across your devices | Performance of a contract (Art. 6(1)(b)) |
| Subscription status | Provide and manage paid features | Performance of a contract (Art. 6(1)(b)) |
| Crash/diagnostic data | Keep the App stable and secure | Legitimate interests (Art. 6(1)(f)) |
| Usage / product-analytics events | Understand how the App is used and improve it | Legitimate interests (Art. 6(1)(f)) |
| On-device child profile / preferences | Operate features on your device | Not collected by us; under your control on the device |
You can withdraw consent for voice processing at any time by deleting the voice or your account; withdrawal does not affect processing already carried out.
Required vs optional data, and automated decisions. An account identifier and sign-in information are required to create and secure an account. Recording a voice is optional: if you choose not to create a voice, narration in your own voice is unavailable, but you can still use the App with our built-in narrator voices. Subscription data is processed only if you choose to subscribe. We do not carry out any automated decision-making or profiling that produces legal or similarly significant effects for you.
We use the following trusted providers to operate Umay. They process data only to provide their service to us and are bound to protect it. We do not sell data to anyone.
| Provider | What it does for Umay | What it processes | Privacy policy |
|---|---|---|---|
| Apple | App distribution, Sign in with Apple, In-App Purchases | Apple account identifier, relay email (if you allow), purchase/subscription transaction | apple.com/legal/privacy |
| Supabase | Authentication, database (voices row), public preset story audio, and private voice/audio storage (us-east-1, US) |
Account identifier, voice metadata row, voice sample + generated audio | supabase.com/privacy |
| Modal | Voice-cloning compute; stores the voice model file (US) | Voice sample (during processing), voice model (.pt) |
modal.com/legal/privacy-policy |
| Adapty | Subscription management | Subscription status, anonymous/transaction identifier | adapty.io/privacy |
| Cloudflare | Hosts this privacy policy (Pages) and serves story scene images through an access-controlled Worker backed by R2 storage (US / global edge) | Your authenticated session token (sent to authorize each image request) and the cached scene images it delivers | cloudflare.com/privacypolicy |
| PostHog | Product/usage analytics (US cloud) | Analytics identifier or account identifier, in-app events, platform/app version, coarse session timing | posthog.com/privacy |
| Sentry | Crash and error diagnostics (production only, no PII, no session replay; US) | Device/app technical data, stack traces | sentry.io/privacy |
Pre-recorded, non-personal story audio (our built-in narrator voices) may be served from a public Supabase Storage bucket (us-east-1). Voice samples and any narration generated using your cloned voice are stored privately and are accessible only through authenticated, short-lived signed URLs (see Section 4). Story scene images are served through a Cloudflare Worker backed by Cloudflare R2 storage; each request carries your authenticated session token so that only signed-in users can load them. We do not use any third-party advertising or content-recommendation network.
Retention. We keep your account identifier, your
voices row, your voice sample, your voice model, and generated
narration audio for as long as your account exists and you
keep the voice, so the feature keeps working across your sessions and
devices. In any case, voice (biometric) data is deleted when its purpose ends
or no later than 3 years after your last interaction with the
App, whichever comes first. We retain product-analytics events only
as long as needed to analyze and improve the App. Crash diagnostics are
retained by Sentry for up to 90 days.
Deleting a single voice. Deleting a voice in the App removes the voice model from Modal and the related audio from cloud storage.
Deleting your account (full erasure). From Settings → Account → Delete Account, you can permanently delete everything. This action:
voices database row(s);Data is deleted from our active production systems. Residual encrypted copies may remain temporarily in routine backups until those backups expire under the relevant provider's retention schedule, and Apple retains its own purchase records under its policies.
You may also email berkaybakisoglu@gmail.com to request deletion, and we will action it.
Depending on where you live, you may have rights to:
EU/UK/EEA residents may lodge a complaint with their local data-protection authority. California and other US-state residents have rights under applicable state privacy laws; we do not "sell" or "share" personal information for cross-context behavioral advertising. To exercise any right, contact berkaybakisoglu@gmail.com. We will verify your request using your account credentials and respond within the period required by law.
We protect your information with measures appropriate to its sensitivity:
No system is perfectly secure, but we work to safeguard your data and to honor the heightened care that biometric data deserves.
Our processors (Supabase, Modal, Adapty, Cloudflare, PostHog, and Sentry) store and process data in the United States (Cloudflare may also serve cached images from edge locations closer to you). If you are in the EU/UK/EEA, these transfers are made under appropriate safeguards — including the Standard Contractual Clauses and Data Processing Agreements maintained by each processor — where required by applicable law. You can review each processor's transfer mechanisms at the privacy-policy links in Section 7. You may request a copy of, or more information about, the relevant transfer safeguard by contacting us (Section 14).
Subscriptions are processed by Apple and are subject to Apple's terms and privacy policy. If the App links out to any external page (for example, this Policy or our Terms), those pages are governed by their own terms.
We may update this Policy as the App evolves or the law changes. We will revise the "Last updated" date above and, for material changes affecting how we handle your voice data, provide a more prominent notice in the App. Continued use after an update means you accept the revised Policy. Where required by law, material changes to voice or biometric processing will not take effect for an existing user until we obtain renewed explicit consent.