Privacy Policy
Effective date: 19 October 2026 · Last updated: 19 November 2026
This policy explains what personal data the Verbi apps for iPhone, iPad and Android process, why, who receives it, how long it is kept and what rights you have. It is published in English and Turkish; both versions have the same meaning.
1. Who we are
Verbi is developed and operated by Mustafa Onur Ilgaz, an independent developer based in Türkiye. He is the data controller for the personal data described in this policy under the EU and UK General Data Protection Regulation (GDPR) and Turkey's Personal Data Protection Law No. 6698 (KVKK).
Contact: theverbiapp@gmail.com
2. In short
- Verbi has no user accounts. We do not ask for your name, email address or phone number.
- Your recordings, transcripts, summaries, chats, translations and study packs are stored on your device. Verbi has no cloud sync, and we do not keep copies of them on our servers.
- To turn speech into text, Verbi sends your audio to speech-to-text providers (ElevenLabs and OpenAI), usually through our own server. Summaries, chat, translation, title suggestions and study packs (flashcards and quizzes) send transcript text to OpenAI.
- The iPhone and iPad app asks for your permission before it sends any audio or transcript to these AI providers, and tells you what is sent and to whom. You can withdraw it at any time in Settings > Privacy > AI processing; nothing is sent to them after that.
- We use Google Firebase for usage analytics and crash reports, and RevenueCat for subscriptions. The iPhone and iPad app also contains Meta's Facebook SDK, which sends app events to Meta.
- The Pro and MAX plans include a number of transcription hours per period. To count them, our server keeps a usage counter and any extra-hours balance under your anonymous app user ID: seconds of audio used and hours left, never the audio or the text (3.5).
- You can turn off usage analytics in Settings. Section 4 explains exactly what that switch does and does not cover.
- We do not sell your personal data.
3. What we process and why
3.1 Audio and transcription
What: audio you record in Verbi; audio and video files you import or share into Verbi; audio taken from YouTube links you paste (see 3.3); your transcription language, speaker-separation setting and custom vocabulary.
How:
- When a recording is transcribed, Verbi uploads the audio file over an encrypted connection to our server (Google Cloud Run, United States). Our server forwards it to ElevenLabs for speech-to-text. If ElevenLabs is unavailable or fails, the audio is sent to OpenAI instead. Long recordings may be sent in parts.
- When speaker separation is on, short clips (a few seconds each) of up to four voices from the same recording are sent with later parts, so that each speaker keeps the same label throughout the transcript.
- Live transcription on iPhone and iPad with Verbi Pro, and on Android: your microphone audio is streamed in real time from your device directly to OpenAI.
- Live transcription on iPhone and iPad on the free plan uses Apple's Speech Recognition. Depending on your device and language, Apple may process this audio on your device or on Apple's servers.
- The Android welcome demo uses your phone's built-in speech recognition service (usually Google's), which may process the audio on its servers.
- In some situations, for example when our server cannot verify a request, the app may send the request to OpenAI directly from your device instead of through our server.
- Our server does not store your audio. It holds an upload only in memory while the request is being processed, and it does not log the content.
- For the Pro and MAX plans, and for extra hours on the free plan, our server measures the length of the audio it receives for transcription, so that the hours can be counted (3.5). Only the length is kept, not the audio.
Why: to give you the transcript you asked for.
Legal basis: performance of our contract with you (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c)).
3.2 Transcripts and AI features
What: transcript text, including speaker labels and any speaker names you add; the recording's title, date and time zone; your custom vocabulary; your questions in the transcript chat, with the earlier messages of that chat; text you translate.
How: sent to OpenAI, usually through our server, to:
- write summaries, automatically after transcription where your plan includes it, or when you ask;
- suggest a title and tags, when automatic naming is on;
- correct how your custom vocabulary terms are spelled in the transcript;
- answer your questions about a transcript;
- translate a transcript;
- make a study pack (flashcards and a quiz) from a transcript, when you ask.
Why and legal basis: as in 3.1.
3.3 YouTube import
What: the YouTube link you paste.
How: the link goes to our extraction server (Google Cloud Run, United States). The server downloads the video's audio from YouTube and stores it temporarily in Google Cloud Storage (United States). Your device downloads it through a private link that expires after 6 hours, and the audio is then transcribed as described in 3.1. Stored files are deleted automatically after one day; after deletion, Google Cloud keeps a recoverable copy for up to 7 more days before removing it permanently. Our server logs record the video's title and, if an import fails, the technical error message, which may include the video's ID. YouTube sees a request from our server, not from your device.
Why and legal basis: as in 3.1.
3.4 Invite a friend
What we store on our server (Google Cloud Firestore, United States) when you use invites:
- the anonymous subscription identifier that RevenueCat creates for your installation;
- your invite code;
- the code you entered, if any, and the anonymous identifier of the person who invited you;
- the rewards you earned and the friends counted towards them, with dates;
- the platform, and a short technical label for how your first transcription was made.
Device check: so that each device can claim a reward only once, we confirm that a request comes from a genuine device.
- On iPhone and iPad we use Apple's DeviceCheck. Apple keeps a per-device flag on its own systems; we store no device identifier.
- On Android we use Google Play Integrity together with your device's Android ID. Our server turns the Android ID into a keyed cryptographic hash and stores only that hash, never the Android ID itself.
Reward days are added to your subscription through RevenueCat.
Why: to run the invite programme and to prevent abuse.
Legal basis: performance of the programme you join (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c)) and our legitimate interest in preventing fraud (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)).
3.5 Subscriptions and purchases
- Payments are processed by Apple (App Store) or Google (Google Play). We never see your card details.
- RevenueCat manages subscription status. It receives an anonymous app user ID, your purchase and subscription history from the store, and technical information about the app and device.
- On iPhone and iPad, the app also gives RevenueCat Apple's AdServices attribution token, so that we can see whether a subscription followed a tap on an Apple Search Ads ad. Apple does not require tracking permission for this, and Verbi does not ask for it.
- Our server reads your subscription status from RevenueCat and adds promotional Premium days for invite rewards.
- RevenueCat also notifies our server when an extra-hours pack is bought, refunded or moved to a new app user ID after you restore purchases. The notice carries the app user ID, the product, the store transaction ID and the time.
Legal basis: performance of our contract with you (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c)); for the attribution token, our legitimate interest in measuring our advertising (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)).
Plan hours and extra hours (usage counter).
What: for each app user ID (the anonymous ID RevenueCat assigns; we hold no name, email address or phone number):
- the seconds of audio used in the current period, and when that period started;
- your extra-hours balance, in seconds;
- for each extra-hours pack: the hours it granted and whether it was refunded or moved to another app user ID. The store transaction ID is kept only as a one-way hash;
- records of refunds of transcription charges, and of balance moves between app user IDs (the other app user ID and the time).
The counter holds no audio, no transcript, no file names and no other content. It is stored in Google Cloud Firestore (United States).
Why: to apply the hour limits of the Pro and MAX plans, to keep the extra hours you bought (they do not expire, and they must survive reinstalling the app or changing phones), and to credit, refund or move them correctly.
How long: we do not delete these records automatically; they stay until you ask us to delete them (section 9). The period usage figure is overwritten when a new period starts.
Legal basis: performance of our contract with you (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c)).
3.6 Usage analytics (Google Firebase / Google Analytics)
What:
- events about how features are used: for example, that a recording was started or saved and how long it was, that a transcription succeeded or failed (with a short error category or technical error description), that a screen or the subscription screen was viewed, or that a setting changed;
- settings such as your plan, app language, transcription language and chosen use case;
- a random identifier that Verbi creates for your installation, and the Firebase app instance ID;
- information Firebase collects automatically, such as device model, operating system, app version, language and approximate location (country, region, city) derived from your IP address;
- on iPhone and iPad, if you installed Verbi after an Apple Search Ads ad: the campaign, ad group and keyword IDs and the country reported by Apple's AdServices service;
- on Android, Firebase may also collect your device's advertising ID, which you can reset or delete in your Android settings.
Not included: your recordings, transcripts, summaries, chat messages, search text, YouTube links or invite codes.
Google Analytics is linked to our Google Ads account so that we can measure our ad campaigns. Ads personalisation is turned off for this link, and Google signals is off.
Retention: Google Analytics keeps event-level data for 2 months and user-level data for 14 months from your last activity.
Why: to understand how the app is used, to improve it, and to measure our advertising.
Legal basis: our legitimate interest (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)). You can object at any time by turning analytics off (section 4).
3.7 Crash and error reports (Firebase Crashlytics)
What: crash reports and stack traces; device model, operating system and app version; for errors, technical details such as the HTTP status, file sizes, an error category and the error message returned by the server. We design these reports not to include recordings, transcripts, file names or YouTube links. While usage analytics is on, reports carry the same random installation identifier as analytics.
Why: to find and fix faults.
Legal basis: our legitimate interest in keeping the app secure and working (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)).
Retention: Firebase keeps crash reports and their identifiers for 90 days (Firebase privacy information).
3.8 Meta (Facebook) SDK on iPhone and iPad
The iPhone and iPad app includes Meta's Facebook SDK with automatic app event logging turned on. Without any further action in the app, the SDK sends Meta:
- events such as the app being installed and opened and, where the SDK detects them, in-app purchases (Meta's description of these events);
- with each event, technical information about the device and app: device model, operating system version, app version and build, language, time zone, mobile carrier and free storage space, together with an anonymous identifier that the SDK creates on your device. Like any internet request, this reaches Meta with your IP address.
We have turned off the SDK's collection of the advertising identifier (IDFA), and Verbi does not ask for tracking permission. The SDK does not receive your recordings, transcripts or other content.
Why: to measure app installs and the performance of our advertising.
Legal basis: our legitimate interest in measuring our advertising (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)).
The SDK runs regardless of the "Share usage data" switch, and the app currently has no setting that turns it off. Meta processes this data under its own privacy policy. The Android app does not contain the Meta SDK.
3.9 Security and server logs
- Firebase App Check (Apple App Attest on iPhone and iPad, Google Play Integrity on Android) confirms that requests to our server come from a genuine copy of Verbi.
- Firebase Remote Config downloads feature settings using a Firebase installation ID.
- Our servers (Google Cloud Run) automatically log each request: time, IP address, user agent (app and system version), path, status, size and duration. We use these logs for security, to limit abuse (for example, with rate limits per IP address) and for troubleshooting. They are kept for 30 days.
Legal basis: our legitimate interest in the security of our service (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)).
3.10 Calendar (optional meeting reminders)
If you turn on meeting reminders and allow calendar access, Verbi reads the titles and times of your upcoming events on your device, only to schedule local reminder notifications. Calendar data is not sent to our servers or to AI providers. On iPhone and iPad, when you switch a reminder on or off for an event, usage analytics records an internal identifier of that event, not its title.
3.11 Data on your device and backups
- Recordings, transcripts, summaries, chats, translations, study packs, vocabulary and settings are kept in Verbi's private storage on your device.
- On the free plan, recordings are deleted automatically after 15 days. Recordings you delete stay in "Deleted Recordings" for 30 days and are then removed.
- If you use device backups, your Verbi data, including recordings, may be included in them: on iPhone and iPad in iCloud or computer backups, under Apple's privacy policy; on Android in Android backup, under Google's privacy policy.
- Uninstalling Verbi deletes its data on your device. It does not delete your backups, or the data described in this policy that is kept on our servers or by our providers.
3.12 Our website (theverbi.com)
What: our website counts visits with Cloudflare Web Analytics. For each page view, Cloudflare receives the page address, the page you came from, your browser and device type, page-load timings and your IP address, from which it works out your country. Cloudflare states that Web Analytics uses no cookies or local storage and does not fingerprint visitors. We see only totals, such as visits per page, referrer and country, never individual visitors or IP addresses. The invite page (theverbi.com/i/) and these legal pages do not use it.
The Google Play buttons on our website add the name of the site you came from (for example "google.com") to the link, so that Google Play's install report can show us which sites send visitors. It is a site name only; we set no cookie and store nothing on your device.
Why: to learn which pages people find useful and how they find us.
Legal basis: our legitimate interest in improving the website (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)).
Retention: according to Cloudflare's privacy policy.
4. The "Share usage data" switch
You find it in the app under Settings > Privacy. Turning it off:
- stops usage analytics (3.6) and resets the Firebase app instance ID;
- removes the analytics identifier from crash reports.
It does not stop:
- crash and error reports (3.7);
- the Meta SDK on iPhone and iPad (3.8);
- the Apple Search Ads attribution token sent to RevenueCat (3.5), or the app's check with Apple's AdServices service of whether the install followed an ad (with the switch off, the answer is not sent to analytics);
- server logs, App Check and Remote Config (3.9);
- what the features you use need, such as sending audio for transcription.
5. Who receives your data
We do not sell your personal data. We share it only with these providers, for the purposes described above:
- Google. Google Cloud (Cloud Run, Cloud Storage, Firestore, Cloud Logging) for our servers, YouTube import, invite records, plan-hour usage records and server logs. Firebase (Analytics, Crashlytics, Remote Config, App Check) and the Google Ads link for analytics, crash reports, feature settings, app integrity and ad measurement. On Android, Google Play for payments, Play Integrity, the install referrer and in-app reviews, and the system speech recognition used in the welcome demo. Google Privacy Policy, Google Cloud Privacy Notice, Firebase privacy information.
- YouTube (Google). Our server requests the video you chose; YouTube sees our server, not your device.
- ElevenLabs. Speech-to-text. Privacy policy.
- OpenAI. Speech-to-text, live transcription, summaries, titles, vocabulary correction, chat, translation and study packs (flashcards and quizzes). Privacy policy, API data controls.
- RevenueCat. Subscription management, invite rewards, and purchase notices that credit, refund or move extra hours. Privacy policy.
- Apple (iPhone and iPad). Payments, Speech Recognition for the free live preview, App Attest and DeviceCheck, Apple Search Ads attribution. Apple Privacy Policy.
- Meta (iPhone and iPad). Automatic app events (3.8). Meta Privacy Policy.
- Cloudflare. Visit statistics for our website (3.12). Privacy policy.
What the AI providers keep. We do not ask OpenAI or ElevenLabs to store your content for us.
- OpenAI states that data sent to its API is not used to train its models, and that by default it keeps abuse-monitoring logs for up to 30 days; for its file speech-to-text endpoint it lists no abuse-monitoring retention (OpenAI: data controls in the API).
- ElevenLabs keeps data according to its own privacy policy.
The same protection. Each provider listed above receives only the data its service needs and, under its terms with us, must protect that data with the same or an equal level of protection as this policy describes.
We may also disclose data when the law requires it, for example to a court or a public authority.
6. Transfers abroad
Our servers and most of our providers are outside Türkiye and outside the EEA and the UK. When you use Verbi, your data is therefore transferred abroad to these providers:
- Google: United States (our servers and storage are in Google Cloud's us-central1 region); Firebase may process data anywhere Google maintains facilities.
- OpenAI: United States.
- ElevenLabs: United States; its privacy policy states that personal information is transferred to the United States for storage.
- RevenueCat: United States.
- Apple and Meta: the United States and other countries where they operate.
- Cloudflare: the United States and the countries of its global network.
Each provider's privacy information, linked in section 5, describes how it protects data it receives from other countries.
7. How long we keep data
- Recordings, transcripts, summaries, chats and study packs on your device: until you delete them. On the free plan, recordings are deleted after 15 days; "Deleted Recordings" is emptied after 30 days.
- Audio on our server: not stored; held in memory only while a request is processed.
- YouTube audio in Cloud Storage: deleted after 1 day, then recoverable for up to 7 more days before it is removed permanently.
- Server logs (IP address, user agent, YouTube video titles): 30 days.
- Invite records: until you ask us to delete them (section 9).
- Plan-hour usage counter and extra-hours balance: until you ask us to delete them (section 9). The usage figure of a period is overwritten when the next period starts.
- Google Analytics: 2 months for event data, 14 months for user-level data.
- Crash reports: 90 days.
- OpenAI, ElevenLabs, RevenueCat, Cloudflare, Apple, Meta and Google, beyond the items above: according to their own policies, linked in section 5.
8. Legal bases at a glance
- Performance of a contract (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c)): transcription, live transcription, summaries, chat, translation, study packs, title suggestions, vocabulary correction, YouTube import, subscriptions, plan hours and extra hours, and the invite programme.
- Legitimate interests (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)): usage analytics, website visit statistics, crash reports, ad attribution (Apple Search Ads, the Google Ads link, the Meta SDK), fraud prevention in the invite programme, security and server logs. You can object at any time (section 9); for analytics you can also use the switch described in section 4.
- Legal obligation (GDPR Art. 6(1)(c); KVKK Art. 5(2)(ç)): when the law requires us to keep or disclose data, for example to answer a court or a public authority, and to answer your requests under data protection law.
9. Your rights
Depending on where you live, you have the right to access your personal data, correct it, delete it, restrict or object to its processing, and receive it in a portable format. Under the KVKK (Art. 11) you can also ask whether your data is processed, for what purpose and to whom it is transferred, object to a result against you that arises solely from automated analysis, and claim compensation for damage caused by unlawful processing.
How to use them:
- Data on your device: view, export or delete it in the app at any time.
- Usage analytics: turn it off under Settings > Privacy > "Share usage data" (section 4).
- Invite data: write to theverbiapp@gmail.com with your invite code, which is shown on the invite screen. We delete your invite, code, reward and redemption records. We keep one item: the record that a reward was claimed on your device (on Android, the hashed device ID), with the link to you removed, so that the same device cannot claim a reward again. Premium days already granted stay. Because we hold no name or email address, we cannot find your records without your invite code.
- Plan-hour usage and extra hours: write to theverbiapp@gmail.com with your invite code, as for invite data. If you have not seen your invite code yet, open the invite screen once (Settings > Account > Invite a friend) and it will be shown. Without it we cannot find your records, and after a reinstall the app has a new ID, so records under the old one cannot be found either. We delete the usage counter and the extra-hours balance together with the other records tied to your app user ID. Deleted hours cannot be restored or credited again, so only ask if you no longer want them. Your purchases stay with Apple or Google, which we cannot change.
- Anything else, including objections and questions about server logs or data held by our providers: write to theverbiapp@gmail.com.
We answer within 30 days, free of charge. You can also complain to a data protection authority: in Türkiye, the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu); in the EEA or the UK, the authority where you live or work.
10. People in your recordings
Recordings can contain other people's voices and personal information. Make sure you have the right to record and transcribe them, and tell them or ask for their consent where the law requires it.
11. Children
Verbi is not directed at children under 16, and we do not knowingly collect their personal data. If you believe a child under 16 has given us personal data, contact us and we will delete it.
12. Security
Connections between the app, our servers and our providers are encrypted (HTTPS/TLS). Data on your device is protected by your device's built-in storage protection. Access to our servers is limited to the developer. No system is perfectly secure; if a breach affects your personal data, we will inform you and the authorities as the law requires.
13. California residents
We do not sell your personal information. You have the right to know what personal information we collect, to have it deleted or corrected, and not to be discriminated against for using these rights. To use them, write to theverbiapp@gmail.com.
14. Changes
When Verbi's data practices change, we update this policy and the "Last updated" date at the top. We announce significant changes in the app or in the App Store and Google Play release notes before they take effect.
15. Contact
Mustafa Onur Ilgaz (Verbi), Türkiye: theverbiapp@gmail.com