Docs/Privacy Policy

Privacy Policy

How Transit Planner handles information, including analytics and product usage tracking, in a typical deployment.

Last updated: April 22, 2026

Note: This document reflects the current app behavior, including analytics instrumentation, but it should still be reviewed by counsel for your organization's specific deployment and legal needs.

Table of Contents

1.Overview2.Information We Collect3.How We Use Information4.Sharing and Third Parties5.Data Retention6.Analytics, Cookies, and Similar Technologies7.Security8.Your Choices9.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 and product analytics used to operate, secure, and improve the service — for example, request metadata, error logs, page loads, feature usage, overlay toggles, lines created, stations placed, portals added, import/export actions, and analysis-tool activity.
3

How We Use Information

  • Provide core functionality — map editing, imports/exports, AI-assisted workflows.
  • Maintain session history and recover work, where enabled.
  • Measure product usage and understand which tools are used most often, such as route generation, council workflows, overlays, and network-building actions.
  • 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.
AnalyticsIf analytics are enabled for a deployment, usage events may be sent to Mixpanel. These events can include page visits, feature usage, counts of lines and stations in a plan, station-placement and line-creation actions, analysis-tool usage, and related product interaction metadata.
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

Analytics, Cookies, and Similar Technologies

Hosted deployments may use analytics and browser storage technologies to understand how the app is used and to keep certain preferences or sessions working correctly. Where Mixpanel is enabled, the app may store a browser identifier and record product events tied to app usage.

Depending on configuration, analytics events may include items such as page loads, feature toggles, route generation requests, council-tool activity, imports and exports, total lines and stations in a project, lines created, stations moved or placed, portals added, and related interaction metadata. If a user is signed in, analytics may also be associated with that account identifier.

7

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.

8

Your Choices

Your choices depend on the deployment you are using. Local and self-hosted deployments may allow the operator to disable analytics entirely. Hosted deployments may also offer browser controls, privacy tools, or account settings that affect analytics and stored data.

If you want data deleted, exported, or corrected, contact the operator of your deployment. If you run Transit Planner yourself, you control those choices directly.

9

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.