Docs/Privacy Policy

Privacy Policy

How Transit Planner handles information in a typical deployment.

Last updated: March 16, 2026

Note: This document is a policy template intended for a typical deployment and should be reviewed by counsel for your organization's specific needs.

Table of Contents

1.Overview2.Information We Collect3.How We Use Information4.Sharing and Third Parties5.Data Retention6.Security7.Contact
1

Overview

This Privacy Policy describes common data flows in Transit Planner deployments. Actual data handling can vary depending on how the app is deployed — local, self-hosted, or hosted. The operator of your deployment is the "data controller" for most uses.

2

Information We Collect

Account information
If sign-in is enabled, your name, email, and profile image may be provided by the authentication provider.
User content
Routes, stops, boundaries, uploads, and messages you submit (including AI prompts and planning context).
Usage data
Basic logs needed to operate and secure the service — for example, request metadata and error logs.
3

How We Use Information

  • Provide core functionality — map editing, imports/exports, AI-assisted workflows.
  • Maintain session history and recover work, where enabled.
  • Monitor performance, troubleshoot errors, and prevent abuse.
4

Sharing and Third Parties

Transit Planner may send data to third-party services depending on enabled features:

Map renderingMap tile requests may be sent to a map provider (e.g., Mapbox). Their privacy policy applies.
AuthenticationSign-in can be handled by an identity provider (e.g., Auth0). Your profile data is managed by that provider.
AI servicesPrompts and related context may be sent to AI model providers when AI features are used.
Text-to-speechIf enabled, selected text may be sent to a speech provider to generate audio output.
5

Data Retention

Retention depends on deployment configuration. Local and self-hosted deployments can choose to retain data only on the local machine or server. Hosted deployments may retain data to support features like session history and auditing. Contact your deployment operator for their specific retention policy.

6

Security

We use reasonable administrative and technical measures designed to protect information. No method of transmission or storage is completely secure. We encourage you to use strong, unique credentials and to report suspected security issues to your deployment operator.

7

Contact

For privacy questions, contact the operator of your deployment. If you are running Transit Planner locally, you control your own data and are your own data controller.

For privacy questions, contact the operator of your deployment. See also our Terms of Use.