1. Who we are
EarWalk is an audio guide app for cruise ports and cities, with a website at https://earwalk.app. The data controller is Erhan Durgun, an individual developer based in Türkiye.
Contact for anything in this policy, including data requests: earwalkapp@gmail.com.
2. The short version
- EarWalk has no user accounts. We do not ask for your name, e-mail address, phone number or contacts.
- The app creates a random device ID on your phone. What we store is tied to that ID, not to you as a person.
- We do not show ads, do not use an advertising identifier and do not track you across other apps or websites.
- Your location never leaves your phone.
- Payments are handled by Apple or Google. We never see your card details.
3. What we collect, and why
3.1 Device and app basics
- Random device ID — created by the app on first launch. It is not your phone's serial number or advertising ID, and it changes if you reinstall the app. Used to deliver your pass to your device, to count a "like" once, and to keep statistics.
- Platform (iOS or Android), app language, the port or city you chose, and the time the app first contacted us.
- A public encryption key generated on your device, so that paid audio can be unlocked only on a device that holds a valid pass.
3.2 How you found the app
If you arrived through a partner's QR code or an advertising link, we store which code brought you (once, on first launch). This is how partners are paid their commission. On Android this comes from Google Play's install referrer; on iOS from the link itself or a code you enter.
3.3 Purchases and passes
When you buy a pass, Apple or Google confirm the purchase to us. We store the store transaction identifier, the product, the time, the price tier, the store's test/production flag, and — where the store provides one — an anonymous store account reference (a random token the store creates for our app; it is not your Apple ID or Google account). We store your pass (when it was bought, when it was first used, when it expires) and which of your devices hold it.
If a purchase is refunded, we record that fact. See section 3.9.
3.4 Listening
When you play audio we record which story, in which language, when playback started, how far you listened, and whether it came from your device, a stream or the free preview. This lets us resume where you stopped, shows us which stories are worth improving, and is used to answer refund requests (section 3.9).
A like is stored as "this device liked this story".
3.5 Questions you ask the assistant
Questions you type to the port assistant, and the answers given, are stored together with the random device ID, the language and the port. We store them to answer you, to improve the ready-made answers, to review answers that users report as wrong, and to control costs. This applies to questions answered on your phone by the built-in quick answers as well as those answered by the AI service; questions asked offline are sent when you are back online.
Please do not type personal information (names, health details, passport or card numbers) into the assistant. It does not need it.
When a question is answered by AI, the text of your question and the last few messages of the conversation are sent to our AI provider (section 5) to generate the answer. The device ID is not sent to that provider.
"Listen" on an answer uses your phone's own text-to-speech voice; the text is not sent anywhere for that.
3.6 Explore (sponsored places)
We record anonymous interaction events for sponsored listings: a listing was shown, its page was opened, the WhatsApp button or the directions button was tapped, and on which screen. Sponsors receive totals only. They never receive device IDs or anything about individual users. If you tap WhatsApp or directions, you leave EarWalk and that app's own privacy policy applies.
3.7 App activity
We record a small set of anonymous app events: the app was opened, how long a session lasted, the payment page was viewed, a plan was selected, a purchase or restore succeeded, failed or was cancelled, and a download started, finished or failed. These carry short codes, not free text.
3.8 Location — stays on your device
If you allow it, the app uses your location only while you are using the app to show where you are on the map, to estimate walking times, and to suggest the nearest port. Your location is processed on your phone and is not sent to our servers. You can use the app without granting location access.
3.9 Refund requests (Apple)
If you ask Apple for a refund, Apple may ask us how the purchase was used. With the consent you give when you buy (see the Terms), we send Apple usage information for that purchase: whether the content was delivered, roughly how much of it was used, and whether a free preview was available. We do not send Apple your questions or your listening history in detail.
3.10 The website and QR pages
Our web pages do not use cookies and load no third-party trackers, fonts or scripts.
When a QR or campaign page is opened we record: the code, the device type (iOS / Android / other), the browser language, the time, and a keyed hash of the IP address. The IP address itself is not stored in our database; the hash only lets us avoid counting the same visitor many times. If you play the short audio preview on that page, we record that it was started and whether it was finished.
3.11 Technical logs
Like every web service, our server keeps short-lived technical logs (time, address requested, IP address, app or browser version, error details) to keep the service secure and to fix faults. They are deleted after about 30 days.
4. What we do not collect
No name, e-mail, phone number, contacts, photos, microphone recordings, precise or approximate location, advertising identifier, or browsing history. We do not build advertising profiles and we do not sell personal data.
5. Who receives data
We use the following service providers. They act on our instructions or as independent providers of their own service.
| Recipient | What for | What they receive |
|---|---|---|
| Apple (App Store) / Google (Google Play) | Payment, purchase verification, refunds | Your purchase, handled under their own privacy policies; from us: purchase identifiers and, for Apple refund requests, usage information (3.9) |
| OpenAI (United States) | Generating AI answers | The text of your question and recent conversation messages. No device ID |
| Cloudflare | Delivering audio, images and map files; storage | Technical connection data (such as IP address) needed to deliver files |
| Hetzner (Germany) | Server hosting | The data described in this policy, stored on our server |
Weather information is fetched by our server from Open-Meteo; no user data is sent there.
Partners (shops, hotels, guides) see counts of scans, installs and sales for their own QR codes. Sponsors see counts for their own listings. Neither sees device IDs.
We may disclose data where the law requires it.
6. Legal bases (GDPR / KVKK)
- Performance of a contract — delivering the pass you bought, the audio, and the assistant (3.1, 3.3, 3.4, 3.5).
- Legitimate interests — keeping the service secure, preventing abuse and refund fraud, paying partners correctly, and understanding in aggregate how the app is used so we can improve it (3.2, 3.6, 3.7, 3.10, 3.11). You may object (section 9).
- Consent — sharing usage information with Apple when you request a refund (3.9); location access on your device (3.8).
- Legal obligation — keeping purchase records for tax and accounting purposes.
Under Turkish law (KVKK no. 6698) the corresponding grounds in Article 5 apply.
7. International transfers
Our server is in the European Union. Some providers (in particular OpenAI, Apple, Google and Cloudflare) process data in the United States or other countries. Where required, such transfers rely on appropriate safeguards such as standard contractual clauses or an adequacy decision.
8. How long we keep data
- Technical logs: about 30 days.
- Listening events, assistant questions and answers, Explore and app activity events, QR page visits: up to 24 months, then deleted or reduced to totals that no longer relate to a device.
- Purchase and pass records: 10 years, because accounting and tax law require it.
- Device record: until it has been inactive for 24 months and holds no purchase, or until you ask us to delete it.
9. Your rights
Depending on where you live, you have the right to ask for access to your data, correction, deletion, restriction of processing, data portability, and to object to processing based on legitimate interests. Where processing is based on consent, you may withdraw it at any time. Under KVKK Article 11 you have the corresponding rights.
How to make a request. Because there are no accounts, we can only find your data by your device ID:
- Open EarWalk and go to Privacy & data. Your device ID is shown there; copy it.
- E-mail it to earwalkapp@gmail.com and tell us what you would like (for example "delete my data").
We answer within 30 days. On deletion we erase your listening history, questions, likes and app events, and remove the link between your device and any purchase record that we must keep by law. The app then gives itself a new random device ID, and nothing from before is linked to it; to keep it that way we store only a one-way fingerprint of the erased ID. If you had an active pass, use Restore purchases to get it back.
You can also simply delete the app: the device ID on your phone is gone, and nothing new can be linked to it.
Complaints. You may complain to the data protection authority where you live — in the EU, your national supervisory authority; in Türkiye, the Personal Data Protection Authority (KVKK, kvkk.gov.tr).
10. Children
EarWalk is a general travel guide and is not directed at children. We do not knowingly collect personal data from children under 13 (or under 16 where the law sets that age). If you believe a child has sent us personal data, contact us and we will delete it.
11. Security
Data is transferred over encrypted connections (HTTPS). Paid audio is encrypted. Passes are cryptographically signed. Access to the administration panel is limited and changes are logged. No system is perfectly secure; if a breach affecting you occurs, we will inform you and the authorities as the law requires.
12. Changes to this policy
When we change this policy we publish a new version with a new date on this page. Earlier versions stay available in the archive linked below.