Draft — pending counsel review. This document describes what the product actually does so a lawyer can finalize it. Bracketed values (like [Company legal name]) are placeholders. Nothing here is in force yet.

Privacy & Security

Terms & DPA →

Last updated: November 2026

This page explains what personal data Syncing Framework processes, why, the rights you have over it, and how we protect it. Because access is by organization, most personal data in the Service belongs to a customer org that acts as the data Controller; we act as Processor on its behalf under the Data Processing Agreement. For our own limited purposes (account security, billing, and running the Service) we act as an independent controller.

What we collect

  • Account & identity data — name, email, display name, phone (optional), org membership, and role assignments.
  • Customer Data your org enters — customers and contacts, worker records, estimates, proposals, projects, schedules, financial records, and uploaded files. Free-text notes fields may contain whatever your users type.
  • Employment & labor data — roles, job classifications, scheduled and forecasted hours, availability, and pay-rate/cost-rate data your org chooses to store.
  • Special-category data (trade-union membership). Where your org records it for workforce planning, a worker record can carry union-membership status and local. Under GDPR this is a special category of personal data (Article 9) and receives the elevated handling described below; we process it only to provide the Service to your org.
  • Technical & security data — IP address, browser/user-agent, timestamps, and application audit logs, used for security, abuse-prevention, and troubleshooting.
  • Push-notification devices — for each phone or browser you turn push notifications on for: its push address and encryption keys (issued by the browser maker, not your name or email), a device name such as “iPhone · Safari”, and when it was last used and last reached. Used only to deliver the notifications you turned on; removed when you turn them off, sign out of that device, or leave the organization.
  • Support and demo requests — what you send us through the support or demo-request forms: name, email, company, and your message (and, if you were signed in, which account sent it). We use it only to answer you. The IP address and browser details captured with a request are deleted after 90 days; demo requests are deleted after one year and support requests after two.
  • Billing data — handled by our payment processor (Stripe). We store only billing name/email/address, tax ID, card brand, and last four digits; full card numbers are entered directly on Stripe's hosted pages and never touch our systems.

We do not collect government IDs, dates of birth, demographic categories (race, ethnicity, gender), health or biometric data, or bank-account details. Aside from union membership above, the Service collects no other special category of data.

How we use it

To provide and support the Service, authenticate users, secure the platform, process subscription payments, keep audit and business records, prevent abuse and fraud, and communicate with you about your account. All email we send is transactional (invitations, notifications you've enabled, and proposals you choose to send) — we do not send marketing email. Phone and browser push notifications go only to devices you turn them on for, and are never marketing. We do not use Customer Data to train third-party AI models.

Legal bases (GDPR)

Where the GDPR applies, we rely on: performance of a contract (providing the Service you or your org requested); our legitimate interests (securing the platform, preventing abuse, and maintaining audit records), balanced against your rights; and, for special-category union data, the condition applicable to your org's employment-law obligations as Controller. Your org, as employer/Controller, is responsible for having a lawful basis for the Customer Data it enters.

We do not sell or share your data

We do not sell personal information, and we do not share it for cross-context behavioral advertising or targeted advertising. We run no advertising or analytics trackers, so there is nothing to opt out of and no Global Privacy Control signal to honor for advertising purposes. Your Customer Data is used only to provide the Service to your org.

Who we share data with

We share personal data only with the sub-processors that run the Service on our behalf — hosting, transactional email, bot protection, payments, AI features, address geocoding, drive-time routing, map tiles, push-notification delivery, and the WA sales-tax lookup. Each is listed, with its purpose and location, in the Sub-processors table of the DPA. We remain responsible for their performance and enter data-processing agreements with them where the provider offers one; the browser makers’ push relays (Apple, Google, Mozilla, Microsoft) carry only end-to-end encrypted notifications under their standard terms. Integrations your organization connects (payroll, your own AI provider) are listed separately and governed by your agreement with that provider. We may also disclose data where required by law or to protect the rights, safety, and security of our users and the Service.

International data transfers

The Service is operated with cloud infrastructure that may process data outside your country, including in the United States. Where personal data is transferred out of the EEA, the UK, or Switzerland, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses (and the UK Addendum) with our sub-processors. The hosting region for your org's data at rest is [project region].

Your privacy rights

Depending on where you live, you may have the right to access, correct, delete, restrict, or port your personal data, and to object to certain processing. If you are a California resident, you may request to know the categories and specific pieces of personal information we hold, request deletion, and are entitled to non-discrimination for exercising these rights — and, as stated above, we do not sell or share your personal information.

Because most personal data sits inside a customer org, we will refer a request to that org as Controller unless we're legally required to respond directly; where we are the controller (account and billing data) we respond ourselves. We act on verified requests within the applicable statutory response window. To exercise a right, contact [privacy@company.example].

Retention

We keep Customer Data for as long as your org's account is active, then per the deletion terms in the DPA. Billing and tax records are retained as required by law. Application audit logs and other transient records follow tightened, time-based retention windows, after which they are purged.

Cookies & local storage

We use only what the app needs to function: an authentication session (stored in your browser's local storage) and functional preferences such as which table columns you've locked or your sidebar layout. On the sign-in page only, our bot-protection provider sets a strictly-necessary security cookie. Because everything we store is strictly necessary or a functional preference, we do not run third-party advertising or cross-site tracking cookies and do not display a cookie-consent banner.

Children's privacy

The Service is a business tool intended for use by construction organizations and their authorized personnel. It is not directed to children, and we do not knowingly collect personal data from anyone under 16. If you believe a child has provided us personal data, contact us and we will delete it.


Security

Security isn't a marketing line here — these are controls actually in place in the product today.

  • Tenant isolation. Every table is protected by PostgreSQL Row-Level Security scoped to the caller's organization. A cross-tenant test suite runs in CI, so isolation is verified on every change — not assumed.
  • Authentication & access control. Authentication is managed by Supabase Auth; passwords are stored encrypted, never in plaintext. Access within an org is role-based and enforced in the database. Optional Cloudflare Turnstile bot protection guards sign-in, and sensitive endpoints are rate-limited.
  • Encryption. Data is encrypted in transit with TLS (with HSTS enforced) and encrypted at rest by our hosting provider. A strict Content-Security-Policy limits what the app is allowed to load and talk to.
  • Least privilege. Privileged operations run in server-side functions with per-action authorization checks; privileged database functions revoke execution from the public role.
  • Audit logging. An application audit trail records record changes with the actor and timestamp, with time-based retention cleanup.
  • Backups & recovery. Our hosting provider maintains encrypted, point-in-time database backups within a defined retention window to support recovery.
  • Payment data. Card details are entered directly on our payment processor's hosted pages (PCI-DSS SAQ-A); we store only tokenized references and the card brand and last four digits, never full card numbers.
  • Breach notification. If a personal-data breach affecting Customer Data occurs, we notify affected customer orgs without undue delay, as set out in the DPA.

Responsible disclosure

We welcome reports from security researchers. If you believe you've found a vulnerability, please report it to [security@company.example] with enough detail to reproduce it, and give us a reasonable opportunity to remediate before public disclosure. We will not pursue action against good-faith research that respects user privacy and avoids service disruption.

Contact

For privacy requests and questions, contact [privacy@company.example]. For security concerns, contact [security@company.example]. Postal address and, where required, our EU/UK representative will be listed here: [Company legal name and address].