City Hunt
Türkçe
Privacy Policy
Last updated 21 September 2026
City Hunt is built to know as little about you as it can. There is no account, no advertising, no third-party analytics and no tracking. Almost everything stays on your phone; the little that leaves is described below. This policy says what the app handles, where it goes, and what your rights are.
1. Who is responsible
The data controller is City Hunt, a sole proprietorship based in Istanbul, Türkiye. Contact: hello.cityhunt@gmail.com.
2. What the app handles, and where it stays
Your location. The app uses your phone's location while you use it to show where you are on the map, to turn a stop's card over when you reach it, and, if you ask, to pick the nearest city. With your permission it keeps receiving your position while a walk is in progress and the screen is locked, so that the "nearly there" notice can reach you with the phone in your pocket. Location is processed on your phone and is not sent to us. We may add a server-side check of where you found each stop, so that coffee coupons cannot be claimed without walking; if that happens we will say so here first.
Photos. Pictures you take at stops are stored on your phone, inside the app's own storage. They are not uploaded. They leave your phone only when you share or save a collage yourself. Choosing a photo from your library uses Apple's picker, which shows the app only the one picture you pick.
Purchases. Hints, and premium routes where they exist, are bought through Apple. Apple processes the payment and holds your payment details; we never see them. The app keeps a record on your phone of what is unlocked and how many hints you hold, and receives a signed transaction from Apple.
The device ID. When the app is first opened it creates a random code for that installation, the device ID. It is the only identifier we use: it is not your name, Apple ID, email, phone number, advertising identifier or your device's serial number, and it is not shared with anyone else. It is given to Apple with a purchase, and it is sent to our own server when you claim a coffee coupon, open "Your coffee", answer the walks question below, or finish a route. Deleting the app discards it, and a fresh install creates a new one.
Your walk. The city you picked, your progress on each route, which stops you used hints on and the photos you kept out of a collage are stored on your phone. While a walk is in progress, none of it is sent to us.
Finished routes. When you turn the last card of a route, the app sends our server a short record of the finished walk: which route it was, when you turned its first card and its last, how far the phone measured you walked, how many hints you used, and whether any card was turned without being at its stop (a demo walk). It goes together with the device ID, the app's version and whether this copy is a test build, so that test copies can be left out. The distance is a single number the phone works out; no position, route trace or photo is sent. If you have no signal at the finish, the record waits on your phone and is sent the next time the app is opened. We use these records only to learn which routes people finish and how long they really take, counted across everyone, so that we can fix the ones that are too long or too hard.
The kinds of walks you enjoy. The last welcome page asks what kind of walks you like, such as History or Nature, or Any. If you answer, the app sends your answer to our server together with the device ID, the app's version, and whether this copy is a test build (a developer, TestFlight or App Review copy), so that test copies can be left out. We use the answers only to decide which routes to write next, counted across everyone. If you tap Skip, nothing is sent.
Coffee coupons. Tapping "Claim your coffee" sends the route's identifier and the device ID to our server, which returns one gift-card code and records that this installation received it. Opening "Your coffee" sends the device ID to read back the codes you already hold. Nothing else about you is sent, and no route content request carries the device ID at all. When you spend the coupon, the café sees the gift-card code and nothing about you.
Diagnostics. The app contains no analytics or crash-reporting service of our own. If you have opted in to share diagnostics with app developers in iOS settings, Apple may send us crash reports without any information that identifies you.
3. Who else is involved
- Apple: the App Store, in-app purchase, restore of purchases, and Apple Maps, which fetches map tiles for the area you are looking at. Apple's own privacy policy applies to these services.
- Supabase (Supabase Inc.) hosts our database in Frankfurt, Germany, and processes data only on our instructions. It holds the route content the app downloads, the coupon records, the walk answers and the finished-route records described above.
- Partner cafés: they see a gift-card code when you spend it, not personal data.
- No advertising networks, no data brokers, no social media SDKs.
4. Why we are allowed to do this
Under the GDPR, the UK GDPR and Türkiye's KVKK, we process what is needed to provide the service you asked for (the walk, the purchase, the coupon), on the basis of the contract between us, and location and camera access only with the permission you give in iOS, which you can withdraw at any time in Settings. Your answer about walks is processed on the basis of our legitimate interest in deciding which routes to write, and only if you choose to give it. Finished-route records are processed on the basis of our legitimate interest in improving the routes; they carry no name, no account and no position, and you can object to them at any time (see section 6).
5. How long
Everything held on your phone stays for as long as the app is installed and goes when you delete it. Purchase records live with Apple under Apple's retention. On our server, a coupon record — the installation identifier, the route and the time — is kept for as long as needed to honour that coupon and to stop the weekly pool being drained, and then deleted. A walks answer — the device ID, the themes, the app version and the test flag — is kept while it is useful for planning routes. A finished-route record — the device ID, the route, its start and finish times, the distance, the number of hints, and the demo and test flags — is kept while it is useful for improving the routes.
6. Your rights
You can ask us what data we hold about you, ask for it to be corrected or deleted, object to processing, and complain to your data protection authority. Because the app keeps its data on your phone, deleting the app deletes it. For anything held by Apple, use your Apple ID settings. For anything held by us, write to hello.cityhunt@gmail.com. Our records are tied only to the device ID, not to your name, so we may not be able to tell which record is yours.
7. Children
The app is not directed at children under 16 and we do not knowingly collect data from them.
8. Changes
We will update this policy before the app changes what it handles — for example if a server-side check of where you found each stop is added. The last change, on 21 September 2026, added the finished-route records in section 2. The date at the top shows the current version.