Privacy Policy

Amp: Tesla Costs & Mileage Log (“Amp”, “we”, “our”) is an app from TIT, based in the Netherlands, that shows your car’s live status, lets you control it remotely, and keeps a history of your drives and charging sessions. To do that, our server receives data from your car through Tesla’s official Fleet API. This policy is for Amp on Android and explains exactly what that data is and what we do with it.

Amp is an independent app. It is not made, endorsed or supported by Tesla, Inc.

You sign in on Tesla’s own login page, which Amp opens in your browser; we never see your Tesla password. Tesla then gives our server access tokens for the permissions you approve: vehicle information, vehicle location, vehicle commands and charging management. We do not request access to your Tesla profile, so we do not receive your name, email address or phone number. Your Tesla account is identified to us only by an opaque account ID.

• Tesla account ID and access tokens. Used to call Tesla’s Fleet API on your behalf and to keep you signed in.
• Vehicle telemetry. While your car is awake it streams data to our server: battery level and range, charging state and power, climate and cabin temperatures, lock, door and window state, Sentry Mode state, tyre pressures, gear, speed, odometer, software version and precise location.
• History derived from telemetry. Drives (start and end place and time, distance, energy use and the route as GPS points), charging sessions (place, energy added, power, cost from the prices you enter), and battery health over time.
• Vehicle details. VIN, factory options, vehicle configuration and warranty dates, fetched from Tesla to show on the Vehicle Info screen.
• Fast-charging bills. For fast charging billed to the car’s Tesla account, the session from Tesla’s charging history: the amount billed, any idle fee, the currency, the site’s name and a reference to the invoice. An invoice is fetched from Tesla when you open it; we don’t store it on our server. Amp keeps the invoices you open on your phone, so that they open again without asking Tesla, until you sign out.
• Things you enter. Home location and saved places, electricity prices and price area, smart-charging and climate schedules, automations, notification preferences, trip rules, business/private tags and notes on drives, trips you add by hand (with their addresses), who drove a drive, expenses, a licence plate if you add one, and the optional display name described under Shared Cars.
• Data you import. Drives and charging sessions from a CSV file you choose. We keep the rows as history and discard the file itself.
• API tokens and webhooks. Personal API tokens you create (we store only a hash of each) and, if you set one up, your webhook address and its signing secret.
• Push token. Your phone’s Firebase Cloud Messaging (FCM) token, used only to send the alerts you enable and to update the charging notification. Amp asks for one only when you’re signed in and notifications are allowed, never in guest mode.
• Crash and performance reports. Android records why Amp stopped running (ApplicationExitInfo, built into Android 11 and later): crashes, freezes where Android reports that the app isn’t responding (with the part of the code that was stuck), failed starts, and Android stopping Amp for using too much memory or other resources, with how much memory it was using. When Amp crashes, the app itself writes down the type of error and the code that was running, without the error’s message. Amp also counts, per screen and per day, how many frames it drew and how many came too late, with JankStats (part of Android Jetpack; it runs on your phone and sends nothing itself). Unless you turn off “Share Crash Reports” in Amp → Settings, the app sends these reports to our diagnostics server at diag.titdev.nl, with the app version and build, the Android version and the phone’s make and model, so that we can find out where Amp crashes or is slow. A report contains no name, account, car data or location. We don’t store IP addresses, and delete reports after 90 days.
• Feedback you send. When you’re signed in, Amp → Settings → Send Feedback sends your message to our server (the one that holds your Amp account), with an email address if you add one for our reply, and technical details: the app and Android version, the phone model, the app’s language and your phone’s language and region setting, time zone and unit setting, whether notifications are allowed, the selected car’s VIN and how far its setup has got, the last few requests to our server that failed (the address and the error, not their content), and the identifiers of your recent crash reports, so that we can find them. Our server adds what it already knows about your account: your cars and their setup and streaming state, your Tesla region and the permissions you approved, and whether Amp Pro is active. When your feedback arrives, we get a notification on our own devices with the first part of your message (up to 180 characters), delivered through Apple’s or Google’s push notification service. “Email Instead”, under Send Feedback, opens an email to info@titdev.nl in your email app with your message and the same technical details in it, for example to attach screenshots or to get our reply by email. In guest mode, email is the only way, and it leaves out the car, its setup status and the failed requests. Nothing is emailed unless you send that email yourself; if you do, we receive your email address and what you wrote.

Car names you set in Amp, and addresses shown for places, are handled on your phone. To show an address, or to find one you search for, Android’s geocoder may send the coordinates or the search text to Google. Amp doesn’t ask for your phone’s location: the positions it shows are your car’s.

The home-screen widget, the Quick Settings tiles and the launcher shortcuts use the account you’re signed in with. While the widget is on your home screen, it asks our server for your car’s status about every 30 minutes and keeps the latest status on your phone; their buttons send commands to your car the same way the app does.

If Android backup is on, Android can copy Amp’s settings on your phone (such as the car names you set, the app’s language and appearance, and the name and reference you use for reimbursement reports) and the invoices Amp keeps to your Google account, under Google’s privacy policy. Your sign-in, the push token, crash and performance reports and the widget’s car status are left out of backups and of transfers to a new phone; on a new phone, you sign in again. You can turn backup off in your phone’s settings.

• To show your car’s status and send the commands you choose.
• To build your drive, charging and battery history and statistics.
• To send the notifications and run the automations you set up, including smart charging.
• To fetch the weather forecasts and electricity prices those automations and your cost figures need.
• To show the live location links and battery reports you publish.
• To know whether your account, or a car you share, has Amp Pro.
• To keep the service secure and working, including backups.
• To answer your feedback and to find and fix crashes, slow screens and other problems.

The legal basis is the performance of our agreement with you (GDPR art. 6(1)(b)) and, for security, backups, crash and performance reports and the technical details sent with feedback, our legitimate interest in running a reliable service (art. 6(1)(f)).

• We don’t receive your name, email address, phone number or Tesla password, unless you add your email address to feedback you send or email us yourself. The only name we store is the display name you can choose to show to a shared car’s other users.
• We don’t use analytics, advertising or tracking SDKs. The third-party SDKs in the app are RevenueCat’s, used solely to process Amp Pro purchases through Google Play, and Google’s Firebase Cloud Messaging and Maps SDK, used only to deliver notifications and to show maps. Firebase Analytics is switched off, and RevenueCat’s SDK does not track you across apps or websites.
• We don’t see or store your payment details.
• We don’t sell your data or share it for advertising.
• We don’t wake your car to collect data. It is only woken when you ask, or when something you set up runs: a climate schedule, a smart-charging window, or closing the windows before rain.

A Tesla can be shared between an owner and drivers. Anyone who signs in to Amp with a Tesla account that has access to the car can see that car’s status, history and shared car settings in Amp. Notification preferences stay personal.

If you set a display name, the car’s other users see it next to the drives assigned to you, in a drive’s change history and in the cost split. If another user of the car sets up a webhook, the car’s alerts and its drive and charging summaries, including start and end locations, are also sent to the address they chose.

A live location link shows anyone who has it the car’s current position, its speed while driving, the battery level, and the destination and arrival time while navigating, with the name you give the link — until it expires (after 24 hours at most) or you stop it. The page loads its map from OpenStreetMap, which sees the viewer’s IP address and the map area.

A published battery report shows anyone who has its link the car’s VIN, model, odometer, battery and charging figures and battery warranty, for a year or until you unpublish it — also after you sell the car.

• Tesla. Supplies the vehicle data and carries out commands through the Fleet API. Tesla’s privacy notice.
• Hostinger. Hosts our server in Frankfurt, Germany.
• Cloudflare. Provides DNS and stores our database backups, encrypted at rest, in its European region. It also runs our diagnostics server, diag.titdev.nl, which stores crash and performance reports in Cloudflare’s D1 database. Cloudflare’s privacy policy.
• RevenueCat, Inc. (United States). Processes Amp Pro purchases for us: it receives your subscription status and purchase history from Google Play (and from the App Store, if you subscribed on an iPhone), linked only to the random billing ID of your Amp account, and tells our server whether your subscription is active. Transfers to RevenueCat are covered by the European Commission’s Standard Contractual Clauses. RevenueCat’s privacy policy.
• Google. Handles all payments for Amp Pro through Google Play, and keeps your phone’s backup in your Google account if Android backup is on. Google’s privacy policy.
• Firebase Cloud Messaging (Google). Delivers the alerts and the charging notification’s updates to your phone. Google receives your phone’s FCM token and a Firebase installation ID, and passes on each message: the alert’s text, the car’s VIN and, for the charging notification, the car’s name and its charging figures (battery level, charge limit, power, time to full). Firebase Analytics is switched off. Firebase’s privacy information.
• Google Maps (Google). The maps in Amp come from the Google Maps SDK for Android. Google receives the map areas shown (around your car, a drive’s route or a charging location), and usage and diagnostic information about the map with a pseudonymous identifier, which it uses to provide and improve its maps. Android’s geocoder, which Amp uses for addresses, may send coordinates or search text to Google. Google’s privacy policy.
• MET Norway (the Norwegian Meteorological Institute). Receives the car’s position rounded to about 1 km, and nothing else, to return the weather forecast we use for rain warnings when a window is open and to start climate schedules early on frosty mornings.
• RDW (the Dutch vehicle authority). If you add a licence plate, we look it up in the RDW’s open data to show the car’s registration and APK (MOT) expiry date, and check it again weekly. Only the plate is sent.

Electricity prices come from ENTSO-E and, for UK regions, from Octopus Energy’s public Agile Octopus rates; exchange rates come from the European Central Bank. Those requests contain no personal data: a request to Octopus Energy names only the region and the time period, and Amp never connects to your Octopus Energy account. If you set up a webhook, we send your car’s events to the address you chose; what happens to them there is up to you.

Your vehicle data is stored and processed in the European Union, wherever you use Amp. If you live outside the EU, using Amp means your data is transferred to the EU, where the GDPR protects it. Subscription status and purchase history (only, never vehicle data) are also processed by RevenueCat in the United States, and Google, which may process data outside the EU, delivers the notifications, maps and address lookups described above.

• Raw telemetry is deleted after 30 days.
• Drive, charging and battery history is kept for as long as you use Amp, so you can look back on it.
• Delete your account any time in Settings → Account → Delete Account. This immediately removes your account and display name, your Tesla tokens, push tokens and API tokens, your webhook, live location links and published battery reports. For cars no one else uses in Amp, it also removes all their history and stops the car streaming data to us. On cars others still use, drives, changes and expenses you added stay with the car but are no longer linked to you.
• Removing a licence plate deletes it and its RDW data. Unpublish a battery report or stop a live location link at any time in the app.
• Subscription status and purchase history are kept while you subscribe, and afterwards only as long as required for tax and accounting purposes. Deleting your account removes the subscription record and billing ID from our server; a Google Play subscription itself is not cancelled by this, cancel it with Settings → Manage Subscription or in the Play Store → Payments & subscriptions.
• Crash and performance reports are deleted from our diagnostics server after 90 days; on your phone, Amp keeps them for up to 30 days. Turning off “Share Crash Reports” stops new reports from being sent and withdraws those not yet sent.
• Feedback sent from Amp to our server is kept until you delete your account; deleting your account deletes it too. Feedback you email us stays in our mailbox at Zoho, our email provider, not on Amp’s server, so deleting your account doesn’t remove it; ask us and we’ll delete it.
• Our backups roll over: deleted data disappears from them within 60 days. Your phone’s backup in your Google account is managed in your Google account settings.

You can also revoke Amp’s access at any time in your Tesla account settings under third-party apps.

Under the GDPR you can ask to access, correct, export or delete your data, and you can object to or restrict how we process it. Email us and we’ll respond within one month. You can also lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens). You can turn off “Share Crash Reports” in Amp → Settings at any time.

Amp is not directed at children under 16. We do not knowingly collect data from children.

We may update this policy. Changes are reflected in the “Last updated” date above, and we’ll tell you in the app about material changes.