Privacy Policy

Effective September 22, 2026

RouteViz is operations software for document destruction companies (“operators”). This policy explains what the service stores, why, and who can see it.

What we store

• Operator staff accounts: name, email, a salted password hash, sign-in codes, and which browser you have trusted.
• Operator business data: customers, service locations, containers, routes, visits, certificates of destruction, invoices and payments, and scanned documents an operator uploads for its customers.
• Driver activity at a stop: arrival time and, when the phone allows it, the arrival location; an optional photo; an optional customer signature; the driver’s name.
• Customer portal accounts and activity: name, email, password hash, and a log of searches, views, downloads and approvals, including the network address they came from. Operators show this log to their customers as a compliance record.
• QuickBooks Online connection (optional): if an operator connects QuickBooks, we store the OAuth tokens Intuit issues, encrypted at rest, the QuickBooks company id, and the QuickBooks ids of the customers, items, invoices and payments we synchronize.

How we use it

Only to run the service for the operator: planning routes, recording visits, producing certificates and invoices, letting the operator’s customers review scanned documents, and, when connected, exchanging invoices and payments with the operator’s own QuickBooks company. We do not sell data, use it for advertising, or train models on it.

QuickBooks Online data

When an operator connects QuickBooks, the service reads that company’s customers, items and income accounts so the operator can map them; creates and updates invoices and payments the operator sends; and reads payments so paid invoices can be marked paid here. It creates a customer or an item in QuickBooks only when the operator explicitly allows it. Access tokens are encrypted with AES-256-GCM and are used only for the operator’s own company. Disconnecting, from either side, deletes the tokens.

Who can see it

Each operator’s data is isolated to that operator. Its staff see it according to their role. Its customers see only their own jobs, documents and activity through the portal. The service provider’s staff access operator data only to provide support, on request.

Security

All traffic is encrypted in transit (TLS). Passwords are hashed with Argon2id. Office and portal logins require a one-time emailed code on a new browser. Uploaded documents and QuickBooks tokens are stored encrypted or on access-controlled storage. Databases are backed up nightly.

Retention and deletion

Scanned documents are kept for the retention period the operator sets and are then deleted automatically, with an audit entry. Certificates, invoices and activity logs are kept for as long as the operator’s account exists, because they are the operator’s business records. An operator can ask for its entire account to be deleted.

Contact

Questions about this policy: the address on the operator’s invoices.