Privacy Policy

1. Effective date

This policy is effective as of September 26, 2026, the date it was last updated. We may revise it from time to time; see the Changes section below.

2. Information we collect

Axlyne is built local-first: vehicle profiles, scans, trips, and adapter records stay on your device unless you export and share them. A fresh installation creates a guest identity with our authentication provider so subscriptions can be purchased and restored without registering. That guest identity is a random identifier. It carries no email, name, or other personal detail, and the app shares it with our subscription-management provider to check, purchase, or restore Axlyne Pro. You stay signed out of any account until you choose to create one; choosing to register upgrades that same guest identity rather than creating a second one. Some installations from an earlier version may keep a limited session created by that version. The categories below describe everything the app may handle.

Account data: our authentication provider assigns a guest identifier on first launch, and if you choose to create an account or sign in with email and password, Google, or Apple, it assigns or returns an account identifier and session credentials. The app stores either in protected storage on your device and shares it with our subscription-management provider to check, purchase, or restore Axlyne Pro. Vehicle profiles, scans, trips, and adapters do not leave your device for account backup. A saved-record copy leaves the device only for AI chat, and only after you tap Start chat.

Abuse-prevention counters: when a signed-in user requests an account-data export, our servers keep a bounded request counter tied to the account identifier for up to seven (7) days. We use it only to limit abuse, never for advertising, analytics, or tracking.

Agreement records: when you accept the current Terms and Privacy Policy, Axlyne records an acceptance receipt containing the document revision, the device-reported acceptance time, platform, and app version. Acceptance while signed out is stored only on the device. When you sign in, a copy of that receipt is linked to your account and stored on our servers with the server receipt time. The original device receipt stays on the installation.

Optional sign-in data: if you choose email and password, Google, or Apple sign-in, our authentication provider processes the identifiers and authentication data needed for that method. Google sign-in requests OpenID, email, and basic profile information. Apple sign-in may provide your email and name according to your Apple choices. We do not receive your Google or Apple password.

Infrastructure logs: our hosting provider automatically records request metadata for every request your device makes to our servers, including the source IP address; device and client metadata; connection security metadata; an approximate location derived from the IP address (city, region, postal code, country, and network organization); and, for signed-in requests, account and session metadata. The provider retains these logs for a limited period set by our service plan, currently no longer than ninety (90) days. Axlyne does not copy the raw IP address or IP-derived location into the Axlyne application database and uses these logs only for service operation, abuse prevention, security, and debugging, never for advertising or personalization.

Sign-in link material: when you sign in with Apple or Google, the app passes the provider's authorization credential to our servers. Our servers validate it with the provider and keep only encrypted revocation material linked to your account identifier. We use that material only to keep the sign-in link verifiable and to revoke it automatically if you delete your account. Raw provider credentials are never written to logs, analytics, support output, or account exports; an export includes only the provider name, revocation state, and timestamps.

Vehicle and diagnostic data: vehicle profile details (such as a nickname, year, make, model, and a Vehicle Identification Number if you enter one) and the trouble codes, reported statuses, systems, and diagnostic responses recorded locally from a scan. A physical scan reads the vehicle's VIN. If the profile has no VIN, Axlyne saves the one it reads; if a VIN is already saved, the vehicle's VIN must match, and Axlyne refuses to save evidence when the VIN is missing, invalid, or different. Axlyne may show the vehicle-reported malfunction-indicator state, emissions-related code count, and supported readiness-monitor completion. It does not infer missing data, present freeze-frame observations, or predict an emissions-inspection result. While an adapter is connected, the app can display live read-only readings from it; until a VIN-verified scan matches the selected vehicle, they are labeled as not yet matched to it. The app processes those live values in memory and does not save them in scans or reports. The demo adapter is clearly labeled and simulated. This release does not send the raw VIN, year, make, or model to NHTSA. Network VIN decoding and NHTSA campaign or complaint lookup are unavailable.

Optional AI chat data: AI chat is available only after a signed-in Axlyne Pro user reviews the current disclosure and taps Start chat. Your device sends recent messages from the visible chat thread and a limited record packet to our servers. Depending on the selected record, that packet can include a scan reference; vehicle year, make, model, and engine; scan time and source; trouble codes and statuses; saved readings and availability; malfunction-indicator, readiness, protocol, and responding-module fields; and maintenance reminders. The structured packet excludes VIN, device location, mileage routes, adapter identifiers, and unverified scans. Contextual AI requires a separate opt-in to the current contextual-AI disclosure for each chat session. After that opt-in, our servers send OpenRouter and its selected model provider your redacted current question, a bounded recent conversation of up to four earlier messages, today's date, and these saved-record facts for each vehicle in the chat, up to six vehicles: vehicle year, make, model, and engine as saved in the vehicle profile; whether its latest record is saved, missing, or simulated; trouble codes and statuses; code-read coverage; saved readings with their names, known units, and quality; malfunction-indicator (check-engine light) state; in a chat about one scan, readiness monitor names and whether each is ready; and up to three open maintenance reminders per vehicle, with the reminder title, due date, and due mileage. Saved text labels, such as make, model, engine, reading and monitor names, and reminder titles, are redacted and limited to 80 characters each. The model request excludes VIN, nicknames, notes, scan references and identifiers, protocol, scan timestamps, account identifiers, device location, mileage routes, and adapter identifiers and logs. We attempt to remove common identifiers from chat text and saved labels, but redaction cannot guarantee that all personal information is removed. Do not include names, contact details, VINs, addresses, or other personal information in your questions, vehicle details, or reminder titles. In contextual chat, the model writes the reply as general guidance, never a diagnosis or a verdict on whether a vehicle is safe to drive. Our servers check the reply's trouble codes, numbers, and safety claims against your saved record and messages before showing it. If the reply fails those checks, our servers show a plain summary of the saved record instead. Answers may repeat details from your redacted question or conversation. Older clients and requests without the new contextual consent use the limited legacy flow: the external model receives only fixed intent, language, layout, and category selections, and our servers render the answer from validated fields. Simulated records stay labeled as demo data. Our servers use your account identifier for access, usage limits, and duplicate-request controls. Infrastructure logs and short-lived pseudonymous abuse-control records follow the retention described below. We do not add your account identifier or source IP address to the model request.

Optional AI-answer reports: a signed-in user can report a displayed AI answer as inaccurate or unsafe. The report stores an encrypted copy of that exact answer, linked to your account identifier, together with the reason and timestamps. The answer may contain saved vehicle or scan facts and details repeated from your redacted question or recent conversation. We do not attach the original question, other chat turns, the original record packet, device data, request address, or a free-form report field as separate report data. Personal information that remains in an answer is part of its encrypted copy. No AI model provider receives the report. Report review may be enabled later; if it is, reviewers see the answer without the account identifier stored with the report. Account deletion removes the report immediately; otherwise it expires after ninety (90) days.

Connection data: the advertised device name, connection transport, and a one-way hash of the local device identifier. These values stay on your device and are used only to remember a connection. Axlyne does not derive or store an adapter compatibility, clone, quality, capability, or reliability score.

Location data: manual GPS recording uses precise device location to estimate a trip's distance while the app is in use. Automatic mileage is off until you turn it on, review the location disclosure, and grant the requested permissions. When enabled, Axlyne collects precise location to detect and record drives even when the app is closed or not in use, subject to operating-system limits. It records sample times, coordinates, accuracy, speed when available, and gaps in sampling. Turn off Automatic mileage in Mileage to stop background location, or revoke location permission in your device settings. Stopping a manual recording does not turn off Automatic mileage.

Mileage records and destinations: routes, trip classifications and notes, repeated-destination suggestions, and places you name or merge stay on this device unless you choose to export them. Axlyne groups reliable recorded endpoints locally; it does not send them to a geocoding service or an AI provider. A destination suggestion does not establish a trip's business purpose. You choose and confirm that purpose. Where a physical OBD connection supplies a verified odometer reading, Axlyne may retain the reading, time, raw response, responding-module and protocol details, and the local vehicle and connection identifiers as mileage evidence. Reports identify GPS distance separately from supported odometer evidence.

Optional mileage reminders use local notifications scheduled on your device. They do not send your routes, destinations, or trip classifications to a notification server. Location samples and mileage records are stored in the app's local SQLite database with operating-system app storage protections; Axlyne does not add database encryption. Files you export may contain precise routes and destinations. You choose where to share them, and copies outside the app remain under the recipient's or destination app's control. When you use AI chat or answer reporting, our hosting provider's infrastructure logs retain IP-derived approximate location and network metadata for the limited period described above.

Local app data: settings and operational state needed to run the app remain on your device. This release does not send product analytics, crash reports, or performance telemetry to us or to an error-monitoring provider.

Purchase data: our subscription-management provider receives the account identifier, app-store purchase and product identifiers, subscription status, and entitlement status needed to provide and restore Axlyne Pro. Payment card details are handled by Apple or Google and are never received or stored by us.

3. How we use information

We use each category only for the specific purposes below, and not for unrelated ones.

To provide core features: read diagnostic responses, record trouble-code observations, display live read-only readings from a connected adapter, show labeled demonstrations, log mileage, and store local history.

To provide identity: process optional account creation or sign-in that you request and keep subscription records associated with the correct signed-in account identifier. For Apple and Google sign-in, retain encrypted revocation material so the linked authorization can be verified and revoked when you delete the account.

To operate subscriptions: confirm and restore your entitlement through the app store.

Optional Axlyne AI chat: Axlyne AI explains saved OBD observations, refers to saved record facts, answers general automotive questions, and helps you prepare questions for a qualified technician. General information is distinct from findings about your vehicle. It can give general guidance, such as what a code commonly means, what is commonly checked, and rough typical cost ranges that vary by shop and region. It does not diagnose a fault in your vehicle, decide whether a vehicle is safe to drive, or give repair quotes. Verify any guidance with a qualified technician.

AI security: we use signed-in account counters, bounded usage budgets, duplicate-request controls, and short-lived pseudonymous request records to detect and stop fraud or abuse and to enforce our Terms. Our servers do not store the raw IP address in the Axlyne application database; our hosting provider's infrastructure logs retain request metadata for a limited period as described above.

To improve and support the app: respond to information you choose to include in a support request and use release testing performed before distribution.

To meet legal obligations: comply with applicable law and respond to lawful requests.

We do not sell your personal information, and we do not use your vehicle, diagnostic, or location data for advertising or for training artificial-intelligence models. Model requests require endpoints that OpenRouter identifies as zero-data-retention and prohibit provider data collection. We disable OpenRouter response caching for contextual requests. These controls govern the model request; the operational metadata and answer reports described in this policy have separate retention periods.

We do not sell personal information and we do not share it for cross-context behavioral advertising, as those terms are defined by California law. We have not sold or shared personal information in the preceding twelve (12) months, and we do not knowingly sell or share the personal information of anyone under sixteen (16).

4. Service providers and sub-processors

We use a small number of third-party providers to run the app. They process data as needed to provide their service under their applicable agreements and privacy terms. The current categories of providers are:

Hosting, backend, and authentication: a cloud platform that hosts our servers and database, authenticates optional accounts, and stores the account records and encrypted sign-in link material described in this policy. Its infrastructure logs retain request metadata for a limited period.

Subscription management: a subscription-management provider that receives the account identifier and app-store subscription information needed to validate, manage, and restore purchase entitlements and to provide subscription analytics.

AI model processing: OpenRouter routes contextual requests to a model provider after the session opt-in described under Optional AI chat data. It receives the redacted question, bounded recent conversation, today's date, and the saved-record facts described there, and writes the contextual reply that our servers check before showing it. We require zero-data-retention routing and deny provider data collection, including use for training, and disable OpenRouter response caching for contextual requests. Legacy requests without the new contextual consent send only fixed, non-record selections. Do not put personal information into chat text: automated redaction can miss it.

App distribution and billing: Apple and Google, which distribute the app and process all payments for subscriptions.

We may add, remove, or change providers over time. A current list is available on request by emailing axlyne@proton.me. We choose providers that offer appropriate security and contractual data-protection commitments.

5. Legal bases for processing (GDPR)

For users in the European Economic Area, the United Kingdom, and Switzerland, we rely on the following legal bases under the GDPR and equivalent laws.

Performance of a contract: to provide the app and the features you request, including optional account creation, sign-in, and subscription access.

Consent: for optional features that you switch on, such as location-based mileage tracking. We also rely on consent for AI chat and a confirmed AI-answer report. You can withdraw that consent by stopping use of the optional feature, with no effect on processing already carried out.

Legitimate interests: to secure the app, prevent abuse, and fix defects, balanced against your rights.

Legal obligation: to comply with applicable law and respond to lawful requests.

6. Data retention

On-device data (vehicles, scans, trips, reminders, and logs) is kept on your device until you delete it in the app or uninstall the app. You control it.

Signed-in account data is kept while the account is active. Uninstalling the app does not by itself delete the backend account. When you delete your account, our deletion service records a deletion marker, delete your subscription customer record with our subscription-management provider and verify that it is gone, remove any matched waitlist entry, revoke each stored Apple or Google sign-in link and verify the revocation, delete the encrypted link material, and then remove the authentication account and its linked records. Apple and Google retain store transaction records under their own policies and applicable law. To prevent a deleted subscription customer from being recreated, Axlyne retains a one-way hash of the subscription customer identifier indefinitely as a deletion-suppression record. It retains no raw customer identifier, email address, provider token, or purchase record, it is not included in the account export, and it is not user-deletable because removing it would remove the protection. We may retain other limited records when required by law or needed to protect the service from abuse. Abuse-prevention counters are deleted with the account or automatically after seven (7) days.

Account-linked agreement receipts remain immutable on our servers while the account exists, appear in the account-data export, and are deleted when the account is deleted. Device-local agreement receipts remain on the installation until local app data is deleted or the app is uninstalled.

Location samples used for a trip are retained as part of that trip record under your control on the device, subject to your export and deletion choices. Automatic detection also keeps a bounded local buffer of recent candidate samples and operational events. Saved destination names and preferences remain until you remove them or delete local app data. Turning off Automatic mileage stops new background collection; it does not erase saved trips. Deleting local app data stops mileage capture and removes its local records. Axlyne cannot remove files you already shared outside the app and does not promise forensic erasure from operating-system backups or storage.

AI retention: Axlyne saves completed chat history and drafts on your phone, separated by signed-in account and vehicle or scan, so you can resume a conversation. Signing out does not erase that local history; it is available again when the same account signs in on that installation. Use Clear chat to remove a conversation. Deleting its vehicle or scan, deleting local app data, or uninstalling the app removes the associated local history. Saved history does not restore consent to send another message. Our servers do not store your chat text, the record packet, or the assistant's answer except when you choose to report an answer as described below. Contextual requests do not use a plaintext prompt or answer cache. Our servers keep short-lived operational records: legacy request markers with a hit count and timestamps expire no more than thirty (30) minutes after creation and are cleaned up on a schedule; daily usage accounting and security events, including the contextual consent version, contain no chat text or record values and are deleted after thirty (30) days or when the account is deleted; account-linked rate-limit records are deleted after seven (7) days or on account deletion; pseudonymous abuse-control records normally remain for less than three hours. Aggregate daily usage totals contain no account identity or chat text. Our hosting provider's infrastructure logs retain request metadata for the limited period described above.

AI report retention: a confirmed AI-answer report stores the account identifier, server-generated report and answer identifiers, the encrypted copy of the exact answer with its protection metadata, the fixed reason, review-state fields, and creation, review, and expiry times. The encrypted answer may contain vehicle or scan facts and details repeated from your redacted question or recent conversation. We do not attach the original question, other chat turns, the original record packet, device data, request address, or a free-form report field as separate report data. Report identity, reason, review-state, and lifecycle metadata appear in the account-data export; the export omits the encrypted content. Account deletion deletes the report immediately. Otherwise it expires ninety (90) days after creation and is cleaned up on a schedule.

Backups and logs may persist for a limited additional period before being overwritten in the ordinary course.

7. Your privacy rights

Depending on where you live, you may have some or all of the following rights.

GDPR and UK GDPR: to access, correct, delete, restrict, or object to processing, to data portability, and to withdraw consent. You also have the right to lodge a complaint with your local supervisory authority.

California (CCPA and CPRA): to know what personal information is collected, used, and disclosed; to delete it; to correct it; to opt out of sale or sharing; to limit use of sensitive personal information; and not to be discriminated against for exercising these rights. We do not sell or share personal information as those terms are defined under California law.

Other US states: residents of states with comprehensive privacy laws (including Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Iowa, Delaware, and others as they take effect) have comparable rights to access, correct, delete, obtain a portable copy of, and opt out of certain processing of their personal data.

We will not discriminate against you for exercising any of these rights.

8. How to exercise your rights

To exercise any right, email axlyne@proton.me from the email address associated with your request, and describe what you would like to do. Much of your data can also be deleted directly in the app through the Your Data screen.

We will respond within the time required by applicable law and may verify your identity before acting. You may use an authorized agent where the law allows.

We will not discriminate against you for exercising a privacy right. If we decline a request, you may appeal by replying to our decision or emailing axlyne@proton.me with the word Appeal; we will respond within the period your state law allows and, if we again decline, tell you how to contact your attorney general.

9. Children

Axlyne is intended only for adults who are at least 18 years old and have reached the age of legal majority where they live. We do not knowingly collect personal information from children. If you believe a child has provided personal information, contact us and we will delete it.

10. International data transfers

We and our providers may process data in the United States and other countries. Where we transfer personal data out of the European Economic Area, the United Kingdom, or Switzerland, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses and equivalent mechanisms.

11. Security

We use reasonable technical and organizational measures designed to protect your information, including encryption in transit, encrypted storage of authentication session credentials on the device, encryption at rest for server-held Apple and Google revocation credentials, and access controls on our systems. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

12. Data breach notification

If a personal data breach occurs that is likely to result in a risk to your rights, we will notify the relevant supervisory authority and, where required, affected users, within the timeframes set by applicable law, including within seventy-two (72) hours where the GDPR applies and without unreasonable delay where US law applies.

13. Changes to this policy

We may update this policy as the app evolves or the law changes. When we make material changes, we will update the date at the top and, where appropriate, provide additional notice in the app. Your continued use after an update means you accept the revised policy.

14. Contact

For privacy questions or requests, email axlyne@proton.me. For general support, email axlyne@proton.me. Omniscient Labs LLC (“we”, “us”, or “our”) is the data controller for the processing described here. Our operations are based in Arizona, United States.

15. Do Not Track and Global Privacy Control

Axlyne is a mobile app and does not use web cookies or cross-site tracking, so browser Do Not Track and Global Privacy Control signals do not apply within the app. We do not track you across other apps or websites for advertising.

16. California Shine the Light

California Civil Code Section 1798.83 lets California residents request information about disclosures of personal information to third parties for their direct marketing purposes. We do not share personal information for third-party direct marketing, so there is nothing to disclose. You may still contact us to confirm.

17. Cookies and tracking technologies

The app itself does not use advertising cookies or third-party tracking technologies. Our providers may use strictly necessary identifiers to deliver their service, such as authenticating an account session or attributing a subscription. We do not use these for advertising.

18. Automated decision-making

Optional generative AI chat explains saved records and general automotive concepts, and helps prepare questions for a qualified technician. It does not provide AI diagnosis or automated decision-making that produces legal or similarly significant effects about you. Neither AI chat nor the diagnostic screens decides whether a vehicle is safe to drive or what repair it needs.