Privacy Policy

What we collect

Nothing beyond what the purposes below require.

• Account: your email address, the language and theme you chose, and the country inferred from the preferences your browser declares.
• Identity provider identifier, if you sign in with Google or Tesla.
• Your grid: section names, bookmark titles and addresses.
• Paired vehicles: the name you give them, the model and trim, and the date of last activity.
• Tesla account, if you link one: an encrypted access token and your account's region.
• Data your vehicle sends, if it is transmitting: charge level and limit, range, odometer, door, lock and Sentry Mode state, the pressure of all four tyres, inside and outside temperature, climate state, distance driven on Full Self-Driving, software version, and whether the vehicle is at its home or work location — two indications the car gives without ever sending us the matching address.
• The destination set in the vehicle, if there is one: its name, its coordinates and the time remaining. Only the CURRENT destination is kept; no history of it is retained, and it stops being displayed after six hours without a refresh.
• Charging sessions: date, duration, start and end levels, energy delivered, charger used and cost. Cost is estimated from the rates you enter, or read from your Tesla billing if you allow us to read it.
• The charge limits you set for home and for work.
• Television channels you favourite, and your electricity rates if you enter them.
• Trips, only if you turn recording on: precise timestamped positions and distances travelled.
• Assistance, if you fill it in: your insurer's name, its assistance number, your policy number and the vehicle's warranty end date. This is only used to show it back to you on the car screen; it is shared with no one.

What the vehicle sends us, and what we send it

Two distinct exchanges, with different reach and different permissions.

• The vehicle PUSHES its data to our servers, continuously, over an encrypted link Tesla establishes at your request when you turn the feature on. We ask for nothing: the car transmits, and only the information listed above.
• iCar can also SEND two commands to your vehicle, and only two: a destination to its navigation, when you tap “Take me there”; and the charge limit, when you have set one for the place you plug in. Nothing else is ever sent.
• Those commands require a permission Tesla does not split up: the one it asks you for also covers the doors, the trunk and Sentry Mode. iCar does not use it for those, and will not without telling you. You can withdraw it at any time from your settings, or from your Tesla account under “Third-Party Apps”.

What we do not collect

Weather and map tiles are requested directly by the vehicle's browser, without passing through us: we see nothing of them.

Your vehicle's identification number is never kept in the clear: we keep only a fingerprint of it, enough to recognise the car but not to recover the number.

Your home address and your work address are never sent to us. The car says it is there; it does not say where that is.

Where you plug in is not retained: we keep only the identifier of the charger recognised, never its coordinates.

To announce points of interest along your route, and to work out which chargers you can still reach, the vehicle sends its position to our servers. It is used to answer the request and then forgotten: it is neither recorded nor retained.

Trip recording is the only feature that keeps positions, and it only starts with your agreement.

No position is ever written to our logs, under any circumstance.

Why, and on what basis

• Providing the service — your account, your grid, its sync to the vehicle: performance of our contract.
• Recording your trips: your consent, which you may withdraw at any time from your settings. Withdrawal stops recording without erasing the history already collected.
• Receiving your vehicle's data and sending it a destination or a charge limit: your consent, given to Tesla when you sign in, and withdrawable on either side.
• Keeping the service secure and preventing abuse: our legitimate interest.

Who else has access

We sell no data and pass none on for advertising purposes.

• OVH (France) hosts the service and its backups.
• Brevo (France) sends sign-in emails.
• Google and Tesla, if you choose to sign in through them or to link your vehicle. These exchanges leave the European Union.

What our servers ask third parties

These services are queried by our servers, at your request and in order to answer it. They therefore see our address and not your vehicle's, and nothing is sent to them until you ask for it.

• France's IGN Géoplateforme and Photon (Komoot), when you search for a destination from the vehicle's map. They receive the text you typed and the vehicle's position, which is used to rank results around you. Neither is retained.
• Photon (Komoot) also when you open the assistance screen, to name the nearest town. It then receives the vehicle's position and nothing else. It is not retained.

What the vehicle contacts directly

Some features are requested by the vehicle's own browser, without passing through our servers. Those services therefore see the vehicle's IP address and what it asks for. We receive nothing from these exchanges, but you should know they happen.

• Open-Meteo, for the weather where you are driving.
• OpenStreetMap, for map tiles.
• Wikimedia, for photographs of the points of interest announced.
• Waze, if your grid holds its shortcut and you open it. The address opened then tells Waze the vehicle's position and, if one is set, its destination — which is what saves you from entering them again. Nothing is opened unless you tap the tile.

Who processes data on our behalf

These providers act on our instructions and for the purposes described here only.

• Stripe Payments Europe, Ltd., for subscriptions and billing. Your card details are entered on Stripe's pages: they never pass through our servers and we store none of them. All we know about your payment is its status and its renewal date.
• Brevo, for sending sign-in links.
• OVH SAS, which hosts the service in France.
• Google and Tesla, if you choose to sign in or link your vehicle through them.

For how long

• Account, grid, vehicles and charging sessions: as long as the account exists.
• Recorded trips: as long as the account exists. We do not yet apply automatic erasure; you can ask for them to be deleted at any time, and it is immediate.
• Destination set in the vehicle: only the current one, cleared as soon as the vehicle stops reporting it, and never shown beyond six hours.
• Sign-in links and codes: one hour.
• Encrypted backups: thirty days on the server, ninety days on their off-site copy, after which rotation destroys them. Data deleted from your account may therefore survive in those backups until they are destroyed.

Your rights

You may request access to your data, its correction, erasure or portability, object to a processing operation, or withdraw a consent. Write to contact@geticar.com.

You may also lodge a complaint with your national data protection authority.

Security

Traffic is served over HTTPS. Tokens granting access to third-party services are encrypted at rest and unreadable without a key held separately. Backups are encrypted before being written to disk.