Privacy & cookies

This covers both transitlab.io and the simulator at app.transitlab.io. The short version: there are no accounts, nothing you build is stored on a server, and the only thing collected is anonymous usage analytics.

What there isn't

• No accounts, no sign-up, no login, no password.
• No database. There is nowhere on the server for your data to live.
• No advertising, no ad networks, no data sold or shared with anyone.
• No email address is collected anywhere on this site.
• No tracking across other websites.

The topologies you build

When you run a trace, the simulator sends your topology to the engine so it can be parsed and the path computed. It is processed in memory, the answer comes back, and it is gone. It is not written to a database, not written to a log, and not cached.

Your work stays in your browser. If you want to keep a topology, use download yaml — that saves a file to your own machine and is the only copy that persists anywhere.

Browser storage

The simulator keeps a draft of the topology you're editing in your browser's sessionStorage, under the key transitlab.draft.v1. It exists so an accidental reload doesn't throw away work you haven't downloaded.

• It never leaves your browser — it is not sent anywhere.
• It is per-tab and is erased when you close the tab. That is why sessionStorage was chosen over localStorage: your network designs shouldn't sit on disk indefinitely.
• Only unsaved work is kept. Loading an example stores nothing, and clicking discard on the restore notice erases it immediately.

Analytics and cookies

Both surfaces use Google Analytics 4 (property G-XJ4KTDCKST) to count visits and see which pages get used. It is aggregate usage measurement — how many people opened the simulator, not what anyone built in it.

These are the cookies, and they are the only ones:

• _ga — distinguishes one browser from another so repeat visits aren't counted as new people. Expires after 2 years.
• _ga_XJ4KTDCKST — GA4's per-property session cookie. Expires after 2 years.

Google processes this data as described in Google's privacy policy, and IP addresses are truncated by GA4 before storage.

Turning it off

Block the analytics script with any content blocker, use Google's opt-out add-on, or clear the cookies in your browser settings. Everything keeps working — the simulator does not depend on analytics loading, and nothing is gated behind it.

Hosting and logs

The site and simulator run on AWS (CloudFront, S3, and Lambda in us-east-1). Request access logging is not enabled, and the engine writes no log of what it parses or traces. AWS records its own standard operational telemetry at the platform level, as it does for any service running on it, and that is outside what this project controls.

Changes

If what's collected ever changes, this page changes with it and the date at the top moves. There's no mailing list to notify, because there's no mailing list.

Questions

Ask in the SoraWorx community channel. TransitLab is a SoraWorx project.