Privacy Policy
This policy explains how the eBattery mobile app (iOS and Android) and the ebattery.app website process your personal data. For users in Turkey we also publish a short KVKK Information Notice; this policy is its detailed version.
1. Controller and contact
The controller is Ahmet Öztürk (Turkey), who operates eBattery. For any privacy question or request: privacy@ebattery.app. General contact: contact@ebattery.app.
2. In short
- We do not sell your data and we do not track you across other apps and websites. The app contains no advertising networks or usage-analytics tools. It may show content sponsored by brands we work with, always labelled as an ad; no personal data of yours is shared with the sponsor.
- You can use the map and stations without an account.
- Showing your location to other users is always optional, and we ask for your permission separately for each purpose.
- Our database is hosted in the European Union (Frankfurt, Germany).
- You can delete your account from inside the app at any time.
3. What data we process
3.1 Account and profile
- Sign-in details: your e-mail address; with Google sign-in, the name, e-mail and profile photo Google shares; with Apple sign-in, your name (Apple shares it only on the first sign-in) and your e-mail (which may be Apple's private relay address); with phone sign-in, your phone number.
- Sign in with Apple token: when you sign in with Apple, our server may exchange the one-time code Apple gives the app for a token from Apple, and keep it encrypted together with the Apple user identifier it belongs to. It is used for one thing only: when you delete your account, to ask Apple to remove eBattery from your Apple Account's "Sign in with Apple" list. It is replaced each time you sign in with Apple; after your account is deleted it is sent to Apple to be revoked and then deleted, at the latest 30 days after the deletion.
- Profile: your display name, username, profile and cover photo; optionally a bio, city and country (in Turkey also a district, if you choose one). Your profile photo is served from a public address. You choose in settings whether your bio, city and country are visible to other signed-in users. If you tap "Find from my location", your location is read once and turned into a suggested place by your phone's own place-name service; it is not sent to us.
- Date of birth: the app no longer asks for it. If you entered it in an earlier version, it is stored with your account; it is not shown to other users and no feature uses it. Write to us and we will delete it.
- Your app language: stored with your account so that the sign-in code e-mail can be sent in your language.
- Account deletion: when you ask to delete your account, we keep a record of the request and may store your app language with it, so that a confirmation e-mail can be written in that language; the language is removed from the record when the deletion completes or you cancel the request. When a deletion you asked for is complete, we may send that one e-mail to your account's address. For it we keep the address, the app language, the date of the deletion and whether you signed in with Apple, until the e-mail is sent and at most 7 days after the deletion.
- Consent records: which permission you gave or withdrew, and when.
- App records: which introduction screens you have already seen, and the waitlists for upcoming features that you joined (kept until the feature launches or you leave the list).
3.2 Location
Granting location permission is optional; without it you can keep using the parts of the app that do not need a location. If you grant it, your location is processed as follows:
- Map, nearby stations and distances: your location is used on your device. To sort station search results from near to far, a point rounded to about 1 km is sent to our server and is not stored.
- Weather: a point rounded to about 11 km is sent, without your identity, through our server to OpenWeather.
- Route planning and search along the route: your start, stop and destination points, or the part of the route still ahead of you, are sent without your identity through our server to Google (Routes, Elevation and Places services) and are not stored by us. If you save a plan, its points are stored with it; if its start is "My location", that is your location at the time of planning.
- Location sharing with friends (explicit consent): if you turn it on, your exact location is delivered only to your friends and only at that moment; it is not stored on our servers.
- Appearing on the map (explicit consent): if you turn it on, your location is rounded to the centre of an area about 1.2 km wide and kept for at most 15 minutes. In the map settings you decide who sees you, for how long, and whether exactly, approximately or not at all, and you can set a different rule for each friend. Being shown by name to the members of your communities is a separate consent, open only to those who declare they are over 18: community members see only the centre of an area about 5 km wide, and only while at least 5 people who share in the same way are in that area. "Who can see me" lists who sees you and has a button that stops all sharing at once.
- Emergency alerts (explicit consent): an alert you send is kept for 10 minutes together with an approximate area.
- Sharing a location or plan in chat: when you send a location, route or trip plan as a message yourself, its coordinates (with an address label for a location message) are stored as part of the message and deleted with it. The preview of a shared route hides the 500 m around its starting point. To draw the map in the message, coordinates are sent without your identity through our server to Google.
- Station status reports: when you report a station's status, your location is read once to check that you are within 300 m of the station, and it is not stored.
- Place search and place names: when you are signed in and the map is a Google map, the text you type in search goes, without your identity and with a point rounded to about 1 km, through our server to Google's place search. Otherwise, place names you type, and coordinates for showing the name of where you are, go to your phone's operating-system service (Google on Android, Apple on iOS). A place you pick from Google's results is kept in a plan or trip by Google's place identifier, and its coordinates are refreshed or removed after 30 days. Your recently searched places are kept on your device only.
- In-app navigation (Android): during guidance, your location, speed and heading are processed by the Google Navigation SDK; Google's own terms are shown on first use. We do not ask for background location permission.
- Android Auto: if you allow it, your car's battery percentage, remaining range and odometer are read into the phone's memory only. The odometer is stored only if you add it to a charging log entry. If you also turn on charge observations (explicit consent), then when your battery rises next to a station your location is read once to find that station (within 300 m) and is not stored; we store the station, the day (not the time), the battery points gained, the minutes and the average power. Other drivers see only a summary built from at least two accounts, with no names or dates. Observations are kept for 90 days and are all deleted if you withdraw consent.
3.3 Chat and social features
- Your community and group messages, your direct and group-direct messages, the photos, voice messages and PDF files you send, your reactions, pinned messages and the messages you star (only you see your stars). If you edit a message (possible for 15 minutes after sending it), the new text replaces the old one and no earlier version is kept.
- Your stories (seen only by your friends, removed after 24 hours), the text and emoji you add to them, and who has viewed them.
- Your friends list, requests, blocked people, group memberships, invite links and chat preferences. A group admin can write a short label that appears in the member list; group admins can see who gave whom which role and who was removed from the group.
- A single "last active" time for online status and last seen, read receipts and the typing indicator. You choose in settings who sees these; information you turn off is hidden from you for others too. On your own messages you can see which members have read them, only while your read receipts are on and only for members who have theirs on.
- People you may know: this list shows people with whom you have at least two mutual friends; nothing else (contacts, location, check-ins or groups) creates a suggestion. It is worked out when you open the list and is not stored. A person you dismiss stays out of your suggestions for 90 days. With "Don't suggest me to others" you never appear in anyone's suggestions.
- Location data (EXIF) is removed from photos on your device before upload; if it cannot be removed, the upload is refused. Chat photos, voice messages and files are not public; only members of the chat can open them, through short-lived links.
- Reports and blocking are described in section 3.12.
3.4 Meeting other drivers
- Anonymous driver counts: if you share your location on the map, or tap "I'm charging" at a station, you may be counted in figures such as "10+ eBattery drivers in this area" or "3+ eBattery drivers here". The count stores only an area about 5 km wide (or the station) and a daily code; it never stores your account, and the day's code can no longer be linked to anyone about an hour after the day ends. Counts appear only in rounded steps and only from a minimum (10 for an area, 3 for a station). A contribution is deleted after about 35 minutes. You can turn off "Add me to area counts" in the settings.
- Station check-in and station chat (explicit consent): if you turn this on and declare that you are over 18, you can check in at the station where you are charging; your location is compared once with the station (within 300 m) and is not stored. A check-in lasts at most 60 minutes. If you choose "Open to chat", people checked in at the same station who made the same choice see your username, name and photo and, unless your profile hides them, your car and level, and you can wave to each other; a wave that is returned opens a direct message. Your posts in a station's chat are visible to signed-in users who have declared they are over 18 (not to people you have blocked or who blocked you) and are deleted after 7 days; if you withdraw consent, your posts are deleted at once.
- Community events: the events you host or answer in a community: the place (always a station or a public place from our own data), your answer (for example going or maybe) and, if you enter the code shown at the event, your attendance. Only members of the group see an event; only the host and people who answered "going" or "maybe" see who is coming; only the host sees who attended. An event and its chat are deleted 180 days after it ends or is cancelled.
- Help network (explicit consent): if you ask for help, your request (its kind, your note and, for help at a charging site, the station) reaches at most 10 remote or 3 nearby helpers who have opted in. Until you accept an offer they see only the area (about 5 km wide), never your name or your exact location; your location is compared once with the station (within 300 m) and is not stored. If you offer help, your position is kept as an area about 5 km wide for at most 2 hours. Requests are kept for 30 days and reports about them for 180 days.
3.5 Station contributions
- Reviews and review photos: public, shown with your name, profile photo and car model.
- Price observations: the live price of a station you open is kept with your account for 24 hours. If observations from two separate accounts agree, the price is published for 7 days without any account information.
- Status reports: kept with your account for 24 hours; other users do not see who reported. From them we keep, without any account, a daily count per station for 60 days, and a day is shown only when at least two drivers reported on it.
- Prices from your charging log: if you log a charge at a Şarj@TR station in Turkey with the amount and kWh, and state that no membership or subscription discount applied, the price per kWh may be shown on that station's page without your identity, but only when at least two accounts agree within 5 % and the station has no verified price. It is worked out from the logs each time it is shown and stops counting as soon as you edit or delete the entry.
- Wrong-information reports: when you use "Report wrong info", we store what you reported (for example the location or the price) and an optional note of up to 280 characters, and eBattery reviews it. The note is removed when the report is resolved; the report is kept for 180 days after that, or 365 days if it is never reviewed. When eBattery accepts a report, the station's name and country, what was wrong and the date of the decision may be listed on our public Data fixes page; never who reported it or the note.
- "Notify me when free": the station and an end time you choose (at most 3 hours). When the station frees up we send one notification and delete the request; the notification is kept for 7 days.
3.6 Cars, charging log, plans and trips
- The cars in your garage; for a car not in the catalogue, the make, model, battery and range you type.
- Your charging log: the day (not the time), the station you picked or a type of place (home, work, other), kWh, the amount you paid and its currency; optionally the battery percentage, the car and the odometer. Only you can see your entries (for the one exception, a price shown without your identity, see 3.5).
- Your saved route and trip plans, favourites, recently used stations, station search picks and notification preferences.
- Trips ("My trips"): each trip you plan: its title and status; the start, destination, dates, interests, car, battery percentage and road preferences; the planned days and stops (place names, coordinates and districts); the places you pin or mark as visited; and, if you enter one, where you stay overnight, which can be a home or hotel address. If a trip starts from "My location", that is your approximate location at the time of planning. Up to 50 trips, kept until you delete them or your account.
- Texts and photos of places: they come from Wikipedia and Wikimedia Commons. Our server sends Wikimedia only a place's name and coordinates; your phone loads the photos directly from Wikimedia, which sees your device's IP address when it does.
- Kept only on your device: the "Charge timer" and its reminders, a reminder you set after a bill check, and the bank-card programmes you tick in "My cards" (programme names only, never a card number). These never reach our servers.
3.7 eBattery AI assistant
- We inform you and ask for your agreement on first use. Your messages are sent to Anthropic's Claude service (USA) together with your location rounded to about 1 km, distances to nearby stations rounded to 100 m, the car in your garage and your open route plan, so that the assistant can answer; the exact position is used only on our server, to find stations and weather. Under the terms of the service we use, Anthropic does not keep your messages and the replies once the reply is given and does not use them to train its models; if its automated safety systems flag a conversation, it may keep that conversation for up to 2 years.
- Trip guide (Premium): after the same agreement, when you ask for an AI description of a trip, its day plan, the names, types and districts of its places with their Wikipedia texts, the overnight place you entered and your app language are sent to the same provider. Your account, location and coordinates are not sent, and the text is not stored by us.
- Your chat history is kept only on your device; it is deleted when you sign out or switch accounts.
- On our server we keep only usage information (model and token counts, not message content) for cost and abuse limits, for 730 days.
- When you ask by voice, your speech is converted to text by your phone's speech-recognition service; we receive only the text. When you listen to a reply, the text goes to your phone's text-to-speech service (Google's engine on Android, Apple's on iOS), which may process it on its own servers if no voice is downloaded on the device.
3.8 Game Area
- Your point transactions, quests, streak and chest records, Reward Wheel spins and what you won, in-game trips, season scores, the friends you add to your Trust Circle and your invitation relationships (whom you invited and who invited you). The name and photo of people who used your invite code are visible to you.
- Your 18+ declaration (not your date of birth), the time you accepted the game terms, and your game permissions, with a record of which permission you turned on or off under which version of the text.
- Which eBattery social-media accounts you follow (so that the same reward is not paid twice), the times you opened quest links (40 days), and your device's time-zone name, so that your game day starts at your own midnight.
- A quality score calculated automatically every night from your contributions (such as review likes and variety of contributions) and a reliability score to prevent abuse. They affect only game rewards and use no device or IP information. You can see your own score in the app.
- The cities in game trips are fictional; they are not your real location.
3.9 Notifications
Your in-app notifications and, if you allow them, your phone's notification token (with language and time zone). Notifications are delivered through Expo and your phone's notification service (Google Firebase Cloud Messaging on Android, Apple Push Notification Service on iOS); these services see the notification's title and text. When the app asks for notification permission, we count how the request ended (allowed, declined, “Not now” or off in Settings), with the day, the phone platform and the screen it was asked from. The count holds no account or device identifier.
3.10 eBattery Premium subscription
Payment is taken by the App Store or Google Play; we never see your card details. We use RevenueCat to verify your subscription. RevenueCat receives a random identifier we generate for you, your device type and operating system, your IP address and purchase information (product, period, store receipt); it does not receive your account identifier. We store your subscription's expiry date.
3.11 Technical and security data
- Crash reports: when the app crashes or hits an unexpected error, a technical report is sent to Sentry (Frankfurt, Germany). The only identifier in it is your account ID; no e-mail or phone number.
- Abuse limits: request counters keyed by IP address or account ID, kept for 1 day.
- Premium monthly allowance counters: how many of each allowance you used each month, tied to your account ID (numbers only, no content), kept to apply the subscription's terms and deleted after 3 months.
- SMS send log: kept for 30 days for fraud prevention when you sign in by phone.
- Moderation records: kept for 24 months with a digest (hash) of the content, not the message itself.
- Route-planner accuracy samples: derived from the charge percentage you give under "My charge now" and stored without account, location or time-of-day information, to improve the planner.
- Rating prompt: counters such as how many days you have used the app are kept on your device only.
- eBattery story views: how many times each eBattery story slide is viewed is counted per day without any identity; which slides you have already seen is kept on your device only.
- Live station data (Turkey): your phone fetches a station's live details directly from EPDK's Şarj@TR service; EPDK sees your device's IP address when it does. The socket counts your phone reads are shared with other users for 3 minutes without any identity.
3.12 Reports, blocking and suspensions
- You can report a message, a station review, a story, a profile, a station-chat post, an event or a help request, and you can block any user. Someone you block can no longer message you, see your stories or your profile details, or see you on the map. A report stores who reported what, the reason and an optional note of up to 300 characters. The person you report is never told who reported them.
- eBattery reviews reports within 24 hours. To decide, an eBattery administrator can see the reported content, including a photo in a story or a chat that would otherwise be visible only to its audience. Each decision records which administrator made it and when.
- When a report is decided, the person who made it is told whether we took action. If we remove content, its owner gets a notification saying what was removed, that it broke the Terms of Use and how to contest the decision. If we suspend an account, the app shows its owner the reason and the end date. A decision can be contested at contact@ebattery.app.
- A suspension stores its end date (or that it has none), its reason and who decided it. While an account is suspended it cannot use the social features or change its public profile.
- A decided report is deleted at the latest 180 days after the decision (an undecided one 365 days after it was made), and an ended suspension 180 days after it ends, so that a decision can be contested and repeated breaches recognised; reports about events, help requests and station-chat posts follow the periods given above. Separately, moderation records keep only a digest (hash) of the content, for 24 months.
3.13 Web community (forum)
- What you post: the topics, replies, helpful votes, saves, follows and reports you make in the community on ebattery.app. Topics and replies are published publicly with your display name and username; you can also add a car to your profile. You sign in with your app account by an e-mail code.
- Photos and images: the photos you add to your topics and the screenshots you add to a support request. Your browser re-encodes an image before uploading it and removes metadata such as location. Topic photos are public with the topic; request images are seen only by you and the community's administrators. The photo of a topic you delete is taken down.
- Notifications, follows and preferences: forum notifications for replies to your topic, your accepted answer, moderation decisions, questions routed to you and answers to your request (separate from the app's notifications); the people and car models you follow; your notification preferences, the people and brands you mute, and your interests. The car in your app garage appears on your forum profile only if you turn that on; the site reads your garage and never changes it.
- Drafts and appeals: the topic draft saved to your account; an appeal you make against hiding or rejecting a topic of yours, and the administrator's answer.
- Support requests: the request's type, title and description, your contact e-mail and screenshot if you give them, the administrator's answer and internal notes. If we decide to show a request on the roadmap, only a separately written public title and description are published, never your correspondence.
- Verified accounts: if we verify that you represent an organisation or have an expertise, the label shown and a note on how it was verified. The label is public; the note stays with the administrators.
- Downloading and deleting your data: "Download my data" gives your forum data as a JSON file. "Delete my community data" deletes your topics, replies, draft, appeals, follows, notifications, preferences, requests and images; your eBattery account and your app data stay. Traffic data and the reasons for moderation decisions are kept for their legal periods.
- Counters: the forum's daily read and search counts are kept without any identity, IP address or search text.
- Traffic data: as Turkish Law No. 5651 requires, every post you make in the forum records your IP address, the type of action, the content acted on, your account ID and the time.
4. Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Creating and running your account; providing the map, route, trip, chat, event, assistant, charging-log, game and subscription features and the alerts you ask for | Entering into and performing a contract (KVKK art. 5(2)(c); GDPR art. 6(1)(b)) |
| Location sharing with friends, appearing on the map and by name in communities, emergency alerts, station check-in and station chat, the help network, charge observations from your car; the Game Area's location, photo and invitation features | Explicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)). You can withdraw it in the app at any time. |
| Security; fraud and abuse prevention; reviewing reports, removing content and suspending accounts; crash reports; verifying price and status reports; anonymous driver counts and station status history; friend suggestions; station prices worked out from charging logs; handling wrong-information reports; improving the planner | Legitimate interests (KVKK art. 5(2)(f); GDPR art. 6(1)(f)) |
| Legal obligations; carrying out deletion requests; proving consent and deletion requests | Legal obligation and establishing a right (KVKK art. 5(2)(ç) and (e); GDPR art. 6(1)(c) and (f)) |
We make no decision that produces legal effects about you based solely on automated processing. The Game Area's quality and reliability scores are calculated automatically and affect only game rewards.
5. Who your data is shared with
We do not sell your data and do not share it for advertising. The service providers below process data on our behalf and only to provide the service:
| Provider | What for | Location |
|---|---|---|
| Supabase (infrastructure: Amazon Web Services) | Database, sign-in, file storage, real-time messaging, server functions | Germany (Frankfurt) |
| Google sign-in, maps, routing, elevation, place search and search along the route, station photos and live status, map images, navigation, Android notifications | USA and other countries | |
| Anthropic | The eBattery AI assistant and the trip guide | USA |
| Apple | Sign in with Apple (including removing eBattery from your Apple Account when you delete your account), iOS maps, iOS notifications | USA and other countries |
| Expo | Notification delivery | USA |
| RevenueCat | Subscription verification | USA |
| Sentry | Crash reports | Germany (Frankfurt) |
| Resend | Sign-in code e-mails and the e-mail confirming an account deletion | Ireland (sending); company in the USA |
| Twilio | SMS codes for phone sign-in | USA |
| OpenWeather | Weather (rounded location, no identity) | United Kingdom and other countries |
| Upstash | Cache (station status and weather; no account information) | Germany (Frankfurt) |
| Cloudflare | Serving the ebattery.app website | Global network |
Your phone also loads some content directly from other services, which see your device's IP address when it does: Google (station photos), EPDK's Şarj@TR service (live station details in Turkey) and the Wikimedia Foundation (photos of places in trips).
Beyond these: your profile, reviews, stories, messages, station-chat posts and events are visible to other users as described above and according to the visibility settings you choose. Where the law requires it, we may disclose data to competent public authorities or courts.
6. International transfers
Some of the providers above are outside Turkey and the European Economic Area, so your data is transferred abroad. These transfers rely on the appropriate safeguards of Article 9 of the KVKK and Chapter V of the GDPR, in particular the standard contracts in the providers' data processing agreements. You can ask which safeguard applies at privacy@ebattery.app.
7. Retention periods
| Data | Period |
|---|---|
| Account and profile, direct messages, reviews, garage, charging log, saved plans and trips, favourites, game records | Until you delete them or your account is deleted |
| Community and group chat messages | 180 days |
| Stories | 24 hours |
| Community location / emergency alert | 15 minutes / 10 minutes |
| Price observations, status reports, request counters | 24 hours |
| Station check-in / station chat posts / reports about them | At most 60 minutes / 7 days / 90 days |
| Anonymous driver count contributions (no account) | About 35 minutes |
| Station status daily counts (no account) | 60 days |
| Charge observations from your car | 90 days |
| Help requests / reports about them / a helper's area | 30 days / 180 days / 2 hours |
| Community events and their chats | 180 days after the event ends or is cancelled |
| Dismissed friend suggestions | 90 days |
| "Notify me when free" requests | Until the notification is sent or the time runs out (at most 3 hours) |
| Wrong-information reports | The note until the report is resolved; the report 180 days after that (365 days if never reviewed) |
| Reports about messages, reviews, profiles and stories | At most 180 days after the decision (365 days if never decided) |
| Account suspensions | While in force; an ended suspension 180 days after it ends |
| Notifications | Read ones 90 days; all at most 180 days; a "Notify me when free" notification 7 days |
| Group invite links | 30 days after they expire |
| SMS send log | 30 days |
| Quest-link open times | 40 days |
| AI usage information (not content) | 730 days |
| Premium monthly allowance counters (numbers only) | 3 months |
| Moderation records (not content) | 24 months |
| Game Energy Point balance | Reset after 12 months of inactivity |
| Accounts never used | An account unused for 24 months is deleted automatically |
| App language stored with a deletion request | Until the deletion completes or the request is cancelled |
| Your address for the deletion confirmation e-mail | Until the e-mail is sent; at most 7 days after the deletion |
| Sign in with Apple token (encrypted) | While your account exists; after the deletion until Apple confirms its revocation, at most 30 days |
| Forum topics and replies | Until you delete them or your account is deleted |
| Forum images | Until you delete your community data or your account is deleted |
| Forum notifications | The newest 500 per person; until your community data or your account is deleted |
| Forum follows, preferences, draft, requests and appeals | Until you change or delete them or your account is deleted |
| Forum verification records | Until the verification is removed or the account is deleted |
| Forum traffic data (Law 5651) | 2 years; kept for that period even after an account is deleted, because the law requires it |
A deletion you schedule becomes permanent after a 30-day waiting period; if you choose "Delete now" where the app offers it, the deletion is carried out at once, or within 24 hours at the latest. What is deleted and what remains afterwards is described on the Delete Your Account page.
8. Your rights
Under Article 11 of the KVKK and, if you are in the European Union, the GDPR, you can ask:
- whether your data is processed and, if so, for information about it and a copy;
- for the purpose of processing and whether data is used accordingly, and to whom it is transferred in Turkey or abroad;
- for incomplete or inaccurate data to be corrected, for data to be erased or destroyed, and for this to be notified to the parties it was transferred to;
- for processing to be restricted and to receive the data you provided in a portable format (GDPR);
- to object to processing based on legitimate interests and to an outcome against you resulting solely from automated processing;
- to withdraw your explicit consent (withdrawal does not affect the lawfulness of earlier processing);
- for compensation if you suffer damage from unlawful processing.
Send your request from the e-mail address registered to your account to privacy@ebattery.app. We resolve it free of charge within 30 days at the latest. If you are not satisfied with our answer, you can apply to Turkey's Personal Data Protection Board or, if you are in the European Union, to the data protection authority of the country where you live.
You can exercise many of your rights directly in the app: edit your profile; delete your messages, reviews, log entries and plans; change your location permissions and visibility settings; and delete your account.
9. Age limit
eBattery is for people aged 16 and over. The Game Area's reward features are open only to those who declare that they are over 18. If we learn that we are processing data of someone under 16, we delete the account.
10. Security
Connections are encrypted (TLS). In the database, every table is protected by rules that let users reach only the data they are authorised to access. Provider keys are kept on the server only. No system is completely secure; if a data breach occurs, we notify the competent authority and the people affected within the legal deadlines.
11. Website
ebattery.app is served through Cloudflare, which processes every request (including the IP address) for security and operation. The site contains no analytics tools and sets no cookie for tracking or advertising. It sets cookies only when you sign in to the community: eb_at (your sign-in token; valid for one hour and renewed while you use the community) and eb_rt (keeps you signed in; valid for 30 days, counted again each time the token is renewed); with Google or Apple sign-in also eb_pkce (completes that sign-in; 10 minutes, deleted when the sign-in returns). All three are set by ebattery.app itself, can be read only by our server (HttpOnly), are sent only over HTTPS and are deleted when you sign out. Cloudflare may add its own security cookie (for example __cf_bm) when its bot protection is in use. Your browser also keeps, on your device only: the colour theme you choose for the site and for the community page, which community campaigns you have already seen, a topic draft you are writing (while you are signed in it is also saved to your account), the articles you save to read later, a note that the home page's opening animation has played during the current visit, and, on the map page, the map settings described below. The site loads its fonts from Google Fonts and, on some pages, a graphics library from Cloudflare's cdnjs service; your IP address reaches these providers when it does.
Charging station map (ebattery.app/map): the base map is loaded from OpenFreeMap's servers (tiles.openfreemap.org); OpenFreeMap's operator and the network that delivers its files receive your IP address, your browser's user agent and the area of the map on your screen. The stations shown on the map are requested from our own server on Cloudflare; these requests carry your IP address like any request to the site, and they reach our database without it. Your location is used only if you tap "My location": your browser reads it once and shows it on the map, and it is never sent to us or to anyone else; the area then on screen is requested like any other. Your browser keeps the map's last view (its centre, rounded to about 100 m, and the zoom) and the power types you chose, under the localStorage keys eb-map-view and eb-map-classes; they are not sent anywhere. The map's position also appears in the page address after the "#" sign: it is not sent to a server, but it goes with the address if you share it. "Directions" opens Google Maps with the station's location, only when you tap it.
12. Changes
When we update this policy we change its effective date. We also announce important changes in the app.
