Privacy Policy

Data: Name, email address, optional phone number, company, job title, fleet size, message content, preferred contact channel, language, and technical request metadata.

Purpose: Responding to enquiries, preparing demos, qualifying Enterprise requests, and keeping sales/support context.

Legal basis: Art. 6(1)(b) GDPR for pre-contractual requests and Art. 6(1)(f) GDPR for business communication and service security.

Retention: Enquiries are kept while the request is active and then retained only as needed for business documentation or legal obligations.

Data: Name, email, password hash, session cookies, email verification state, password reset tokens, role, locale, login/session activity, and admin acting-user context. For the most recent login only, we also record the platform used (web, iOS, or Android), the IP address, and the browser/device (user agent) string.

Purpose: Creating accounts, signing users in, protecting accounts, sending verification/password emails, and detecting and preventing unauthorized account access.

Legal basis: Art. 6(1)(b) GDPR for account delivery and Art. 6(1)(f) GDPR for security and abuse prevention.

Retention: Account data is kept while the account exists. Security logs and reset/verification tokens are limited according to operational need. The most-recent-login platform, IP address, and device/browser data are overwritten on each new login and are not kept as a history.

Data: Vehicle details, VIN lookups, mileage, reminders, service logs, expenses, uploaded documents, document metadata, telemetry provider settings, and related support history.

Purpose: Providing the Fahrnex SaaS features for vehicle maintenance, reminders, documents, expenses, analytics, telemetry, and support.

Legal basis: Art. 6(1)(b) GDPR for product delivery and Art. 6(1)(f) GDPR for product reliability and support.

Retention: Vehicle and document records remain available while the account is active or until the user deletes them, subject to legal retention duties.

Data: Aggregated event names, public page paths, referrer domain, campaign parameters, inferred visit intent, device/browser category, language, account identifiers where applicable, timestamps, limited non-sensitive metadata such as plan type or feature category, and Google Analytics 4 measurement data where visitors opt in.

Purpose: Understanding public-page interest, campaign performance, feature usage, reliability, conversion, and support demand. Google Analytics 4 should load only after analytics consent, while non-essential advertising and retargeting storage remain disabled.

Legal basis: Art. 6(1)(a) GDPR for consent-based analytics and Art. 6(1)(f) GDPR for product improvement, operational insight, and service reliability where data is processed without non-essential cookies.

Retention: Analytics events are kept only as long as needed for product and operational reporting, then aggregated or deleted according to the retention policy.

Data: Plan, subscription status, invoice data, billing name, billing email, payment preferences, Stripe checkout references, refund claims, and invoice PDFs.

Purpose: Managing paid plans, invoices, refunds, payment confirmation emails, and accounting records.

Legal basis: Art. 6(1)(b) GDPR for billing performance and Art. 6(1)(c) GDPR for statutory tax/accounting duties.

Retention: Commercial and accounting records may be retained for statutory retention periods, commonly up to 10 years in Germany depending on record type.

Data: Ticket subject, category, priority, messages, assigned admin, notification settings, notification logs, and reply history.

Purpose: Providing customer support, documenting support actions, and sending support replies or reminders.

Legal basis: Art. 6(1)(b) GDPR for support related to the service and Art. 6(1)(f) GDPR for support quality and dispute documentation.

Retention: Support records are kept while needed for customer service, product quality, and legal defence.

Data: Precise device location (GPS coordinates) when you use location-aware features such as nearby fuel station search, and an Expo push notification token together with your device platform (iOS/Android).

Purpose: Finding nearby fuel stations and prices (your rounded coordinates are forwarded to our fuel-price data provider, Tankerkoenig, to retrieve nearby station data), showing location-aware vehicle workflows, and delivering reminder and account push notifications to your device.

Legal basis: Art. 6(1)(a) GDPR for location access, which is requested via an explicit device permission prompt and only used while the relevant feature is active, and Art. 6(1)(b) GDPR for delivering push notifications you have enabled.

Retention: Location coordinates are used for the current request and are not stored after the nearby-station search completes. Push tokens are kept while your account and app installation remain active, and are removed when you log out, uninstall the app, or revoke notification permission.