Privacy Policy

• //Account information: name, email address and username/handle. You sign in with Google or Discord, or with a one-time link sent to your email; we hold no password. If you sign in with a third-party provider, we receive basic profile information from that provider as permitted by your settings there.
• //Profile information: any bio, location (as you choose to enter it), avatar, and other details you add to your public or private profile.
• //Vehicle and build data: information you enter about your vehicles, including make, model, year, VIN (where you provide it), chassis code, modifications, service and maintenance records, mileage, specifications, and related notes.
• //Media: photos and files you upload (for example, images of your vehicle). See Section 2.4 regarding location metadata in photos.
• //Communications: information you provide when you contact us for support, respond to surveys, or otherwise communicate with us.
• //Payment information (when applicable): if and when paid features are enabled, payments are processed by our third-party payment processor (Stripe). We do not collect or store your full payment card details on our servers; Stripe handles card data directly. We receive limited information such as subscription status, transaction records, and the last four digits/card type as provided by the processor.
• //Identity verification (when applicable):if you choose to complete identity verification ("Red Check"), verification is performed by our third-party provider (Stripe Identity). We receive the result of the verification and related status information; the underlying identity documents are handled by the verification provider, not stored by us.

• //Usage data: how you interact with the Service, including pages/features visited, actions taken, timestamps, and general activity (used, for example, to compute active-user metrics and improve the Service).
• //Device and log data: IP address, browser type, device type, operating system, referring pages, and similar technical information.
• //Cookies and similar technologies: we use cookies and similar technologies for authentication (keeping you signed in), security, preferences, and analytics. See Section 8.

• //Authentication providers: if you sign in via a third-party provider, we receive profile information as described above.
• //Vehicle data services: we may use third-party services (for example, VIN-decoding databases such as the U.S. NHTSA vPIC service) to enrich vehicle information you provide. We send the VIN you enter to such services to retrieve specifications.
• //Payment and verification providers: as described in Sections 2.1 and 4.

Photos can contain embedded location metadata (EXIF/GPS). To protect your privacy and security, TougeX strips location and identifying metadata from images upon upload before they are stored or displayed. However, you are responsible for the content visible within your photos (for example, a recognizable location in the background). Do not upload images you are not comfortable sharing according to your chosen privacy settings.

If you pair an OBD-II adapter with the TougeX app, the app connects to it over Bluetooth to read what your car reports: diagnostic trouble codes and live values such as engine speed and coolant temperature. Live readings are shown on your phone; they are not uploaded as a stream. What we store on our servers is:

• //Trip summaries: when a trip started and ended, its distance and duration, and coarse speed and coolant bands (low, mid or high) — never a recording of the drive.
• //Trouble codes: the codes your car reports, when each was first and last seen, and whether it cleared.
• //Your adapter:its Bluetooth identifier (on Android, the adapter's hardware address), the name it advertises, its firmware, the result of our compatibility check, and an odometer reference used to keep your mileage current.
• //Performance runs:if you record a run (for example, 0–60), its measured result and, for a verified run, the run's time series of speed and engine values, stored privately. Your phone may record positions during a run; we delete them when the run is uploaded and store no location from it.

Open trouble codes are part of the vehicle details sent to our AI provider when you use Diagnose or TunerX (see Section 4.1).

• //Near me: when you ask for meets near you, the app sends your current location with that request so we can find nearby meets. We do not store it.
• //Live position at a meet: off by default. At a live meet you have checked into, you can choose to share your position with the other checked-in drivers there who can view live positions. You choose it each time, and you can stop at any moment. By default your position is approximate — rounded to an area of about 150 metres before we store it; only if you choose exact sharing do we store your precise position. We keep your current position only, never a history: each update replaces the last, stopping removes it, a position older than 90 seconds is no longer shown, and a daily cleanup deletes positions from meets that have ended or that have gone stale.

Messages you send — direct messages, club threads and meet threads — are stored on our servers so they can be delivered to, and shown to, the people in that conversation: the other person in a direct message, the members of a club, and the people who can see a meet. They are not end-to-end encrypted. You can delete a message you sent.

If someone reports a message, our moderators see the reported message in our moderation queue to review the report, and may hide it if it breaks our rules. If you delete your account, the messages you sent stay in the conversations of the people who remain, shown as from "deleted" rather than from you; their attachments are deleted.

With your permission, the app uses your camera to scan a code — a driver's code, a lobby code, or a VIN barcode — which is read on your phone; the scan image is not uploaded. You can also take photos in the app to add to your garage, your profile or a post.

Before we store a photo, we remove its location and other embedded metadata (EXIF, XMP and IPTC), and we reject the upload if any of it survives. Your profile picture and cover, the covers of clubs and meets, photos of PitX listings, and photos posted in a public club or to a public meet are stored with our storage provider (Cloudflare R2) at an address that is not published but that anyone who has its link can open. Photos of your vehicles are stored privately: you see them in your account, and other people can see them only while the vehicle is public or the photo is in a gallery post that is live. Making a vehicle private stops every shared link to its photos at once. Photos posted in a private club or to a private meet, documents and receipts, datalogs, performance-run data and design files are stored privately and served only to people permitted to see them.

When you sign in on the app, we record the device: its platform (Android or iOS), the app version, and the device's name as your phone reports it — which may include your name — so that you can see your signed-in devices and sign them out from your account. Your sign-in is kept in your phone's secure storage. Where your phone supports it, sensitive actions are confirmed with a key held in its secure hardware and unlocked by your fingerprint or face; your fingerprint or face data stays on your phone and is never seen by TougeX.

Some tools send information to Anthropic, which provides the AI models behind them, to produce your result. Anthropic processes it on our behalf as a service provider. Each tool sends only the following:

• //Diagnose:your vehicle's details — year, make, model and chassis, mileage, specifications, installed modifications, service history (including notes you wrote on it), maintenance status, track days (venue and best logged lap), open trouble codes from your OBD adapter, and open recalls — together with the symptom you describe, any trouble code you enter, and your conversation with the tool. We do not send your VIN, your name or your account details.
• //TunerX: the same vehicle details (including planned modifications) when you choose a vehicle from your garage; what you tell it about the tuning platform, fuel, hardware, budget and goal; and your conversation with the tool. For a datalog, it sends a summary we compute from the log on our servers — never the log itself, which is stored privately.
• //DesignX: the part type, your request and instructions, your conversation with the tool, and — when you design for a vehicle — its fitment details (for example, bolt pattern and hub bore). The design code this produces is run on our computing provider, Railway, to build the part files; Railway receives the code, not your account details.
• //Receipt scan:the receipt image or PDF you choose to scan, including anything printed on it (for example, a shop's name, your name, or part of a card number).

What you enter in these tools and the results are stored on your account so you can return to them.