Privacy Policy

1. Information We Collect

The Service collects and stores the following information.

• User authentication information: Email address and display name. Email-registration passwords are stored as bcrypt hashes (Tesla passwords are not received or stored).
• Tesla Fleet API access token: Used for vehicle data retrieval and Telemetry configuration; encrypted with AES-GCM before database storage.
• Vehicle data: Driving history, charging records, battery status, vehicle location, and similar data. Stored in shared PostgreSQL and separated by tenant_id in application queries.
• Access logs: IP address, browser information, and access timestamps. Used for security and service quality improvement.
• Payment and refund synchronization records: We store the minimum Stripe object IDs, states, and verification summaries needed for reconciliation, without retaining raw webhook data containing personal information. Records linked to you are included in local data exports and removed when your account is deleted.

2. Purpose of Use

Information we collect is used solely for the following purposes.

• Providing and maintaining the Service
• Visualizing and analyzing Users' vehicle data
• Improving service quality and responding to issues
• Preventing unauthorized use and ensuring security
• Measuring first paid subscriptions from Google Ads with optional consent

3. Disclosure to Third Parties

Service providers receive the information needed to operate the features they provide. Visits to the website pass through the Cloudflare proxy and Tunnel. Cloudflare may process the visitor IP address, requested URL, HTTP headers, and submitted content to deliver and secure the website. Tesla Fleet API is used for OAuth, vehicle data retrieval, and Telemetry configuration. Stripe processes payments; card details are entered on Stripe's checkout page. LINE notifications and browser Web Push are sent only when the User links or registers those features. Map views use OpenStreetMap tiles, and route elevation calculations use the Geospatial Information Authority of Japan elevation API. S3 backup storage and operational alert services may be used depending on server configuration. Processing locations vary by provider and operational settings; not all processing necessarily takes place in Japan. Information may also be disclosed with User consent or where required by law.

4. Data Storage and Protection

The Service implements the following measures for User data.

• Vehicle data in shared PostgreSQL is separated by tenant_id in application queries (no dedicated database or RLS)
• Tesla OAuth access tokens are encrypted with AES-GCM before database storage
• TLS is used for website and external API communications
• Admin APIs are governed by role-based access control (RBAC) and audit logs

Encryption for the full database, host disks, and backups; backup destinations; and operator remote-access scope must be confirmed against the production host, backup settings, and provider agreements.

5. Security Measures and Responsibility

This Service is a subscription service operated by an individual developer.

Implemented safeguards confirmed in the code include application-level tenant_id checks, AES-GCM encryption of Tesla OAuth tokens, TLS communications, and RBAC and audit logs for admin APIs. Encryption for the full database, host disks, and backups; backup destinations; and operator remote-access scope require confirmation against the production host, backup settings, and provider agreements.

• Data backup: Because server failures and similar events could cause data loss, Users are encouraged to also keep their own backups of important data.
• Changes to the Tesla API: Changes to Tesla's API specifications may affect stored data or features of the Service.

The operator's liability for damages relating to the handling of personal information, and to use of the Service generally, is governed by Article 8 (Disclaimer and Limitation of Liability) of the Terms of Service. The disclaimer and limitation of liability in that Article do not apply where the operator has acted with intent or gross negligence.

6. Use of Cookies

The Service uses cookies (HttpOnly, Secure) for session management. Advertising measurement is optional. Only after you make the new allow choice do we load Google Ads code, which may send ad click identifiers, IP address and browser information, a restricted public-page URL, and a pseudonymous transaction identifier, amount and currency for your first paid subscription to Google. Ad events do not include Tesla authentication codes, vehicle identification numbers, driving locations, names or email addresses. We do not use ad personalization or enhanced conversions.

The consent preference and advertising cookies are retained for up to 90 days. Previous consent for service cookies is not treated as advertising consent. Browser tracking opt-out preferences are respected. Registration and purchases remain available without advertising consent. You can withdraw permission in Privacy Controls. Withdrawal stops new ad events but does not automatically retract information already sent to Google. See Google Privacy Policy for its processing.

Measurement may occur when you return to the site in a consenting browser; an automatic charge after a trial is not guaranteed to be reported immediately.

7. User Rights

Users have the following rights with respect to their own personal information.

• The right to request disclosure of personal data held about them
• The right to request correction or deletion of personal data
• The right to request complete deletion of their account and all related data

To make any of these requests, please use the Contact page. We will respond within a reasonable period.

8. Data Retention Period

Account information, driving and charging history, and user-entered records are retained as needed to provide the Service. Older raw vehicle state records are removed according to the system retention period. An account is not automatically deleted solely because it has been unused for a year.

Unresolved payment and refund synchronization records are retained until reconciliation is resolved. Only records confirmed to be unrelated and not linked to a user are removed once 30 days have passed since their last update.

Account deletion removes the account, vehicles, and related records from the current service database. Attachment files are removed by a subsequent deletion process. Audit records needed for security investigations, such as event times, hashed identifiers, and access-source information, may be retained separately. Existing backups are unavailable through normal account access and expire according to the backup retention policy. Transaction records held by Stripe or other providers follow their legal obligations and retention policies.

9. Changes to This Privacy Policy

When this Policy changes, the changes and their effective date will be announced on this page. Material changes to the handling of personal data will also be notified to registered email addresses before they take effect. Where the law requires consent, the operator will request it before applying the change. Continued use of the Service alone will not be treated as consent to a change that requires consent.

10. Contact

For questions or requests regarding privacy, please contact us via the Contact page.