Privacy Policy

TrafficLite is operated by Workflow Corporation. For account data — who you are and how you sign in — we decide how it is used. For the traffic and billing data a workspace keeps (advertisers, contacts, contracts, logs, invoices), the workspace's organisation decides, and we process it on its behalf.

Account data

• Your name, email address and a hash of your password (never the password).
• If you sign in with Google, GitHub or Radio Workflow, the identifier and profile details that provider shares.
• Your language and theme preference, stored in cookies.

Workspace data

• What members enter: stations, advertisers and agencies with their contact details, contracts and rates, copy, programming, logs, as-run files, invoices and payments.
• Membership, roles and invitations, including invitees' email addresses.

Operational data

• An activity log of consequential actions (who changed what, and when), with the IP address the request came from.
• API request logs: method, path, status, timing, IP address and user agent.
• For paid plans, subscription and payment records. Card details are collected by our payment processor; we keep only the card brand, last four digits and expiry.

• To run the service: sign you in, show your workspace, and do what you ask.
• To bill for the subscription and handle failed payments.
• To send service email: invitations, password resets and notices about your account or billing.
• To keep the service secure, investigate abuse and fix faults.

We do not sell personal data, show advertising, or use workspace data to train machine-learning models.

TrafficLite uses only cookies it needs to work: a session cookie that keeps you signed in, and preference cookies that remember your active workspace, station, language and colour theme. There are no advertising or cross-site tracking cookies.

We share data only with service providers that help us run TrafficLite:

• Our cloud hosting and database provider, where the service and its data live.
• Our payment processor, for paid plans.
• Our email delivery provider, for service email.
• The sign-in provider you choose, if you use one.

Data also leaves the service when a workspace sends it somewhere: an automation export, a webhook, or an API client. Those destinations are chosen by the workspace, not by us. We disclose data to authorities only when the law requires it.

• Workspace data is kept until the workspace deletes it or the workspace is deleted.
• Account data is kept until you delete your account. Deleting an account also deletes any workspace in which you are the only member.
• Payment records and the activity log are kept as long as we need them for accounting, security and legal obligations.
• Deleted data leaves our backups as those backups expire.

You can update your profile and delete your account yourself under Settings. Depending on where you live you may also have the right to access, correct, export or erase your personal data, or to object to how it is used. Email support@workflowcorp.comand we will respond within 30 days.

If your details are held in a workspace you are not a member of — for example, as an advertiser contact — the station group that runs that workspace controls them. Contact them first; we will help if they do not respond.

Connections are encrypted, passwords are hashed, API keys are stored only as hashes, and access inside a workspace follows the roles its owner assigns. No system is perfectly secure; if we learn of a breach affecting your data we will tell you without undue delay.

We will post changes to this policy here and tell account holders about material changes before they take effect. Questions and requests go to support@workflowcorp.com. See also the Terms of Service.