How project and account data are handled

1. Information we collect

• Account data such as name, email address, role, organization affiliation, and login activity.
• Project data such as job names, locations, production entries, documents, forms, takeoffs, and uploaded images or PDFs.
• Operational metadata such as timestamps, audit history, device/browser signals, and route usage needed for security and troubleshooting.
• Billing data such as subscription status, seat counts, customer identifiers, and payment status from the payment processor.

2. Why we use the information

• Authenticate users and enforce project and organization access.
• Store and render project records, documents, forms, and reports.
• Support billing, seat management, trial enforcement, and subscription status.
• Monitor reliability, investigate issues, and improve product workflows.
• Protect the service from abuse, fraud, unauthorized access, and storage misuse.

3. Billing and payment handling

Payment details should be processed by the configured payment provider rather than stored directly inside the app. The platform may store provider customer IDs, subscription state, and related billing metadata needed to manage access.

4. Storage and file handling

Uploaded project files may be stored in configured object storage and may be processed to generate previews, signed access URLs, extracted PDF text, document metadata, or suggested workflow records.

These processing steps are intended to support the operational workflow, not to transfer ownership of the underlying documents.

5. Sharing

We do not treat your project records as public content. Data is shared only with the users inside your organization, with service providers supporting storage, authentication, hosting, analytics, or billing, or when legally required.

6. Retention

We retain account, project, and billing records for as long as needed to operate the service, enforce agreements, maintain audit history, resolve disputes, and satisfy legal obligations. Abandoned trial data may be deleted after a grace period.

7. Security

We use reasonable administrative, technical, and organizational safeguards to protect account and project data. No system is perfectly secure, so organizations should still use proper credential management and role assignment.

8. Organization control

If your employer or contractor organization provides your account, that organization may control user access, project visibility, and data retention inside its workspace.

9. Your options

• Ask your organization administrator to update or remove your access.
• Request account or policy support through the support contact used by your organization.
• Use organization controls for user deactivation, seat management, and project membership changes.