TakenLee › Privacy Policy

Privacy Policy — TakenLee

Last updated: 9 October 2026

TakenLee (in Hebrew: תקן-לי) reads diagnostic data from your car's computer through an OBD-II adapter, shows public vehicle information from the Israeli Ministry of Transport's registries, and lets you share your car with the garage you choose and with other drivers. This page explains what is collected, why, who it is shared with, and how to delete it.

In short: we collect your phone number, your vehicle's details and its diagnostic data. It is shared with the garage you choose to link to and with drivers you choose to share with — and with no one else. We do not sell data, do not use it for advertising, and the app contains no analytics, advertising or tracking SDKs. The one-time purchase is paid through Apple or Google, and your payment details never reach us.

1. Who is responsible

KesTech, the operator of TakenLee. For any privacy question, request or complaint: y28112000@gmail.com.

2. What we collect

Phone number — this is your account. Sign-in uses a one-time SMS code; we store no password for drivers.
Display name, if you entered one.
Licence plate number, and the public vehicle details it resolves to: make, model, year, fuel type, colour, VIN and roadworthiness-test expiry date. These come from the Israeli Ministry of Transport's open vehicle registry.
Vehicle diagnostic data — trouble codes (DTCs) and when they were read, a freeze-frame snapshot of the engine at the moment a fault set (RPM, speed and coolant temperature as the car's own computer stored them — so your garage can see the conditions the fault occurred under), odometer readings, trip summaries (start and end time, distance, average and maximum speed, estimated fuel use, and the count of harsh accelerations and braking events behind the eco-driving score), and acceleration measurements you choose to run. The live readings shown while you drive (RPM, speed, temperatures and so on) stay on the phone: only the summaries described here are sent.
Per-drive health vitals — at the end of each drive we store a summary of measurements that mean nothing individually and a great deal as a series: cranking, resting and charging voltage, air temperature at start-up, peak coolant temperature and whether the engine reached operating temperature, short- and long-term fuel trims, whether the warning lamp is lit and how far you have driven with it lit, the state of the car's emissions self-tests, and the results of the tests the car's computer runs on parts such as the catalytic converter, the oxygen sensors and the evaporative system, with the limits it sets for them. A battery going flat or a fuel trim drifting shows up in that series weeks before any lamp comes on.
Safety recalls — once a day we check the Ministry of Transport's recall register for an open recall on your vehicle, and keep the result on your account so we can alert you and show it to your garage.
Pre-purchase inspection reports — if you run a deep inspection on a car, the report is backed up on your account so it survives a change of phone. It holds the VIN the inspected car reported, its licence plate if you typed one and what the Ministry of Transport has on record for it, the odometer it reported, the warning lamp and self-test status, its fault codes, which systems answered the scan and what they reported, and the time. The car inspected is usually someone else's (the seller's); the report is kept on your account only and is deleted with it.
Appointment requests — when you ask your linked garage for an appointment, the reason and preferred time you wrote are stored and shown to the garage, together with its answer.
The adapter you connected — so the app can reconnect to it automatically, your phone remembers its identifier. It is kept on the phone only and is not sent to us.
Adapter compatibility, anonymously — on every connection to a car, and whenever you run an adapter check, the app sends a technical report on how the adapter and the car got on: the link type (classic Bluetooth or Bluetooth Low Energy), the name the adapter advertises and how it identifies itself, the car's communication protocol, which readings the car supports, whether the VIN could be read (not the VIN itself), the app version and the phone's platform; and for an adapter check, the speed and stability measured, which commands the adapter supports and which of the car's systems answered. Whenever you run an adapter check or a pre-purchase check, a copy of the report is sent too, as it appears on screen, with the car's raw replies. Before the copy leaves the phone, the licence plate, the raw replies that contain the VIN, and the last six characters of the VIN, which identify one car, are removed (the maker, model and year remain). Of the car, only make, model, year, fuel type and engine code are kept. The report is stored with no link to you or your car: no account, phone number, licence plate, VIN, or adapter Bluetooth address, and time only to the day. It tells us which adapters work well with which cars, and lets us fix support for a car before a driver runs into the problem.
Notification token — a Firebase Cloud Messaging token and your platform, so we can notify you about a fault or a due service. Notifications sent to you are also kept in the in-app notification centre, together with the notification preferences you chose.
Purchase state — if you bought the pre-purchase inspection unlock, a flag saying so is stored on your phone. Apple or Google process the payment; we do not receive your payment details and do not store them.
Conversations with Lee — if you use the in-app assistant, your questions and its answers are kept on your account so the conversation stays available to you. You can delete them at any time from the chat screen. If you report an answer, the reason you chose and any note you added are kept too, so we can review it.
Crash reports — if the app crashes, a technical report is sent to us through Firebase Crashlytics: device model, operating-system version, app version, where in the code it crashed, and your internal account id (not your phone number), so that a fault recurring for one user can be fixed. A connection to an adapter that fails unexpectedly is reported the same way, with the adapter's name, so we learn which adapters struggle to connect. The report contains no screen content and none of your conversations.
Service log — services you log yourself: what was done, when, at what mileage, the cost and notes you wrote, and photos of receipts you chose to attach (from the camera or the gallery, only the photo you picked). You and drivers you share the car with see them, and they are deleted with the car or the account. A "Checked by TakenLee" page shows only the service, the date, the mileage and whether there is a receipt: never the receipt, the cost or the notes.
Feedback — if you send us feedback from the app, we keep what you wrote, the kind of message, the app version, the phone's platform and operating-system version, and the adapter's name if one was connected. Sent from a signed-in account, it is tied to that account, and we contact you by phone only if you ticked that we may. Sent before signing in, it carries only the contact details you chose to leave.
Adapter waitlist: if you join it, we keep the phone number or email you left, which phone you use and when you joined. They are used only to tell you when the adapter is available and to hold the early price for you. They are deleted with your account, or when you ask by email.

3. What we do not collect

Location permission on Android 11 and below. On those versions the operating system requires it before any app may scan for Bluetooth devices, and it serves only to find the adapter.
Contacts, microphone, or photos and files on your device, other than a receipt photo you chose to attach to the service log. When you share a car with another driver, you type their phone number yourself — the app does not read your contacts.
Analytics, advertising or cross-app tracking. No such SDK is present in the app. The crash reports and adapter compatibility reports described above are technical only: they describe the app, the adapter and the car, not what you did in the app.
Payment details. Your card or billing account stays with Apple or Google.

4. How the data is used

To identify you at sign-in and keep your vehicle and its history.
To explain faults in plain language, with the context they were stored in.
To estimate mileage and remind you about services and test expiry.
To notify you when a new fault appears, a service falls due, or a recall is opened for your car, and to send a weekly summary — according to the preferences you chose, and never at night.
To compare your fuel consumption over time against what is normal for your car and alert you when it rises — a sustained increase often precedes a fault that has not yet lit a warning lamp. The comparison is against your own vehicle's history only, not against other cars or manufacturer figures. The cost in shekels is computed from the official fuel price published by the Ministry of Energy.
To show you where your fuel use stands among other drivers of the same model, on the same kind of drives. You see only your own rank, the median and the number of cars, and only when there are at least five other cars of the model. No other driver sees your data.
To publish reliability pages by model on the website (real fuel consumption and common faults), computed daily from the trips and fault codes of all cars, including the anonymous copies described in section 8. The pages hold only aggregates: a model is published only with at least five cars, every figure on a page rests on at least five cars, and a fault code appears only if at least three different cars reported it. They never contain a plate, VIN, name, dates or locations.
To warn you about a fault developing before it strands you — a battery weakening, fuel trims drifting, a stuck thermostat, overheating, or self-tests that were wiped and would fail a roadworthiness test.
To pass that same information to the garage you chose, so they can work on the car knowing what happened to it.
To fix crashes and faults in the app, and to read and answer feedback you send.

We make no automated decisions with legal effect for you, and build no marketing profile.

5. Who it is shared with

The garage you choose. Once you enter a garage code, that garage's staff can see your name, phone number, vehicle details, faults, trip summaries, health vitals, open recalls, service reminders and appointment requests. This is the purpose of the product and it stays under your control: you can unlink at any time from the app, and the garage stops seeing you from that moment. One garage never sees another garage's customers.
Drivers you share a car with. If you add another driver to a vehicle by their phone number, they see the vehicle in their own list — its details, faults, trips and health vitals — and receive its fault alerts. They also see your display name as the owner. Only the owner can share or unshare, at any time.
Anyone you give a "Checked by TakenLee" link. If you create such a link for a vehicle (say, for a sale ad), anyone holding it sees a page with the make, model, year, a rounded mileage, whether the VIN was verified, the current faults and those from the last two years, the services you marked done, open recalls and since when the car has been followed. The plate appears only if you chose to show it. The page never shows your name, your phone or the VIN, and is blocked to search engines. The link expires after 90 days, and you can revoke it or make a new one (which revokes the old) at any time from the app. Only the owner can create one.
Infrastructure providers acting solely on our behalf: Railway (server and database hosting), Google Firebase (SMS verification, push notifications and crash reporting), Sentry (server error reporting — the name of the operation that failed and the technical error details, never the content of your conversations), and Resend (email: the waitlist confirmation for anyone who joined with an email address, and feedback sent from the app, which is forwarded to us by email so we read it promptly).
Apple and Google — to process the one-time purchase, under the privacy policy of the store you bought through.
DeepSeek, our language-model provider — only if you use Lee, the in-app assistant. Your question and a snapshot of the vehicle are sent to its service to generate the answer. That snapshot is: make, model, year, fuel type, engine model, estimated mileage, roadworthiness-test expiry date, the open fault codes and when they were read, the services falling due, how your fuel consumption over the last fortnight compares with what is normal for this car, the active alerts already sent to you, and the name and phone number of the garage you are linked to. Your phone number, your name and your vehicle's licence plate are not sent. DeepSeek is a company headquartered in China, its servers operate outside Israel, and under its privacy policy content you send may be used to improve its service. For that reason: do not write personal details to Lee — it does not need them to answer questions about the car. If you never open Lee, nothing is sent to them.
The Ministry of Transport registries (data.gov.il) — the plate number is sent there to retrieve vehicle details, recalls and specifications. That request does not identify you. The same applies to the licence-plate check, in the app and on this website: the plates you look up are sent to the public registries, the answer is cached on our server for one hour for performance without any link to your account, and we keep no record of which cars you looked up. On the website, to limit the number of checks, your IP address is held in the server's memory for one hour only, without the plates you checked.

We do not sell, rent or transfer data to third parties for marketing. Data is disclosed to an authority only where the law requires it.

6. Where the data is stored

On our infrastructure providers' servers, which may be located outside Israel, including in the European Union and the United States. Transfers are encrypted (TLS) and governed by those providers' data-processing terms.

7. Security

All traffic between app and server is TLS-encrypted. Account access uses a signed token, and garage-account passwords are stored only as hashes. Access is scoped by role: a driver sees only their own vehicles and those shared with them, and a garage sees only the customers who linked themselves to it.

8. Retention

For as long as the account exists. Deleting the account permanently erases everything that identifies you or your car, including operational backups, within 30 days. Crash reports are retained by Firebase for up to 90 days. Feedback is deleted a year after it was sent.

What remains after deletion, anonymously. Before deleting, we keep a copy of the car's technical data to improve the app: make, model, trim, year, fuel type and engine code, mileage rounded to 5,000 km, fault codes and the engine conditions when they were stored, trip summaries and health vitals. The copy has no phone number, name, licence plate, VIN, colour, garage or dates: time is kept only as the number of days since that car's first record. Nothing in it links back to you, so it is not personal data. Feedback you sent stays until a year after it was sent, without the link to your account and without any contact details you left. You wrote the text yourself, so if it contains something that identifies you and you want it removed, email us. Adapter compatibility reports are anonymous from the start, so deleting the account does not touch them.

9. Your rights

You may review the data held about you, ask for it to be corrected, and delete it. Deletion is self-service: Settings → Delete account in the app, or via the account deletion page. A single car can be removed on the vehicles screen (⋮ → Remove from account), which deletes its trips, faults and reminders. When the Ministry of Transport shows that a car changed hands after you registered it, and someone else adds it, the plate moves to them: the car's history stays with you, without the plate and without reminders, and you are told. For anything else, email us and we will respond within 30 days.

These rights arise under Israel's Protection of Privacy Law, 5741-1981. If you are in the European Union, you also hold GDPR rights, including data portability and the right to complain to your national supervisory authority.

10. Children

The app is intended for licensed drivers and is not directed at children under 16. We do not knowingly collect data about children under that age.

11. Changes

If this policy changes, the date at the top is updated. A material change in how data is used will also be shown in the app before it takes effect.