Data controls

Delete your account

Last updated August 10, 2026

Axlyne works local-first. Vehicle profiles, scans, mileage routes, and saved adapters stay on your device. A fresh installation starts signed out. If you choose to create an account or sign in, Supabase creates or returns an account user ID. Axlyne sends that ID to RevenueCat for signed-in subscription access. An existing installation may retain a legacy anonymous Supabase session created by an earlier release. The current app does not create a new anonymous session automatically. You can delete local data inside the app or by uninstalling Axlyne.

Request deletion

If your account has an email address, email axlyne@proton.me from that address and write “Delete my Axlyne account” in the subject.

If you are signed in, you can also open Axlyne, go to Settings, then Your Data, and start the account deletion request there.

What gets deleted

  • The release-candidate deletion service records an erasure fence, requests deletion of the RevenueCat customer and verifies provider absence, removes the matched waitlist row, automatically revokes and verifies each stored Apple or Google authorization, deletes the encrypted provider credential, then removes the Supabase authentication account and linked database rows.
  • Axlyne stores encrypted Apple or Google revocation material linked to your Axlyne account only to verify the connection and revoke it during deletion. It is kept until replacement or verified revocation. Raw credentials do not appear in Axlyne logs, analytics, support output, or account exports. Exports contain only safe provider, state, timestamp, and non-secret revocation proof metadata.
  • If an existing federated account predates credential capture, sign in again with each connected provider. Deletion stays pending until Axlyne can revoke every linked authorization automatically. Manual provider-unlink instructions are not deletion proof.
  • Vehicle profiles, scans, mileage routes, and saved adapters remain on the device unless you delete them separately.
  • Public launch remains blocked until the exact production deployment and signed cross-device tests prove that a stale installation cannot recreate the deleted RevenueCat customer.
  • Axlyne retains a one-way SHA-256 digest of the RevenueCat customer identifier indefinitely as a security and deletion-suppression record. It contains no raw customer identifier, email address, provider token, or purchase record and is not included in the account export. The digest is not user-deletable because removing it would remove the erasure fence.

Apple and Google retain store transaction records under their own policies and applicable law. Deleting an account does not cancel a store subscription.