Privacy Policy
Duyarim has no server that processes audio, which is why this document is shorter than most privacy policies: your audio does not leave the device. We are equally open about what does leave it — verifying your subscription, an anonymous technical report if the app crashes, and the details needed for your invoice if you buy premium in the browser.
In short
- No account, sign-in or sync in the app store versions.
- Audio is never sent to any server.
- Recordings stay only on your device.
- No ads, no advertising identifier, no cookies, no behavioural analytics in the app.
- Delete the app and the recordings go with it.
Data we collect
Duyarim has no backend that processes audio; your sound never reaches a server. In the app store versions (App Store, Google Play) the app never asks you for a name, email address, phone number or location, and you do not need an account. If you buy premium in the browser version, your contact and billing details are requested once during payment so that an invoice can be issued — the detail is in the Subscription verification section.
In the app, there is specifically none of the following:
- User accounts, sign-up or sign-in steps.
- Behavioural analytics, usage statistics or screen tracking.
- Advertising, advertising identifiers (IDFA/AAID) or tracking pixels.
- Cookies or comparable browser technologies.
- Marketing or tracking SDKs that harvest data.
Your app settings (amplification level, recording preference, storage limit and so on) stay on your device and never reach us. The two technical flows that do leave the device are described separately in the next two sections.
Subscription verification
Live listening requires a paid plan. To check whether your purchase is valid, purchase information is processed through our subscription infrastructure provider, RevenueCat, Inc. That flow contains an anonymous user identifier generated by the app, the purchase receipt issued by the store, and technical details such as platform and country.
In the app store versions your name, email address, card details, voice or recordings are not part of this flow. The payment itself is taken by Apple or Google; we never see or store your payment details.
Buying in the browser
In the browser version the purchase does not go through an app store; the payment is taken by iyzico, a licensed payment institution. So that an invoice can be issued, the payment step asks for your first and last name, email address, billing country, city and address; if you are buying a subscription, the payment provider also asks for your phone number. These are requested only at the moment of purchase; the app itself never asks for them.
Your card details never reach us — the card number goes straight into iyzico’s own payment form. Your email address is also the anchor of your access: a session is kept in your browser so that your subscription can be recognised. Your voice and your recordings are not part of this flow.
Without this check a paid app has no way of knowing who is subscribed. Its scope has deliberately been kept this narrow.
Crash reports
If the app closes unexpectedly, a technical crash report is sent through Google Firebase Crashlytics so we can find and fix the problem. It contains the stack trace, app version, operating system version and device model.
It contains no audio, recording name, file content, microphone label or anything that identifies you as a person. This is not usage analytics; it is produced only at the moment of a crash.
Website measurement
On duyarim.com — the site you are reading right now — we count how many visitors arrive and which pages are read, using Vercel Web Analytics. We also count how often the links to the App Store and to the browser version are clicked; there is no other way to know which explanation actually works.
This counting uses no cookies, no localStorage and no advertising identifier, and it creates no persistent identity that follows you across visits and devices. What is recorded is aggregate information such as the page address, the referring site, the country, the browser and the device type — nothing that shows who you are.
This section covers the website only. The app itself has no usage analytics — the “Data we collect” section above explains that.
Microphone and live listening
During live listening, the audio from the microphone goes straight to the output you chose — your headphones. That stream is never sent to a server.
The app does not need an internet connection to work.
How recordings are stored
While session recording is on, the session you listen to is written to your device. Recording starts only with the explicit consent we ask for on first launch, and it can be turned off in Settings with one tap; while it's off, no session is ever written to disk.
Recordings stay only on your device. Nothing is written to your photo library, the cloud or the phone's shared media folder, and other apps cannot reach those files.
Browser version
In the browser (app.duyarim.com), recordings are held in the local storage the browser sets aside for Duyarim; nothing is uploaded to a server, nothing is written to your downloads folder, and no other site can reach it. Clearing your browser data — or deleting this site's data — deletes the recordings too. To keep one, share or download it to your device.
Platform backups
Depending on your own settings, iOS and Android may back app data up to your iCloud or Google account. That is operating-system behaviour: it is not initiated by Duyarim, and it is not somewhere Duyarim can reach. If you'd rather your recordings weren't backed up, exclude Duyarim in your device's backup settings.
Sharing
The only way a recording leaves your device is you sharing it. When you tap Share, the audio file is handed to the app you pick (messaging, email, a file manager and so on) and from that moment on it is subject to that app's rules.
Deletion and control
You have complete control over your recordings:
- Delete them one by one from the Recordings tab.
- Remove all of them at once with “Delete all”.
- Use the automatic retention limit in Settings (7 days, 30 days or forever) to have older recordings delete themselves.
- Delete the app and the recordings go with it.
Deletion happens on your device; there is no copy on our side that we would need to delete.
Permissions
The app asks only for the permissions it needs to work, and uses each one only for the stated purpose.
You can revoke any permission from system settings at any time. Live listening will not work without microphone access.
Children's privacy
Duyarim is not directed at children under 13 and does not knowingly collect data from that age group. Since no data is collected from any user in the first place, no children's data ever reaches us.
GDPR and KVKK
Because Duyarim processes no personal data and transfers nothing off your device, there is no data controller or processor receiving a transfer. That also means there is no copy of your data for us to hand over, correct or erase on request — we simply hold no record of you.
Access, correction (renaming, trimming) and deletion of the recordings on your device are entirely in your hands, straight from inside the app and without waiting on anyone's approval.
This section is for information only and does not constitute legal advice.
Medical notice
This product is not a medical hearing aid and is not intended for diagnosis or treatment. If you suspect hearing loss, see a specialist.
Changes
We may update this policy from time to time. When something meaningful changes, we publish the current text on this page and update the “last updated” date below. Significant changes are also announced inside the app.
Contact
For privacy questions, write to us: destek@duyarim.com. We usually reply within 48 hours.
If you're having trouble with the app, take a look at our support page.
Last updated: 19 August 2026