Subprocessors
Effective: November 10, 2026 · Version 1.1
These are the companies that process personal data for us to provide Construction Company Software. This list is Annex 3 of our Data Processing Addendum, and the Privacy Policy refers to it too.
1. Current subprocessors
| Subprocessor | What it does for us | Personal data | Where | When used |
|---|---|---|---|---|
| Vercel Inc. | Hosting of the website and the app (servers, content delivery, background job endpoint) | All data the app handles passes through it; request logs with IP addresses | United States (app servers in the US East region by default); website content cached on a global network | Always |
| Neon (Postgres database) | Database that stores accounts and all Customer Data except uploaded files | All account data and Customer Data (projects, contacts, phone numbers, messages, consent records, logs) | United States (AWS US East, N. Virginia) | Always |
| Cloudflare, Inc. (R2 storage) | Storage of uploaded files | Photos, plans, documents and other files uploaded by users, subs and clients (including any personal data in them) | United States (Cloudflare R2, Eastern North America location) | Always |
| Resend | Sending email (sign-in links, notifications to subs and clients, invoices, billing notices) | Recipient email addresses, names, email content | United States | Always |
| Stripe (Stripe Payments Europe, Ltd., Ireland, and its affiliate Stripe, Inc., United States) | Subscription billing for our customers | Billing contact name and email, company name, card details (entered directly with Stripe; we never see full card numbers), payment history | Ireland and United States | Always |
| Anthropic (Anthropic Ireland, Limited, and Anthropic, PBC, United States) | AI features (Claude models) | Only what an AI request needs: for example the project's schedule, sub and company names in a schedule review, a photo being tagged, or a document you asked about | United States | On plans that include AI, unless an admin turns AI off (Settings → AI & privacy) |
| Twilio Inc. | Sending and receiving text messages (SMS) | Mobile phone numbers, message content, delivery status | United States | When texting is live (it starts once our toll-free number is verified) |
| Functional Software, Inc. (Sentry) | Error monitoring | Error reports with a user ID and company ID; we strip names, email addresses, phone numbers, message text and link tokens before sending | United States | When error monitoring is switched on |
| Crisp IM SAS (France) | Live chat on our website and in the app | What you type in the chat, your name and email if you give them (or, when signed in, your name, email, company and plan), browser and device details, approximate location from the IP address | European Union | Always |
| Mixpanel, Inc. | Product analytics (which setup steps companies complete) | User ID, company ID, event name (for example "schedule sent") and a few counts; no IP address, no names, no content, no cookies | United States | When product analytics is switched on |
| Upstash, Inc. | Shared rate-limit counters that protect sign-in and other endpoints from abuse | IP addresses and email addresses used as short-lived counter keys (minutes to a day) | United States | When shared rate limiting is switched on |
| Google LLC (Google Workspace) | Our own email inboxes (support@, privacy@, admin@ and the other addresses on our domain) | Whatever you send us by email: names, email addresses, message content and attachments | United States (Google may process data in other countries where it has facilities) | Always |
2. Services that are not our subprocessors
- Services a customer chooses to connect, such as Google (sign-in and Calendar), Microsoft (Outlook calendar), Intuit (QuickBooks Online), Zapier, webhooks, API clients and AI assistants. Data goes to them on the customer's instruction, under the customer's own agreement with them.
- Mobile carriers, email providers and browser push services (for example Google, Apple, Mozilla or Microsoft for web push), which deliver messages to their recipients. Push notification content is encrypted for the recipient's browser.
- The US National Weather Service, which receives a job site's map coordinates (no names) to return a forecast.
- Stripe, for its own purposes (such as fraud prevention), as an independent controller, and a customer's own Stripe account for online invoice payments.
- An external scheduler that calls a protected address on our servers to start background jobs; it receives no personal data.
3. Transfers outside Europe
We are based in the Netherlands. For subprocessors outside the European Economic Area, we rely on the EU–US Data Privacy Framework where the vendor is certified under it, and otherwise on the European Commission's Standard Contractual Clauses in the vendor's data processing terms. Details are in the DPA.
4. How we announce changes
At least 30 days before a new subprocessor starts processing customer personal data, we update this page (with a new version number and entry in the version history below) and email the owner of every customer account. Customers can object as described in section 5 of the DPA. Anyone else who wants to be told about changes can email privacy@construction-company-software.com.
Version history
- Version 1.0 (November 10, 2026): First published list.
- Version 1.1 (November 15, 2026): Added Crisp (live chat).
Earlier versions are available on request from admin@construction-company-software.com.