Your car's
complete memory.

Teslogr uses Tesla's official OAuth and asks for the read-only Fleet API scopes needed to power the app: vehicle_device_data (state, charge, climate, drive history), vehicle_location (GPS so drives can be mapped), and offline_access (so the app keeps working without re-prompting you weekly). We do not request the vehicle_cmds scope — Teslogr is read-only and cannot lock, unlock, honk, climate-control, or otherwise command your car. You can revoke Teslogr's access at any time from account.tesla.com → Security → Third-Party Apps.

We collect what the Fleet API returns for the scopes above: battery state, location, lock state, climate, tire pressure, sentry status, and per-drive / per-charge telemetry (route geometry, speed, energy, duration). It's stored in an encrypted Postgres we operate, scoped to your account. We never see or store your Tesla password, we don't share data with advertisers or brokers, and we don't train AI models on your data. You can export everything as CSV/JSON or delete your account to wipe it permanently.

Tesla charges approved third-party developers roughly $3 per vehicle per month for Fleet API access on top of metered command and telemetry usage — this is the largest single line item we pay for every connected car. On top of that we run telemetry polling, an encrypted Postgres for your full history, Mapbox tiles, reverse geocoding, weather data, payments and (on Pro) the LLM tokens behind chat and drive narratives. The pricing block above breaks the unit economics down honestly. We don't sell data or run ads, so subscriptions are how the service stays alive.

No. Teslogr is intentionally read-only. We never request the vehicle commands scope from Tesla, so even if our servers were compromised an attacker could not lock/unlock, honk, flash lights, control climate, open the trunk or start a charge through us. If we ever introduce commands it will be opt-in, scoped per vehicle, and require you to re-authorize Tesla with the new permission.

When you connect a Tesla account, you're redirected to auth.tesla.com — Tesla's own login page. You sign in there, see exactly which scopes Teslogr is requesting, and approve them. Tesla then sends Teslogr a short-lived access token and a refresh token; we never see your password. Tokens are encrypted at rest with AES-256. You can revoke Teslogr at any time from your Tesla account settings, and the next API call we make will fail cleanly — no orphaned access.

No. Teslogr is an independent project and is not affiliated with, endorsed by, or connected to Tesla, Inc. in any way. We're an approved third-party developer on Tesla's Fleet API, which is the same public program any other Tesla app uses.

Every Tesla that's eligible for the Fleet API: Model 3 (including Highland), Model Y (including Juniper), Model S, Model X, and Cybertruck. If a vehicle shows up in your Tesla account, it'll show up in Teslogr.

Teslogr is in private beta today. Join the waitlist to be notified when public sign-ups open, and early subscribers will be offered a founder rate on annual plans.