This policy explains what the Wonderwhy app and the wonderwhy.net website collect, why, who processes it, how long it is kept and what you can do about it. It describes how the app works today. When that changes, we update this page and the date above. If you’re in Türkiye, the KVKK notice summarises it in the order Turkish law asks for.
Who we are
Wonderwhy is published by Yiğit Özdemir (Yelkovan.ai) (“we”). We are the data controller for the personal data described here. For anything about your data, write to info@yelkovan.ai.
Summary
- The free version shows ads from Google AdMob. They aren’t personalised: they aren’t chosen by your interests or by what you do in other apps. To improve the app we measure how it’s used and when it crashes; turn this off any time in Profile › Privacy & data. To see whether our ads work, whether you installed the app from an ad and whether you subscribed is reported to Google and Apple; no advertising ID is used and no ads are personalised (see Ad measurement). We don’t sell your personal data.
- You need an account to read and listen: email and password, Sign in with Apple (on iPhone and iPad) or Sign in with Google. Without one you can only look around. Your lists and settings sync between your devices.
- You can subscribe to Premium if you like. Apple or Google takes the payment; we never see your card details.
- When you ask a question by voice, the recording goes to Google’s Gemini service to be understood and answered. We don’t store it. If you turn on voice commands, your phone itself understands them; your voice doesn’t leave the phone.
- AI writes the news summaries from public news feeds. None of your data is sent for that.
- Apart from your account and what you keep in it, we keep nothing for more than 7 days. The one exception is usage measurement: 90 days (see Usage measurement and crash reports).
- You can delete your account in the app, or by email without it (see Delete your account).
| Data | Why | Where it goes | How long |
|---|---|---|---|
| Email, password or Apple/Google sign-in, optional name | Account and sign-in | Google Firebase Authentication | Until you delete your account |
| Email verification code (only a summary) and number of tries | Confirming the address is yours | Google Cloud Firestore (Belgium); sent through Google Workspace | 7 days at most; at once when you delete your account |
| Synced lists and settings | Keep them in step across your devices | Google Cloud Firestore (Belgium) | Until you delete your account |
| Votes and poll answers | Count them once and show totals | Google Cloud Firestore (Belgium) | 7 days after the story’s day, or until you delete your account if sooner |
| Voice question (up to 15 seconds) and the sentence playing | Understand and answer your question | Google Gemini API | Not stored by us |
| Voice commands (if you turn them on) | Control the briefing by voice | Nowhere: understood on your phone | Not stored |
| Daily usage counters (your ID and a number) | Fair-use limits | Google Cloud Firestore (Belgium) | 7 days; deleted at once with your account |
| Free listening time (how many seconds you listened today) | Counting the daily free time | Your phone; Google Cloud Firestore (Belgium) | Today’s count only, overwritten the next day; deleted at once with your account |
| Subscription (your account ID, the store’s purchase record, your subscription status) | Confirming the purchase and unlocking Premium | RevenueCat; Google Cloud Firestore (Belgium). Apple or Google takes the payment | Status while the subscription lasts; the RevenueCat record until you delete your account |
| Server logs (IP address, app and device details) | Security and fixing problems | Google Cloud (Belgium) | 7 days |
| Usage measurement (screens you open, listening, buttons you tap; your account ID and the app’s device ID) | Improving the app | Google Cloud Firestore (Belgium), Google Analytics for Firebase | 90 days (Google Analytics: 2 months); daily totals aren’t personal and are kept |
| Mini survey answers (the option you pick; no free text), with your account ID | Improving the app and how we promote it | Google Cloud Firestore (Belgium), Google Analytics for Firebase | Same as usage measurement: 90 days (Google Analytics: 2 months); the “Where did you hear about us?” answer stays in your account’s usage summary until you delete your account |
| Ad measurement (whether you installed the app from an ad; first open, sign-in, listening and subscription events; on iPhone and iPad the SKAdNetwork registration and Apple’s AdServices token). No advertising ID | Seeing whether our ads work | Google Ads, through Google Analytics for Firebase (not in the EEA, the UK or Switzerland); Apple; RevenueCat | Under Google’s and Apple’s own retention periods; the RevenueCat record until you delete your account |
| Crash reports (where the error happened, device model, system and app version, your account ID) | Finding and fixing bugs | Firebase Crashlytics | 90 days |
| Ad data (IP address and approximate location, device and app details, interaction with ads; a device ID: the identifier for vendor (IDFV) on iPhone and iPad, the advertising ID on Android) | Showing and measuring non-personalised ads, preventing fraud | Google AdMob | On Google’s own schedule |
Your account
To open stories and listen, you need an account; without one you can go through the introduction and see the day’s headlines. When you create an account, we process your email address, your password and, if you enter it, your name. Google’s Firebase Authentication stores them; we never see your password. You can also use Sign in with Apple (on iPhone and iPad) or Sign in with Google. Apple or Google then shares your name, your email address (Apple may give a private relay address) and a sign-in token with us. With Google, Firebase Authentication also stores the web address of your Google profile photo; the app doesn’t use or show it. During Google sign-in, Google’s sign-in software may also use your IP address to estimate your approximate location, to protect the sign-in against fraud.
When you create an account with email and password, we send a 6-digit code to confirm the address is yours. The code comes from info@yelkovan.ai through Google Workspace and is valid for 10 minutes. We don’t store the code itself: only a one-way summary of it and how many times it was tried, for 7 days at most. Password reset emails come from Firebase Authentication, in the name of wonderwhy.net.
Before you sign in, the app may create a random guest ID (a Firebase anonymous account) for features that need one. It isn’t linked to your name or email, but it is still personal data, because what is stored under it can be linked back to your phone. If you then create an account, your guest ID becomes your account ID. If you sign in to an account you already have, the app stops using the guest ID. A guest ID that isn’t used for 7 days is deleted automatically.
What syncs to your account
When you are signed in with an account (not as a guest), the app keeps the following in Google Cloud Firestore so it follows you to your other devices. Only you can read it.
- Preferences: your topics, languages, story depth, text size, listening settings and notification choices.
- Saved stories (up to 50), stories you recently read or listened to (up to 30) and your listening queue (up to 20). These are copies of the stories inside the app.
- Topics and sources you follow or mute.
- Your own copy of your votes and poll answers, and the stories you reported.
- Your word list and My questions (up to 1,500 entries): each word or concept with the sentence and headline where you found it. When you ask by voice what something means (for example “what is …?”), the concept and the answer are added here.
- Today’s listening progress: which stories you heard, how long you listened and how many questions you asked. Only the number of questions is kept, not the questions.
- Your subscription status and today’s count of free listening time (see Subscription and payment). Only our server writes these.
Votes and reports
When you react to a story or answer a poll, your vote is stored with your account ID, so that it counts once and you can change it. Other people see only the totals. Votes are deleted with the story, 7 days after the story’s day.
When you report a problem with a story or an answer, we store the story, the reason you picked and the note (up to 500 characters). If you report a voice answer, the app fills the note with your question and the answer so we can see what went wrong; you can change or delete it before you send. The report isn’t linked to your ID, and it is deleted after 7 days. Please don’t put personal information in the note: because it isn’t linked to you, we can’t find it earlier to delete it.
Microphone and questions
Push-to-talk questions
While a briefing plays, you can hold the microphone button and ask a question. The app records only while you hold the button, for up to 15 seconds. It sends the recording, together with the sentence that was playing, to our server. Our server sends them to the Google Gemini API, which works out your question and writes an answer. Google’s text-to-speech then reads the answer in the briefing’s voice.
Before your first voice question, the app tells you that your voice goes to Google’s AI and asks you to agree. Nothing is recorded or sent until you do.
We don’t store the recording, and we don’t write what you said or the answer to our logs. There are two exceptions, both in your hands: if you report an answer, the report keeps your question and the answer for 7 days (see Votes and reports); and when you ask what something means, the concept and the answer are saved to My questions in your Library and sync with your account until you delete it (see What syncs to your account). Our logs keep only numbers, such as the length of the answer and how long it took. Your voice is not used to identify you.
We use the Gemini API as a paid service. Under Google’s terms for paid services, Google doesn’t use this data to improve its products; it keeps prompts and answers for a limited time only to detect misuse and to meet legal obligations.
Voice commands
If you turn them on, your phone’s own speech recogniser understands the short commands you say while a briefing plays (“stop”, “next”, “faster”). Recognition happens on your phone; the audio doesn’t go to us or to any other company, and it isn’t stored. The microphone listens only while the app is on screen and a briefing is open, or the Today screen is showing; the player, the mini player and Today say “Listening”. You can turn voice commands off in Profile › Reading and listening.
Ready-made questions
Some questions are buttons, such as asking for more detail on a story. Their answers are about the story, not about you, so we save them with the story and reuse them for everyone.
Your phone asks for your permission before the app can use the microphone, and for speech recognition before voice commands. You can turn it off at any time in your phone’s settings.
How the news is made
Our server collects stories from news outlets’ public feeds, and reads the opening paragraphs of their pages to compare how outlets report the same story. It sends them to OpenAI to write the summaries and to Google to read them aloud. These requests contain only news text, none of your data. Stories and their audio files are deleted from our servers 7 days after the day they were published.
Your personal briefing is put together on your phone from the shared edition, so your topics aren’t sent to any AI service.
News images load directly from the publishers’ servers, and source links open the publisher’s page in a browser inside the app. Those publishers can see your IP address and apply their own privacy policies.
On your phone
- Your lists, settings and sync state, in the app’s own storage.
- A cache of story audio, in a temporary folder that your phone may clear.
- Today’s count of free listening time. If you subscribe, the Today audio downloaded for offline listening also sits in the cache folder and isn’t backed up.
- Your sign-in session: on iPhone and iPad in the Keychain, where it can remain after you delete the app; on Android in the app’s private storage.
- An offline copy of your synced data, kept by Firestore.
When you sign out or delete your account, the app removes your lists, votes, words and progress from the phone. It keeps your app settings (topics, languages, text size) so the app keeps working. Deleting the app removes them.
For usage measurement and crash reports the app keeps a random ID and the records waiting to be sent on your phone. Your choice to turn them off is kept on the phone too and isn’t cleared when you sign out.
To protect our servers from misuse, the app uses Firebase App Check, with Apple’s DeviceCheck on iPhone and iPad and Google Play Integrity on Android, to confirm that requests come from the genuine app. We don’t store device identifiers.
Notifications
Only if you allow notifications, your phone subscribes to topics (such as your morning briefing time or major developments in your edition) through Firebase Cloud Messaging, and on iPhone and iPad also Apple’s push service. We send to topics, not to you personally, and we don’t store a device token. You can turn notifications off in the app’s Profile or in your phone’s settings.
Usage limits and server logs
To keep the service fair and affordable, we count how many questions you ask and how many story audios you have generated each day. Each counter holds your account ID, the date and a number. While a story’s audio is being made, the job is recorded with your ID. Counters and job records are deleted after 7 days, and at once when you delete your account.
Our servers run on Google Cloud in Belgium (europe-west1). Google Cloud keeps request logs with IP addresses and app and device details for 7 days. Our own log lines contain numbers, not account IDs.
Subscription and payment
The free version lets you listen for a set time each day. To count it, the app keeps how many seconds you listened today on your phone and in your account: only today’s number, overwritten the next day, with no history. It isn’t counted for subscribers.
If you subscribe to Premium, Apple takes the payment on the App Store and Google on Google Play; we never see your card or payment details. We confirm the purchase and your subscription status with RevenueCat. RevenueCat receives your account ID and the store’s purchase record; it doesn’t receive your email, your name or your device’s advertising identifiers. On iPhone and iPad it also receives Apple’s AdServices token, to tell whether you installed the app from an Apple Ads ad (see Ad measurement). Your subscription’s current status (which product, when it ends, which store, whether it renews) is kept in your account and deleted when the subscription ends. Only our server writes it.
If you subscribe, the audio of your Today list is downloaded to your phone so you can listen offline. It sits in your phone’s cache folder and isn’t backed up. It is deleted on a new day, when you sign out, when you delete your account or when your subscription ends, and within 7 days at the latest.
Deleting your account doesn’t end the subscription; cancel it separately in the App Store or Google Play subscription settings. Purchase, trial, cancellation and refund terms are in the Terms of Use.
Usage measurement and crash reports
To improve the app we measure how it’s used: which screens you open and for how long, which stories in a briefing you listen to, skip or stop at, that you asked a question (only how many, how long and whether it worked, never the text of the question or answer), and taps on buttons like save, share and reactions. Each record carries your account ID, a random ID the app gives this phone, the app and system version, language and edition. Story text, your questions, your email and your name never go into these records. They’re kept on our servers (Belgium) and in Google Analytics for Firebase.
When you finish listening, the app may now and then, at most once a week, show a one-question mini survey (e.g. where you heard about us, where you usually listen). Answering is optional; if you’re not a subscriber, answering adds a few minutes of listening to that day. You only pick one of the given options; there’s no free text. Your answer is kept with usage measurement, linked to your account: raw records for 90 days; the “Where did you hear about us?” answer also stays in your account’s usage summary until you delete your account.
When the app crashes or hits an error, technical details (where in the code it happened, device model, system and app version) go to Firebase Crashlytics with your account ID. We don’t write error message text to our own records.
We do this based on our legitimate interest (see Legal bases). You can turn “Usage data” and “Crash reports” off separately any time in Profile › Privacy & data; from then on nothing is sent from that phone and pending records are deleted. The app tells you this once, the first time you open it.
Usage measurement doesn’t use the advertising identifier (IDFA, Android advertising ID) and isn’t used to personalise ads; we use it only to see whether our own ads work (see Ad measurement). Ad personalisation signals and Google signals are off in Google Analytics. We don’t sell or share personal data, as California law defines those terms. We don’t make decisions about you by automated means that have legal or similarly significant effects.
Ads
The free version shows ads: small ads in the Today list, in Explore, at the end of stories and in the player, and now and then a full-screen ad when you finish or close a listening session. Premium has no ads. Google AdMob picks and shows the ads.
The ads aren’t personalised: they aren’t chosen by your interests or by what you do in other apps and websites. On iPhone and iPad we don’t ask for access to the advertising identifier (IDFA). Even so, to show ads, cap how often they appear, measure them and prevent fraud, Google’s ad software collects from your phone: your IP address and the approximate location it gives, device and app details, your interaction with ads and a device ID: on iPhone and iPad the identifier for vendor (IDFV), which is specific to our apps; on Android the advertising ID and the app set ID. Google processes this under its own privacy policy. On Android you can reset or delete the advertising ID in your phone’s settings.
In the European Economic Area, the UK and Switzerland, the app asks for your choice with Google’s consent form before showing ads. You can change it later in Profile › Privacy & data › Ad privacy choices.
We don’t give Google your account ID, email, name or the stories you listen to for ads.
Ad measurement
We promote Wonderwhy with ads on Google and Apple. To see whether our ads work, whether you installed the app from an ad and whether you subscribed is reported to Google and Apple. No advertising ID (IDFA, Android advertising ID) is used and no ads are personalised.
- Google: some usage measurement events (e.g. first open, sign-in, listening and subscribing) are passed from Google Analytics for Firebase to Google Ads as conversions. This is off in the European Economic Area, the UK and Switzerland. If you turn off “Usage data” in Profile › Privacy & data, nothing goes to Google Ads.
- Apple (iPhone and iPad): the app registers with Apple’s SKAdNetwork; Apple tells the ad network, without any identifier and with a delay, whether an ad led to an install or a subscription. The app also gives Apple’s AdServices token to RevenueCat; RevenueCat uses it to ask Apple whether you installed the app from an Apple Ads ad and adds the answer (which campaign) to your subscription record.
We do this based on our legitimate interest in spending our ad budget where it works (see Legal bases).
Who processes your data
- Google (Firebase Authentication, Sign in with Google, Cloud Firestore, Cloud Functions, Cloud Storage, App Check, Play Integrity, Cloud Messaging, Gemini API, Google Analytics for Firebase and Firebase Crashlytics): hosting, sign-in, sync, questions, audio, usage measurement and crash reports. Google Play takes subscription payments. Google AdMob picks and shows the ads (see Ads). Google Ads measures how our ads perform (see Ad measurement). Firestore, Cloud Functions and Cloud Storage are in Belgium; sign-in, Gemini and some other services may process data in the United States and other countries.
- OpenAI: writes the news summaries. It receives no personal data.
- Apple: Sign in with Apple, DeviceCheck and push notifications. It takes subscription payments on the App Store. It reports how our ads perform through SKAdNetwork and Apple Ads.
- RevenueCat (United States): confirms purchases and your subscription status. On iPhone and iPad it passes the AdServices token to Apple for Apple Ads measurement.
- GitHub: hosts this website.
- Metricool (Spain): counts visits to this website.
- Google Workspace: hosts our mailbox and sends email verification codes; the email you send us is stored there.
These providers process data on our behalf under their data processing terms, which require them to protect it at least as well as this policy describes. Apple and Google also process store payments, and Google ad data, under their own privacy policies. Google and Apple also process ad measurement data under their own privacy policies.
Some of them process data outside Türkiye and the European Economic Area, including in the United States. These transfers rely on the safeguards the law requires: for the EEA, the providers’ standard contractual clauses; for Türkiye, the mechanisms in Article 9 of the Personal Data Protection Law No. 6698 (KVKK).
How long we keep data
Your account and what you keep in it stay until you delete the account. Usage measurement is kept for 90 days. Everything else is deleted within 7 days: a job runs every night and removes what is older.
- Account and synced data: until you delete your account.
- Votes: deleted with the story, 7 days after the story’s day, or earlier if you delete your account.
- Guest IDs: deleted after 7 days without use. This includes a guest ID left behind when you signed in to an existing account.
- Reports: 7 days.
- Email verification codes: the code itself isn’t stored; its summary and the number of tries for 7 days at most, at once when you delete your account.
- Daily usage counters and audio job records: 7 days; deleted at once when you delete your account.
- Subscription: its current status while it lasts; your RevenueCat record until you delete your account. The free listening count is today’s only; offline audio 7 days at most. Apple and Google keep purchase records under their own policies and legal obligations.
- Usage measurement: 90 days; 2 months in Google Analytics. Your account’s usage summary (first and last day of use, totals) until you delete your account; without an account, 90 days after last use. Daily totals that aren’t tied to anyone (e.g. how many people listened that day) are kept.
- Mini survey answers: same as usage measurement, 90 days; the “Where did you hear about us?” answer stays in your account’s usage summary until you delete your account.
- Ad measurement: under Google’s and Apple’s own retention periods; the Apple Ads result in RevenueCat until you delete your account.
- Crash reports: 90 days.
- Ad data: on Google’s own schedule; we don’t keep it.
- Voice recordings: not stored. A question and its answer are kept only as described above: in a report (7 days) or in My questions (until you delete your account).
- Stories, story audio and ready-made answers: 7 days after the story’s day.
- Server logs: 7 days. They contain no account IDs.
- Emails you send us: as long as we need to deal with your message. If you ask us to tell you when the app is out, we keep your address until we have done so, then delete it.
Deleting your data
In the app, go to Profile › Delete account and confirm with Delete account permanently. This deletes at once your account, everything stored under it (lists, settings, words and progress), all your votes, and your usage counters, usage measurement, email verification records, subscription status, free listening count, RevenueCat record and audio job records. If you used Sign in with Apple, the app also revokes its access to your Apple ID. On your phone, the app removes your lists and keeps its settings, as described above.
Deleting your account doesn’t cancel your subscription. To stop being charged, cancel it in the App Store or Google Play subscription settings.
Afterwards nothing linked to your account remains on our servers. Records in Google Analytics and Crashlytics are deleted on their own schedule (2 months, 90 days); anonymous reports and server logs, which contain no account ID, within 7 days. What went to Google Ads and Apple for ad measurement is deleted on their schedules.
If you can’t use the app, write to info@yelkovan.ai from the email address of your account. The steps are also on the Delete your account page. Guest IDs are deleted automatically after 7 days without use; if you want yours deleted sooner, write to us.
Your rights
Depending on where you live, you have some or all of these rights:
- Türkiye (KVKK, Article 11): to learn whether we process your data and request information about it; to learn the purpose and whether it is used for that purpose; to know who it is shared with in Türkiye or abroad; to have it corrected or deleted and have those you shared it with told; to object to a result against you that comes only from automated analysis; and to claim compensation for damage caused by unlawful processing. You can apply by writing to us from the email address registered to your account; we answer within 30 days, free of charge. If you aren’t satisfied, you can complain to the Personal Data Protection Authority (KVKK). Details: KVKK notice.
- EEA and UK (GDPR): to access, correct or delete your data; to restrict or object to its use (for usage measurement and crash reports, instantly with the switches in the app); to receive it in a portable format; to withdraw consent at any time; and to complain to your data protection authority.
- California (CCPA/CPRA): to know what we collect and how we use it, to delete and correct it, and not to be treated differently for using these rights. We don’t sell personal information. To measure whether our own ads work, limited app events go to Google Ads (see Ad measurement); you can stop this by turning off “Usage data” in Profile › Privacy & data. We use sensitive information, such as your account login, only to provide the service.
To use any of these rights, write to info@yelkovan.ai. We may ask you to confirm the request comes from you.
Legal bases
- Providing the service you ask for (account, sync, answering questions, votes, subscription and free listening time): performing our contract with you (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c)).
- Security, misuse prevention, usage limits and logs: our legitimate interests (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)).
- Usage measurement and crash reports: our legitimate interest in improving the app and fixing bugs (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)). This includes mini survey answers. You can object and turn them off in Profile › Privacy & data.
- Ad measurement: our legitimate interest in seeing whether our ads work (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)). The part that goes to Google is off in the European Economic Area, the UK and Switzerland; elsewhere you can object by turning off “Usage data” in Profile › Privacy & data. To object to the rest, write to us.
- Non-personalised ads: our legitimate interest in keeping the free version running (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)). In the European Economic Area, the UK and Switzerland, your choice in the consent form (GDPR Art. 6(1)(a)).
- Microphone, speech recognition and notifications: your permission, which you can withdraw in your phone’s settings (GDPR Art. 6(1)(a)).
- Legal obligations, where they apply (GDPR Art. 6(1)(c); KVKK Art. 5(2)(ç)).
Age
The app is for adults. You must be at least 18 to use it: its question feature uses Google’s Gemini API, whose terms don’t allow services aimed at, or likely to be used by, people under 18. If you think someone under 18 has given us personal data, write to us and we will delete it.
This website
wonderwhy.net is a static site hosted by GitHub Pages. It uses no cookies, no browser storage and no third-party fonts. To count visits we use Metricool: on each page you open, a Metricool script sends Metricool the page address, your window size and the page that linked you here, and Metricool sees your IP address. The script sets no cookies and stores nothing in your browser. GitHub processes visitors’ IP addresses to deliver the site and keep it secure, under the GitHub Privacy Statement. News photos on the home page load from the publishers’ servers; publishers can see your IP address, and no referring address is sent. Audio samples load only when you press play. If you email us, we use your address to reply.
Changes to this policy
We update this page when the app or the law changes, and change the date at the top. For significant changes we will also let you know in the app.
Contact
Yiğit Özdemir (Yelkovan.ai)
info@yelkovan.ai