Privacy Policy

1. Scope

This policy covers the T2Car mobile app on iOS and Android and this website. By installing the app or opening this page you are taken to have read it.

2. What we do NOT do

• No tracking code, no advertising identifier (IDFA), no tracking of you across other companies' apps or websites.
• No third-party analytics or advertising SDK. The app connects only to the T2Car service, and to Apple and Google to sign in or to buy. When you look up a VIN, the T2Car server sends the VIN string to a third-party data-processing partner that T2Car contracts with to look up the vehicle catalogue.
• No user profiling, no scoring, no ad targeting.
• We do not sell, rent or trade data with third parties. Data reaches other people only when you choose to send it, such as a quote request in section 9.
• The app does not ask for location, contacts, calendar or health data. When you pick a photo, the app receives only that photo; it does not read your whole photo library.

Messages sent through the website

When you send the contact, plan-advice or co-founder form, you give your name, email, subject, message and a profile if you attach one. T2Car keeps this in its own system so the team can receive, handle and answer the request. Form data is never shown publicly. To have what you sent corrected or deleted, write to [email protected] with the reference number you were given.

Website measurement and cookies

On the t2car.com website, and only with your permission, T2Car counts how the site is used (pages viewed, scroll depth, clicks on download buttons, language, page speed) and loads Google Analytics 4 under Google Consent Mode. Before you accept, only anonymous counts are kept and no identifier is stored in your browser. The app is not affected: it embeds no third-party analytics.

The list of cookies, their lifetimes and how to withdraw your consent are in the Cookie Policy.

3. Signing in with Apple or Google

The app offers Sign in with Apple and Google. The provider issues an identifier and may share your name and email address. The app sends the signed identity token, a verification nonce and the name you provide to the T2Car server, which checks the token against the provider's public keys before it creates an account session.

The server stores the provider identifier, your name and email if provided, your T2Car account ID and the link between the account and the device that signed in. On iOS the session is protected in the Keychain without iCloud sync; Android uses the device's secure store. We never receive or store your Apple ID or Google password. Each account has one active session: signing in on a new device signs the old one out. You can link both sign-in methods yourself; the system never merges accounts by email.

Apple shares a name only at the first authorisation. When an Apple account has no name or contact email yet, the app invites you to enter a display name (up to 60 characters) and a contact email; both are optional. The contact email is kept separately, so a later Apple sign-in does not overwrite it.

If you choose “Hide My Email”, Apple shares only a private relay address; T2Car does not learn your real email unless you enter it yourself as the contact email. The server encrypts the Apple authorisation token it needs to revoke access when the account is deleted.

4. Data kept on the device

The app keeps the information and drafts it needs to carry on your work:

• The account information in section 3, protected in the Keychain.
• Diagram bookmarks, viewing and search history. A bookmark is a reference; the app does not download the library for offline use.
• Job drafts, saved parts, pinned vehicles, notes and reading positions. While you are signed in, private data on the device is encrypted and kept per account. Bookmarks, notes, reading positions and submitted jobs sync with the server; search history, recently viewed items and unsent drafts stay on the device. Guest data is kept apart and never moves to an account on its own.
• A random installation ID and the queue of usage events not yet sent (at most 500, see section 6). The installation ID is removed with the app, so a reinstall counts as a new installation.
• App settings such as appearance, language, display options and onboarding state.

Removing the app deletes the data it stores on the device, including your garage (My car), which is kept only on the device. The account and the data synced to the server remain; deleting an account only closes it, as described on Delete your account and what happens to data.

5. Data sent to the server

When you open a diagram or look up a code, the app calls the catalogue server at api.t2car.com. The request carries what you are looking up — a part number, a fault code or a diagram reference — along with the app, device and session credentials needed to grant access, prevent abuse and stop requests from being replayed.

The server stores what you sync: job cards, vehicles, parts, bookmarks, notes, reading positions and feedback. On a workshop plan this includes roles, assignees and update history; members with the right role can see shared jobs. Personal feedback is visible only to you and the administrators who handle it.

Operational logs and security events may include IP address, time, path, status code, device ID and the detail needed to investigate faults or protect the service. They are never used for advertising or to sell user profiles. Daily access records with the IP address are kept for 30 days.

6. App usage statistics

The app records a few usage events and sends them in batches to the T2Car server at api.t2car.com. These are statistics T2Car keeps for itself; no third-party analytics SDK or service is involved.

• Each batch carries: a random installation ID the app creates on first launch, the platform (iOS), the app version, the iOS version, the device model code (for example iPhone15,2), and the device's language and region setting.
• Each event carries a random ID, the event name, the time and, where relevant, a screen name, a fixed label or a number.
• Events sent today: first launch, app open, session start and end (with its length), sign-in started (with the provider, Apple or Google), signed in, signed out, vehicle page opened and diagram opened.

For statistics, the server records an approximate country derived from the device's network connection (the IP address is not stored for this purpose), linked to the installation and the account.

Screen names and labels are fixed keywords set by the app; these events never contain what you type, the codes you look up or document content. Event batches are sent without your sign-in session, but the installation ID travels with every request to the server: once you sign in, the server links the installation ID to your account.

Purpose: running and improving the app — counting installs and active devices, finding faults and seeing which features are used. These statistics are not used for advertising or to track you across other apps or websites, and they are not sold.

The server stores the installation ID only as a SHA-256 hash. Events are deleted after 90 days; an installation record is deleted after 400 days without activity. Closing your account does not remove the link between the installation record and the account.

7. Device verification and service protection

The app creates a P-256 key for the device, held in the Secure Enclave on devices that have one. Your session is bound to that key and the server stores only the public key's thumbprint, so a leaked access token is useless on another device.

On iOS, supported app versions and servers may use Apple's App Attest to verify the app. It creates a key in the device's secure hardware and gives the server an attestation that requests come from a genuine T2Car build. The attestation carries no name or email and cannot be used to track you between apps.

Each request also carries a fixed list of device flags: simulator, release build running under a debugger, signs of a jailbreak, and device without App Attest support. To detect a jailbreak the app only checks whether a few system paths exist; it does not read other apps' data.

The server stores the device ID and these flags with your session, solely to authenticate, spot unusual access and protect the service. Depending on server settings, a device showing signs of a jailbreak or being debugged may be refused content; you can still sign out and delete your account. This information is never used for advertising and is not sold.

8. Camera and photos

The app asks for camera access so you can scan part numbers printed on a component or its box, DTC fault codes and vehicle identification numbers (VIN) instead of typing them.

Reading text while scanning, and when you pick an existing photo to read a code from it, happens entirely on the device: those images are not uploaded. A VIN or part number that was read is sent only when you use it for a lookup. A VIN lookup sends the VIN string through the server to the data-processing partner described in section 2; the original image is never sent there. You can refuse the permission, pick an existing photo or type as usual.

Identifying a part from a photo is different: it does upload the photo. When you are signed in and pick a photo on the Research screen, the app shrinks it on the device to at most 512 px on the long side, converts it to JPEG and sends it to the T2Car server with your session. The app says so just below the photo button, before you pick.

The server shrinks the image further to 256 px and passes it to an image-recognition model that T2Car runs on its own infrastructure; it is not sent to an outside AI service. The photo is processed in memory only, to return a short suggested part name; the server does not store the photo. The suggestion is filled into the search box for you to check before you use it.

9. Asking for part prices

In countries where quote requests are open, you can ask for a parts quote from the app. A request contains the vehicle brand, the parts you are asking about (number, quantity, and name and note if given), your city, a contact phone number and, if you enter them, the vehicle, VIN and a general note. The country comes from the device's region setting, not from location services.

The server sends the request to matching parts suppliers so they can quote. They see the request, including country, city, vehicle, VIN and notes, but only the supplier whose quote you accept sees your phone number.

10. Buying VIP

On iOS, plans offered by the store are bought through Apple In-App Purchase. Apple handles the whole payment; we never see or store your card number or payment details.

To confirm a transaction is genuine, the StoreKit receipt is checked by a verification service. The server keeps what it needs to manage your entitlement: product ID, original transaction, the token that links the transaction to your account, expiry and refund/revocation status. VIP belongs to your T2Car account; changing devices does not lose what you bought. Card data is handled by Apple alone.

11. Children

T2Car is a technical reference tool. It is not directed at children and does not knowingly collect children's data. The service processes only the data described in this policy.

12. Your rights

You can delete your account in the app without contacting support. Deleting closes the account: you are signed out on every device and the Apple authorisation is revoked, but the server does not erase your data. What is kept, why and for how long is on Delete your account and what happens to data.

Usage events are deleted after 90 days, installation records after 400 days without activity, and daily access records with IP address after 30 days. Records of purchases, saved items, jobs, reports, price requests, VIN lookups and violations are kept as described there.

For questions about your account or data, write to [email protected].

13. Changes to this policy

When this policy changes, the date at the top of the page changes with it. If a change lowers the level of protection, we will tell you in the app before it applies.

14. Contact

Send privacy questions to [email protected], or see the Support page.