How is VoltKeep driving data protected?

Updated August 18, 2026 · VoltKeep
Short answer

Detailed driving data — including routes and location — is encrypted with X25519 public-key cryptography before being stored on the server. The private key needed for decryption only exists on your device, so even VoltKeep operators cannot read the contents. Only numeric summaries (distance, energy efficiency) are aggregated server-side to power rankings and statistics. Vehicle Identification Numbers (VINs) are stored as SHA-256 hashes to prevent re-identification. Tesla OAuth tokens are kept in the iOS Keychain, and are also stored encrypted on our servers for automated telemetry maintenance.

Server-side encryption (X25519 + AES-GCM)

The driving data VoltKeep collects (route, speed, acceleration, battery state, etc.) is encrypted on your device before it ever leaves the iPhone. We use a hybrid X25519 public-key + AES-GCM scheme:

  • On first setup, your device generates an X25519 key pair
  • Only the public key is sent to the server. The private key stays in the iOS Keychain
  • The server encrypts data with that public key when storing it
  • Decryption happens on your device, using the locally held private key

With this design, not even our server administrators can decrypt your routes or location data. Even if the database were leaked, the contents remain unusable in their encrypted form.

Numeric summaries used for statistics

Numeric summaries — distance driven, energy used, efficiency, trip counts — are aggregated server-side to power rankings and statistics. These summaries contain no routes or location data. When published, they are only released as aggregate statistics that cannot identify an individual or vehicle. See our privacy policy for details.

VIN hashing

Tesla VINs are never stored as-is — they are kept as SHA-256 hashes.

This means database records are not directly tied to a specific vehicle. To look up a record by VIN, you'd have to hash the VIN first, and external matching against a known VIN list is impractical.

How Tesla OAuth tokens are handled

The access and refresh tokens issued by Tesla's OAuth flow are stored in the iOS Keychain on your iPhone.

  • Tokens are also stored encrypted on our servers to support automated telemetry maintenance
  • Your Tesla password is never handed over (OAuth means we don't see it)

Uninstalling VoltKeep removes the tokens from your Keychain, and revoking the session from your Tesla account also invalidates the tokens stored server-side.

Data deletion requests

From the app's settings you can run "Delete Account", which immediately erases all server-side data for your account (encrypted data, public keys, VIN hashes, auth tokens, and numeric summaries) and resets the data on your device. To remove only the data stored on your device, use "Reset All" instead. If you can no longer access the app, contact [email protected] (see our privacy policy).

Encrypted Tesla driving analytics, free to start.

The decryption key only lives on your iPhone — our servers can't see your routes or location data.

Get it on the App Store