Privacy
Collect less. Explain what is stored.
The consumer organizer and fleet demo keep case details in the browser. The optional fleet assessment and Health Check application store only the business contact and workflow information needed to review the request.
Information entered into the tools
Ticket details, plate information, timelines, evidence notes, fleet rows, and draft text are processed in the visitor's browser. TicketTriage does not intentionally transmit or store those entries on its servers. Closing or clearing the browser may remove locally stored work.
Fleet assessment and Health Check applications
If a business chooses to save a Leakage Score or apply for a Health Check, TicketTriage stores the submitted business name, business email, industry, approximate vehicle and ticket volumes, assessment result, workflow description, concerns, consent choices, source label, status, and submission date. The application form must not be used for plate numbers, summons numbers, driver names, ticket facts, or evidence files.
Accepted audit materials
If a Health Check is accepted, TicketTriage may issue a unique Dropbox File Request for the agreed limited materials. Dropbox processes those files under its own privacy and security terms. The request must not be shared publicly or reused for another business. TicketTriage limits access to the accepted work and removes or restricts materials after the agreed retention period.
Limited review and retention
Application information is used to evaluate fit, respond by email, deliver the requested workflow review, prevent duplicate submissions, and measure the acquisition funnel. Rejected or inactive applications are intended to be deleted within 90 days; accepted pilot records are kept only while needed for the agreed service, accounting, dispute resolution, and legal obligations. Email the address below to request access, correction, deletion, or withdrawal from follow-up.
Privacy-conscious measurement
To distinguish outside interest from owner testing, TicketTriage creates a random temporary browser-session token in session storage. The server keeps only a one-way hash of that token, along with the date, page path, campaign label, referring domain, and action type. The token is not a cookie, does not follow a visitor after the browser session ends, and is not tied to a name or email address. Only the referring domain is retained, never the full referring URL. The application uses the browser's automation signal and user-agent category to filter obvious bots, but does not store the user-agent string. Analytics older than 90 days are removed. Browser Do Not Track is honored.
What analytics never contain
Analytics do not contain a ticket number, plate, driver name, ticket facts, draft, evidence, email address, full referring URL, IP address, or persistent visitor identifier. Owner and tagged test sessions are kept out of outside-session totals, and the private growth dashboard does not count itself as a pageview.
Payments and outside websites
Payments are processed by Stripe, PayPal, or another checkout provider under that provider's own privacy practices. TicketTriage does not receive or store card or bank details. Links to NYC.gov and other external services are governed by those sites' policies.
Questions, deletion, or opt-out
Email jauntinoanderson@gmail.com with a privacy request or to opt out of fleet follow-up. Do not email ticket evidence, plates, summonses, or driver information unless TicketTriage has accepted a limited audit and provided a separate secure-materials instruction.