Security

Security & data practices

Everything on this page is true of the product as it runs today. We publish practices when they are verifiable, not in advance — specificity over badges.

Tenancy isolation and access control

Every workspace is isolated at the database row level. Postgres Row-Level Security is enabled across the application schema — 125 active policies layering organization → project → row — so a query in one workspace cannot read another workspace's records, independent of application code.

Inside a workspace, role-based permissions control what each person can see and do. Owners, reps, accountants, and external partners are invited with roles that fit their job, and financial approvals route through sequential sign-off that matches how the owner delegates.

Encryption

Data is encrypted in transit (TLS) and at rest on managed infrastructure. Application traffic is HTTPS-only.

Audit trail

Approvals, budget changes, contracts, and invoices keep who did what, when, and the backup documents behind the decision. Contracts and change orders are signed with built-in e-signatures, and the executed document, its signers, and its timestamps stay attached to the project record.

Your data stays yours

Financials and reports export cleanly, documents remain downloadable, and the record — including its audit history — stays exportable after a project closes out. There is no lock-in mechanism between you and your own paper.

Infrastructure and subprocessors

These vendors process data on our behalf:

SupabaseDatabase, file storage, and authentication (managed Postgres)

VercelWeb application hosting

RailwayAPI hosting and malware scanning of bidding files (self-hosted ClamAV)

Trigger.devBackground jobs — document and drawing processing, report and export generation, and notification delivery; jobs handle uploaded files and project and financial records

AnthropicAI document classification and automatic sheet numbering for drawings — document filenames and drawing title-block images; sheet numbering can be turned off per project

BoldSignElectronic signatures for contracts and change orders — the documents sent for signature, and recipient names and email addresses

MapboxAddress autofill, geocoding, and maps — project, company, and bid package addresses

StripeBilling and payment processing

ResendTransactional email — sign-in, invitation, and notification emails

MicrosoftCompany email (Microsoft 365), including support correspondence, and optional sign-in with a Microsoft work account (Entra ID)

LinearSupport and bug-report tracking — the request text, the requester's name, email, user and workspace IDs, and the page, browser, and operating system it came from

SentryError monitoring, bug and support reports, and session replay for signed-in users — events carry the user's name, email, and workspace; replays record rendered screens, including project and financial figures, while typed input is masked

PostHogProduct usage analytics — sanitized events only; no project documents, financials, or inquiry contact details

CalendlyDemo scheduling — the details you enter when booking a demo

Security reviews and questionnaires

Running a security review, vendor questionnaire, or procurement process? Email michael.eads@siteops360.com — a founder answers directly.

Not yet published here: formal backup and recovery documentation, an incident-response policy, an accessibility conformance statement, and third-party certifications. Sections are added to this page as each becomes verifiable.