Transparency and operations

How pricing, data storage, and access controls work.

💰 Pricing transparency

How we price
and operate

We do not sell driving or charging records. We handle these records for service features, support, security, troubleshooting, and service improvement as described in our Privacy Policy. That policy also describes transfers to external services needed for these functions.

We use open-source software, while server operations, maintenance, and Tesla API integration still have ongoing costs. Subscriptions are billed monthly or yearly for each vehicle. Starting the 14-day free trial requires card registration. The battery health certificate is a separately priced one-time product. Check the amount and billing date at checkout.

Open source and published pricing

Monthly, yearly, and one-time product prices are published.

📦 Logical separation by tenant

How access to
vehicle data is separated

Vehicle data is stored in a shared PostgreSQL database. Application queries check tenant_id to separate tenants. We do not use a dedicated database per user or PostgreSQL row-level security (RLS). Storage and processing regions differ across the database, backups, and external services. The Privacy Policy describes purposes and integrations; actual regions depend on operational settings and provider contracts.

Administrative APIs are subject to role-based access control (RBAC) and audit logging. Website traffic passes through the Cloudflare proxy and Tunnel. The service uses Tesla Fleet API and Stripe. LINE is used when connected; Web Push uses the browser push provider when registered. Maps use OpenStreetMap tiles and the Geospatial Information Authority of Japan elevation API. Processing regions and settings vary by provider.

Logical separation in shared PostgreSQL

The application checks tenant_id in its queries.

External service integrations

Tesla, Stripe, and other services are used for specific purposes.

Audited access control

Administrative access uses RBAC and audit logs.

Built on published specifications

We independently develop this service using published specifications such as Tesla’s Fleet Telemetry protocol. Licenses and credits for the open-source libraries we use are available on the public OSS Licenses page.