PathieTürkçe

Privacy Policy

Effective date: 20 October 2026

Pathie records your walks, lets you draw routes, and — if you choose — share them. This document explains which of your data we process, why, and who we send it to. It contains everything shown on the notice screen when you first open the app, plus the company and country details promised there.

Data controller
Duhan Enes Ovalı
İstanbul / Tuzla
Email: support@pathie.app

The data controller is established in Türkiye, so the processing is subject to Turkish data protection law (KVKK, Law no. 6698). If you are in the European Union you also have the rights granted by the GDPR, and this document is written to satisfy both.

1. What data is processed

What stays on your phone

Your location during walks (including in the background, with the screen off), the photos you take, your notes on stops, the map area you have uncovered (your "fog"), and statistics such as distance and duration. These live in your device's own database; Pathie works fully in airplane mode. They leave the phone only when you share something, when you turn a walk into a route (its points are map-matched once, below), or — encrypted — if you turn on Backup to my account (below).

What is written to the server with your account

Your email address, the username you choose, your display name and avatar, your age range, your device's encryption key, and your friend list. These are written the moment you create an account, because they are what identifies it.

We also keep when you last connected — the time only, a single value refreshed at most once an hour. What you do in the app, which screens you open, what you tap is not recorded: Pathie has no analytics SDK, no advertising identifier and no behavioural logging. The one timestamp exists for an operational reason: knowing how many people are using the app.

Each open session keeps the device's IP address and app signature; that is what answers "which device is this" under Settings → Account → "Signed-in devices". A session lives at most 90 days and its record goes when you sign out or delete the account.

If you allow notifications, your phone's notification address (push token) is kept with your account and with the session that registered it — it is the only way a notification can reach you. It is deleted when you sign out on that phone, when you end that phone's session under Settings → Account → "Signed-in devices", when the notification service reports that the address no longer works (for example after you uninstall the app), or when you delete your account.

If you sign in with Apple, the refresh token Apple issues for that sign-in is kept with your account, encrypted, for one purpose only: asking Apple to remove Pathie's access when you delete your account. It is deleted with the account.

If you subscribe, the store purchase token or receipt, account and product ids, purchase and expiry dates, store country and app version are written to the server with your subscription status. Your payment card never reaches us or RevenueCat.

Backup to your account (optional)

Off unless you turn it on, under Settings → Your data → "Backup to my account" or when the app offers it. While it is on, the phone uploads a copy of everything it keeps: your walks with their GPS track points, the fog, photos, journal and memories, saved places, plans with their emergency contacts, your pet and your conversation with it. The copy is encrypted on the phone with a key wrapped under your own master key or recovery phrase; the server stores it but cannot open it. It is held in Cloudflare R2 storage under the "eu" jurisdiction restriction.

What leaves your phone only when you share

The routes and walks you publish, room messages, the photos you send in rooms, memory collections you share with chosen people, your fog map and regional achievements if you share them, location photos you make public, and — if you turn it on — your live location.

A public location photo is published with its place rounded to about 100 metres and only the day it was taken, and anyone can see it until you withdraw it.

Live location is end-to-end encrypted with a key made for each sharing session and given only to the people you allowed. The server relays sealed packets it cannot read and stores none of them; once the connection closes no record remains. Room messages are end-to-end encrypted too, and the server cannot read them.

If you choose to share a walk, that walk's step count is written to the server as part of the share and is visible to the audience you chose (your friends, or everyone). Nothing is counted at all while the step counter is switched off in Settings.

Your interactions with shared content

When you like, save, copy or comment on a public route, or follow someone, that is recorded individually — there is no other way for a like to be undoable or for what you saved to stay in your list.

These records are also used to order the Discover feed for you. This is not an exception to the "no behavioural logging" sentence above but its boundary: what is recorded is your own action (what you liked), not your browsing behaviour — and none of it goes to advertising or to matching with a third party.

Your raw GPS trace is not kept on the server in readable form. When you share a walk, what goes to the server is not your individual location fixes but a line derived from them: each point's timestamp and accuracy value are dropped. One exception: when you turn a recorded walk into a route, its points, with their times, are sent once to our server for map-matching, so the route follows the paths you walked. Our server passes them to Geoapify (listed below), returns the matched line and does not store them. Apart from that, the full trace reaches the server only inside your encrypted backup, if you turn on Backup to my account. Your room messages, the photos you share in rooms and your live location are end-to-end encrypted — we cannot read them either.

If you join the launch waitlist

If you join the launch waitlist on pathie.app, your email address and the language you chose are stored on Cloudflare D1 only to tell you when Pathie is available. The entry is deleted once that message has been sent, and you can ask for it to be deleted earlier at support@pathie.app.

2. Why it is processed, and on what legal basis

3. International transfers — who receives what

Map tiles, route calculation and weather cannot be produced on your phone; they come from outside. The list below is complete. None of these recipients is located in Türkiye, and Turkish law treats this as a transfer abroad.

These transfers are continuous and part of how the app ordinarily works, so they rest on appropriate safeguards rather than on your consent. That is the order KVKK Art. 9 sets: without an adequacy decision, an appropriate safeguard, with explicit consent reserved for incidental transfers (Art. 9/6). The GDPR draws the same line — Art. 46 safeguards, Art. 49 derogations. No adequacy decision has been issued for any country in the table below.

The safeguard takes one of two forms, depending on the recipient: the standard contractual clauses (EU SCCs) or data processing agreement that recipient publishes and we have accepted; or, where there is none, the standard contract issued by the Turkish Personal Data Protection Board, signed with the recipient and notified to the Authority within five business days of signature. To learn which instrument covers a particular recipient, write to support@pathie.app.

Sharing, live location and crash reports are separate from this: they rest on your explicit consent, which you can withdraw at any time from Settings → Privacy and security → Consents. Sharing and live location are asked when you first share; crash reports have their own optional tick on the first-launch screen. That screen's required tick only records that you have read this notice; it is not consent to these transfers. Withdrawing the sharing permission also ends a live walk or live location you are sharing at that moment.

Expo (app updates)
Legal entity
650 Industries, Inc.
Country
United States
Data sent
Your IP address, device and version information
When
On every launch — after you have passed the first-launch screen
Mapbox (map tiles)
Legal entity
Mapbox, Inc.
Country
United States
Data sent
The map area you are viewing, and the area around a route whose card cover is drawn. What you search for and the places around you are not sent to Mapbox
When
While the map is open and when route lists are displayed
MET Norway (weather)
Legal entity
Norwegian Meteorological Institute (Meteorologisk institutt), Postboks 43 Blindern, 0313 Oslo
Country
Norway
Data sent
Your stops rounded to ~1 km, and the estimated arrival time. Your IP address is not sent — the request is made by our own server
When
While drawing a route and when a plan’s forecast is shown
OpenRouteService (routing engine)
Legal entity
HeiGIT gGmbH, Schloss-Wolfsbrunnenweg 33, 69118 Heidelberg
Country
Germany
Data sent
The exact coordinates of the stops you place and the travel mode, to draw the route and order the stops. Your IP address is not sent — the request is made by our own server
When
When you draw a route and when you ask for the best stop order
Apple / Google (your phone’s geocoding service)
Legal entity
On iOS, Apple Inc., One Apple Park Way, Cupertino, CA 95014 — in the EEA, the United Kingdom and Switzerland, Apple Distribution International Limited, Ireland. On Android, Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043 — in the same countries, Google Ireland Limited, Dublin
Country
United States — Ireland for users in the EEA, the United Kingdom and Switzerland
Data sent
Your location
When
Automatically, if you have granted location permission
Cloudflare (our server)
Legal entity
Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107 (EU/UK entity: Cloudflare, Ltd., London)
Country
United States — storage is provisioned with the "eu" jurisdiction restriction, so the data itself is held within the European Union
Data sent
Your account, profile, friend list, everything you share and, if you turn it on, your encrypted backup
When
The moment you create your account; shared items when you share them; the backup while you keep it on
RevenueCat (subscription status processing)
Legal entity
RevenueCat, Inc. — a processor acting on our behalf
Country
United States
Data sent
The store purchase token or receipt, your account id, product id, purchase and expiry dates, store country and app version. Your payment card is never sent
When
To verify subscription status; while your account exists and for as long as the store requires for its own records
Cloudflare Email Sending (email delivery (first route))
Legal entity
Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107 (EU/UK entity: Cloudflare, Ltd., London)
Country
United States
Data sent
Your email address and the one-time sign-in code sent to you. Resend is used only when this route fails
When
When you request a sign-in code
Resend (email delivery)
Legal entity
Plus Five Five, Inc. (Resend is the brand name)
Country
United States
Data sent
Your email address and the one-time sign-in code sent to you
When
When you request a sign-in code
Sentry (crash reporting)
Legal entity
Functional Software, Inc., 45 Fremont Street, 8th Floor, San Francisco, CA 94105 (EU representative: Sentry Software Netherlands B.V., Amsterdam)
Country
United States — the contracting party is the US company; the data is held in Sentry’s EU data region (de.sentry.io, Frankfurt, Germany)
Data sent
The error itself and your device model/version. Your location, routes and photos are not sent
When
From the app only when an error occurs and only if you turned crash reports on; our own server’s errors always, carrying no identity or location
Cloudflare (the AI model)
Legal entity
Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107 (EU/UK entity: Cloudflare, Ltd., London)
Country
United States
Data sent
The text you type in the chat and the conversation so far, a photo only if you attach one yourself, a saved route only if you attach one (its name and its stops’ names and positions), a few hints worked out on your phone (whether you have walked here before, your usual pace, the kinds of places you like), and — with every message you send — your location rounded to ~1 km. The model itself never sees coordinates; they are used only to answer a question about places around you. An attached photo is described and discarded; it is not stored. Your walks, your photo library and your fog map are not sent
When
Only once you have allowed AI chat in the app, when you send your pet a message or attach a photo to one
Geoapify (place search, places nearby and path matching)
Legal entity
KEPTAGO LTD (Geoapify is the brand name), N. Nikolaidi & T. Kolokotroni, Onisiforou Center, 8011 Paphos
Country
Cyprus — by the company’s own statement, the service runs in data centres within the European Union
Data sent
The words you search for and your location rounded to ~1 km; for places nearby, that location and the kind of place you asked for; a place name you write to your pet, without your location; and, to snap it to the road, the exact coordinates and timestamps of a walk you turn into a route. Your IP address is not sent — the request is made by our own server
When
Every time you turn a walk into a route, and while you type in the search box; places nearby when you look for them, when a finished walk lists the places you passed and when you ask your pet
Tavily (web search)
Legal entity
AlphaAI Technologies Inc. (Tavily is the brand name), 1350 Broadway, 24th Floor, New York, NY 10018
Country
United States
Data sent
The name of the place being looked up and the city it is in — not your message, not your location, not who you are
When
Only when your pet needs evidence about a place you asked about
Wikimedia (Wikipedia)
Legal entity
Wikimedia Foundation, Inc., 1 Montgomery Street, Suite 1600, San Francisco, CA 94104
Country
United States
Data sent
The area you are looking at, rounded to ~1 km. Your IP address is not sent — the request is made by our own server
When
When a museum, park or historic place appears in your pet’s answer
DuckDuckGo (site icons)
Legal entity
DuckDuckGo, Inc., Paoli, Pennsylvania — the company’s privacy policy names no separate controller for Türkiye
Country
United States
Data sent
Only a source’s domain name, such as tripadvisor.com. Your IP address is not sent — our own server fetches the icon; nothing about you, your location or what you asked
When
While a place card in your pet’s answer shows its sources
Overpass API (street data)
Legal entity
Not stated — a public endpoint run by OpenStreetMap volunteers (overpass-api.de); it declares no commercial controller
Country
Germany
Data sent
The bounding box of the neighbourhood you are looking at — the neighbourhood, not your location. Your IP address is not sent; the request is made by our own server
When
The first time a neighbourhood’s streets are needed (the result is cached, so it is not asked twice)
Google (notification delivery)
Legal entity
Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043
Country
United States
Data sent
Your phone’s notification address and the text of the notification sent to you
When
When you allow notifications, and when one is sent to you
Amazon Web Services (elevation data)
Legal entity
Amazon Web Services, Inc., 410 Terry Avenue North, Seattle, WA 98109
Country
United States — the bucket read is in Frankfurt (eu-central-1), so the data is within the European Union
Data sent
The number of the map tile your route falls in — the tile, not your location. Your IP address is not sent
When
While the route’s elevation profile is computed
Backblaze (server backups)
Legal entity
Backblaze, Inc., 2261 Market Street STE 81006, San Francisco, CA 94114
Country
United States — the contracting party is the US company; the backups are held in the EU (Backblaze B2 EU Central, Amsterdam, Netherlands)
Data sent
An encrypted copy of everything the server holds: your account, profile, what you share, your photos and your encrypted cloud backup. The key that opens it is not at Backblaze
When
Every night. Daily copies are kept for 30 days, the copy made on the first of each month for 12 months
GitHub (backup job)
Legal entity
GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107
Country
United States — GitHub decides the region of the server the job runs on
Data sent
The same data as the backup. It is held on a GitHub server only while a job runs: the nightly backup job encrypts it before it leaves, and the monthly restore check loads it into a temporary database at Cloudflare that is deleted when the check ends. The server is discarded when the job ends
When
Every night while the backup job runs, and once a month while the restore check runs

If you choose to sign in with Apple or Google, the only thing that company receives is which app you signed in to; what comes back to us is your name and email address (with Apple, optionally through a private relay address). This is a different processing operation from the geocoding row above.

Apple or Google processes the subscription payment under its own privacy terms. The store takes the payment card, collects the charge and issues the receipt or invoice; neither we nor RevenueCat sees your card details.

The update check waits for the first-launch screen. The app looks for a new version on launch (the Expo row) only once you have passed that screen; nothing is sent to Expo before then.

4. How long data is kept

5. Your rights

Under GDPR Art. 15–22 and KVKK Art. 11 you have the right to learn what data of yours is processed, to access it, to have it corrected or erased, to object to processing, and to receive your data in a portable form. Most of these can be exercised inside the app, without asking anyone:

Server-side deletion is queued and normally completes within minutes; the screen does not say "deleted" until the work has actually finished. Copies already in the server backups leave them when those backups expire (see section 4). For written requests: support@pathie.app.

We answer a written request within 30 days (the KVKK application communiqué, Art. 6). A request under GDPR Art. 12(3) is answered within one month; where the request is complex that period may be extended by two further months, and you are told of the extension and its reason before the first month is out.

If our answer does not satisfy you, you may complain: in Türkiye to the Personal Data Protection Authority (Nasuh Akar Mah. 1407. Sok. No: 4, 06520 Çankaya/Ankara), and in the EU and EEA to your own country's supervisory authority.

6. Security

7. Age limit

You must be at least 16 years old to use Pathie. The app is not directed at children; people under 16 may not use Pathie and we do not knowingly collect their data.

8. If this document changes

Whenever the text changes materially, the app asks for your approval again — the document carries a version number, and raising it re-shows the screen. Changes are never made silently.