ChargeChefENTRPrivacy Policy
Last updated: 31 October 2026. Applies to the ChargeChef mobile app (versions downloaded from the Apple App Store and Google Play, iOS and Android) and to the Android release-day email requested on chargechef.app.
Who we are
Data controller: ALP EMRE YASAR (individual developer), Türkiye. Contact: [email protected].
Summary
ChargeChef does not require an account; there is no sign-in or sign-up. We do not build user profiles, we do not sell data, and we do not use advertising networks, advertising identifiers (AD_ID / IDFA) or cross-app tracking. The app sends only what is needed to plan your trip (coordinates and the place name you are looking for) to the services listed below, plus anonymous daily usage counts that are not linked to you (see "Usage statistics").
Data we process
| Data | Purpose | Where it goes |
|---|---|---|
| Device location (only with your permission, only while the app is open) | Set your start point, preload nearby stations, focus search around you | The routing, station and weather services below; not stored by us. If you decline, you type the start point yourself and the app still works. |
| Route coordinates (origin, destination, stops) | Road routing, charging plan, venue suggestions, weather | Mapbox, our station server, Google Places (via our proxy), Open-Meteo |
| Place name (typed, or spoken through a voice command) | Find places | Apple Maps (iOS), Google Places, OpenStreetMap Nominatim |
| Vehicle choice, saved and skipped stations, settings, last route | Personalise plans | Stored only on your device; never sent to us |
| Subscription status (Pro / Chef Mode) | Unlock Chef Mode | Apple App Store or Google Play billing and RevenueCat (see "Subscription") |
| Usage statistics (counts only, no identifiers) | Learn which features are used and which screens lead to a Chef Mode purchase | Our server (Supabase), as daily totals; see "Usage statistics" |
| Crash reports | Fix bugs | We do not collect crash reports at the moment. If we enable them in a release, we will say so in the release notes and update this page. |
Voice commands
Voice commands are optional; they run only while you hold the microphone button.
- Your speech is converted to text by your device's own speech recognition service (Apple on iOS, Google on Android). Where on-device recognition is supported, audio never leaves the device; for languages without on-device support, audio goes to the operating system's recognition server under that platform's privacy policy. The app shows which applies.
- The app, and we, receive text only. We do not store audio recordings and never send them to any server of ours.
- The place name extracted from the text follows the same path as typed search (table above).
Subscription
The Chef Mode subscription is purchased through the Apple App Store or Google Play. Payment and card details stay with Apple or Google; they never reach us. RevenueCat keeps the purchase and subscription record (receipt, renewal status). RevenueCat identifies you by an anonymous app user id generated on your device; no name, e-mail or phone number is sent. When the Chef Mode screen opens, the app tells RevenueCat that it was shown; when you start a purchase, it also notes which screen you came from (for example the header badge). Both are stored with the same anonymous id and only help us see which screens lead to purchases.
Usage statistics
To learn which features help and which screens lead to a Chef Mode purchase, the app counts a fixed list of actions on your device (for example "route planned", "Chef Mode screen opened from the header badge", "purchase completed"). Once a day it sends the previous day's totals to our server. Each total holds only the date, the action, the platform (iOS or Android), the app version, the region set on your device (not your location), the app language and the count.
The totals contain no name, e-mail, account, advertising or device identifier, IP address, location, route or search text, so we cannot link them to you or your device, and we do not try to. We do not use them for advertising and we do not share them. Counts waiting to be sent stay on your device for at most 30 days; deleting the app deletes them.
Permissions
| Permission | Used for | Required? |
|---|---|---|
| Location (while in use) | Start point and nearby stations | No; manual entry works |
| Microphone and speech recognition | Setting up a route by voice | No; only if you use voice commands |
We do not request background location, contacts, photos, files, calendar or advertising-id permissions.
Our server
Our station database (Supabase) holds public charging-station data. Requests to it contain route coordinates only; we do not store user identifiers with them. Venue lookups to Google Places pass through our server, which caches results for up to 30 days keyed by location, never by user. It also stores the daily usage totals described under "Usage statistics", without IP addresses or identifiers.
Third-party services
Mapbox (routing), Google (Places, fallback routing), Apple Maps (place search on iOS), OpenStreetMap / Nominatim / OSRM, Open Charge Map and national charging registries (station data), Open-Meteo (weather), RevenueCat (subscriptions and purchase-screen statistics), Apple and Google speech recognition (voice commands). Each is governed by its own privacy policy. We send them no name, e-mail or identifier beyond what the platform itself requires.
Android release-day email
If you email [email protected] to be told when ChargeChef is on Google Play, we use your address and the language of your message only to send that one email. We do not add it to a mailing list or share it. Legal basis: your request (GDPR Art. 6(1)(b)). We delete the request right after the release-day email is sent. Email is handled by Google Workspace (Gmail), which may process it outside your country under Google's standard contractual clauses. You can ask us to delete it earlier at the same address.
Retention and your rights
We keep no personal profile to delete; removing the app deletes all local data. Usage totals are not linked to any person, so one person's counts cannot be found or deleted; counts still on your device are deleted with the app. Under GDPR and Turkish KVKK you may request access, correction or deletion of any personal data we might hold, and lodge a complaint with the Turkish Data Protection Authority or your local supervisory authority. For deletion and other requests write to [email protected]. We reply within 30 days.
Children
The app is not directed at children under 16 and does not knowingly collect their data.
Changes
We will post updates on this page and change the date above.