Customer control
Customers choose what to upload, what to review, what becomes saved history, and what they share with a shop.
Privacy overview
Use only what helps the customer-shop handshake.
Project Lazon's working privacy direction is to collect and retain only the account, vehicle, source-document, service-context, participation, feedback, and limited operational data needed to provide and secure the experience the person chose.
Exact access
Customer, shop, Field Rep, and Founder/Admin data should be separated and available only to the identity and physical location that needs it.
Source provenance
Originals, extracted candidates, customer-confirmed facts, explanations, and shop-approved wording remain distinguishable.
No secret promises
The final policy must name material processors and actual retention/model-use behavior. Project Lazon will not promise that data never leaves the platform unless production evidence supports it.
Do not place secrets in feedback or Cockpit notes.
Passwords, authentication tokens, full tax identifiers, banking or payment credentials, private identity records, and other highly sensitive material do not belong in ordinary notes, comments, telemetry, or support fields.
Privacy & data controls during early access
Signed-in customers can open Account & tools → Privacy & data controls to download a current customer snapshot or submit a private request for a fuller data copy, correction, account deletion, or review of a shop connection.
A submitted request is a review record—not a claim that deletion, export, or disconnection is already complete. Project Lazon may need to verify identity, separate customer-controlled information from another party’s legitimate records, and preserve limited security or audit evidence. The request history shows its current status.
Archiving a ride removes it from the active garage but preserves its history and allows restoration. Permanently removing an unattached moment capture deletes its private storage object and pending-capture record after confirmation.
Service-record and packet quality review
During early access, authorized Project Lazon operators may review uploaded repair orders, estimates, quotes, invoices, related customer service records, and the saved packet snapshots produced from them. This review is used to verify that records are readable, retained, connected to the intended vehicle or service request, represented accurately in a packet, and useful to the customer and shop.
Opening an original or saved packet through the Founder review workspace creates an access record. Identity documents such as driver licenses, registration, insurance, and other identity sources are excluded from the ordinary service-record review surface and require a separately controlled sensitive-record process.
Project Lazon must separately disclose and review any external AI or model provider before uploaded customer records are sent to that provider. The current review capability does not silently enroll customer files in general-purpose model training.
Optional site analytics
Project Lazon asks before loading Google Analytics. If you allow anonymous analytics, Project Lazon uses a separate Project Lazon property to understand broad traffic, signup, and workflow drop-off. Automatic enhanced measurement and advertising signals are disabled.
Project Lazon's analytics boundary excludes names, email addresses, phone numbers, postal addresses, VINs, plates, service-concern text, form entries, account or vehicle identifiers, document names, invitation or packet tokens, URL queries, and URL fragments. You can change your choice through the Analytics preferences control.