Privacy Notice

Draft V1 notice for the local MVP. Production launch requires legal review, final business address, provider list, retention periods, and support contact.

Data handled

The product is designed to handle workspace user profiles, customer contact details, service addresses, route locations, bin/service data, payment status metadata, message history, service photos, imports, sync events, and audit logs.

Payment data

SoLoRoutePro should not store raw card numbers. Card-on-file, subscriptions, invoices, retries, and update links should be handled by Stripe or the configured payment processor.

Exports and deletion

Workspace owners must be able to export customer, route, billing-status, and service-history data. Deletion requests should preserve required audit and financial records only where legally necessary.