Home/Privacy

LAST UPDATED • AUGUST 22, 2026

Privacy by project role.

This first-version notice explains the platform design and must receive legal and operational review before public launch.

Information collected

Contact details, organization and member records, locations, vehicles, quote inputs, projects, files, proof comments and approvals, messages, milestones, invoices/payment-status records, delivery and installation information, preferences and audit events.

Why it is used

To respond, scope, estimate, quote, design, proof, produce, deliver, install, support, document, secure and enable reorders for requested work.

Production network

Authorized partners may receive only the specifications, approved files, timing, assignment details and relay information needed for assigned work. They do not automatically receive customer prices, other bids, margins, unrelated customers or owner notes.

Private object storage

Customer files are stored in private object storage with relational ownership and audience metadata. Access occurs through authorized server routes rather than public object URLs.

PWA + offline data

Only selected public resources enter public offline caches. Device-only notes may use browser storage. Private projects, proofs, messages, partner costs and internal records are not added to the public cache.

Permissions

Camera, location, notification, wake-lock, fullscreen and share capabilities are requested or activated only after user action and remain subject to browser and operating-system controls.

Security + retention

Role checks, membership checks, authorized object access, mutation validation and audit events support security. Retention schedules, incident response, subprocessors, legal bases and verified business contact details must be finalized before public launch.

Your choices

Request access, correction, export or deletion where applicable; manage device permissions; clear public offline packs and device-only notes; and choose notification preferences after activation.