Privacy
TripBoard stores the data needed to authenticate users, link Tesla accounts, and render trip, charging, maintenance, analytics, and assistant features. For self-hosted deployments, the deployment operator is responsible for how that data is retained and protected.
What TripBoard stores
Account records, linked vehicle metadata, trip history, charging sessions, maintenance records, assistant settings, and notification state may be stored so the dashboard can stay functional across sessions.
Tesla access
If you connect Tesla, TripBoard stores the tokens and session state needed to call the Tesla APIs you authorize. Protecting those credentials depends on the security of the deployment and its backing database.
Data handling
TripBoard does not need unrelated personal data to operate. If you no longer want data retained, remove the deployment data or ask the deployment operator to delete the stored records and credentials.