Legal
Sub-processors
Last updated: October 6, 2026
SiteSui LLC runs Sitesui on a small number of other companies’ services. This page names every one of them that can touch data a customer puts into Sitesui, says what it does, what personal data it can see, and where it processes. It is the list the Data Processing Addendum refers to, and it is kept in step with the code rather than written once and forgotten.
The list
Each of these processes personal data on a customer’s behalf, under a written agreement with obligations equivalent to our own. Rows marked optional only run while that capability is switched on — by us, when the provider’s key is configured, and for resident-report triage also by each workspace, where it is on until an owner or admin turns it off; with it off, nothing reaches that company at all.
Vercel, Inc.
- What it does for us
- Application hosting, the edge network that serves every page, and the privacy-preserving counts behind our own page analytics.
- What personal data it can see
- Everything a request carries while it is being served — the signed-in person's name and email, the inspection, report or work order on screen, and the IP address the connection comes from. Our own count of public-page visits records the page, the referring site, the country and city and the device type against a random id; it stores no IP address.
- Where it processes
- United States
Supabase, Inc.
- What it does for us
- The database of record, sign-in and session handling, and the private buckets holding photos, video, voice notes, signatures and documents.
- What personal data it can see
- All customer content and account data: people, properties, inspections, ratings, notes, media, reports, work orders, vendors and resident reports, plus email addresses and password hashes for sign-in.
- Where it processes
- United States — PostgreSQL on AWS in us-west-2
Stripe, Inc.
- What it does for us
- Subscriptions, checkout and invoices.
- What personal data it can see
- The billing contact's name and email, the workspace name, and the card details the customer types into Stripe's own form. Card numbers never reach Sitesui.
- Where it processes
- United States
Resend, Inc.
- What it does for us
- Sending every email the product sends — verification, report and signing links, work-order notices, lifecycle mail and founder notes — and receiving replies so they become tickets.
- What personal data it can see
- Recipient name and email address, the subject and full body of the message (which can include a property address or a report link), and delivery, open and click events.
- Where it processes
- United States
Twilio, Inc.
- What it does for us
- Text messages to vendors, staff and pros who opted in by replying YES, and the phone line: calls to our number and the messages callers leave.
- What personal data it can see
- The mobile number, the text of the message (a job reference and a link), and the carrier's delivery status; for a call, the caller's number, the time and length of the call, and the recording of a message left.
- Where it processes
- United States
Cloudflare, Inc.
- What it does for us
- The second copy: a nightly copy of the database and every stored file in R2 object storage, at a different company from the one holding the originals. The copy is encrypted at rest by Cloudflare's storage, not separately by us. Backup copies expire after 35 days.
- What personal data it can see
- A copy of everything in the database and in storage, as it stood when the copy was taken.
- Where it processes
- We set no jurisdiction on the bucket, so Cloudflare places the objects on its own network. Ask and we will confirm where it sits today.
GitHub, Inc.
- What it does for us
- Source control and the scheduled job that runs the backup.
- What personal data it can see
- The backup runs on a GitHub-hosted machine, so the database dump and the files pass through it while they are being copied. Nothing is kept there when the run ends, and no customer data is in the source code.
- Where it processes
- The runner's region is GitHub's to choose; we do not set it.
X.AI LLC (xAI)optional
- What it does for us
- Optional model calls (Grok): triage of a resident's report into a trade and an urgency for a person to confirm, which is on for a workspace until an owner or admin turns it off under Settings → Workspace; a summary of feedback a Sitesui user sends us about the app; the three-sentence summary at the top of our own end-of-day business brief; and drafting our own blog posts and help answers.
- What personal data it can see
- The text of a resident's report — what they wrote, where they said it was, how urgent they said it is — with no name, email, photo or account identifier, and nothing at all from a workspace that turned triage off. For app feedback a user chose to send us: their message and the screenshot of the part of the page they pointed at. For the end-of-day brief: the day's counts, and for each new or changed workspace its name, its trade, where the signup came from (referring site, city and country), the device type, and plan changes with their amounts — no person's name, no email address, no report and no photo. Nothing a model returns acts on its own.
- Where it processes
- United States
Anthropic, PBCoptional
- What it does for us
- Fallback only: the same model calls — resident-report triage where the workspace has it on, app-feedback summaries, the end-of-day brief, and our own blog drafting — go to Anthropic's Claude when no xAI key is configured.
- What personal data it can see
- The same as xAI's row, and only while xAI is not configured.
- Where it processes
- United States
OpenAI, L.L.C.optional
- What it does for us
- Turning a voice note into words, and only when the inspector's own browser could not do it and the key is configured.
- What personal data it can see
- The audio clip itself, which is whatever the inspector said while walking. The words come back and are stored with the note; nothing else is sent.
- Where it processes
- United States
Mapbox, Inc.optional
- What it does for us
- Turning a property address into a map pin, and suggesting addresses as they are typed.
- What personal data it can see
- The address text or the coordinates. Never a name, an account or anything about the person typing.
- Where it processes
- United States
Komoot GmbH (Photon)
- What it does for us
- The free address lookup used when no Mapbox token is configured, built on OpenStreetMap data.
- What personal data it can see
- The address text or the coordinates. Never a name, an account or anything about the person typing.
- Where it processes
- Komoot is a German company; its service is public and we do not control which of its servers answers.
Where a region is not named
Our commitment is in DPA §9: the Service is operated from the United States, and customers subject to GDPR or UK GDPR are covered by the Standard Contractual Clauses there. Where the rows above name a region, that is the region the service is configured to use, and the database of record — every inspection, photo and report — is in one named United States region.
Two places we have not yet pinned to a region ourselves, and would rather say so than imply otherwise: the backup bucket at Cloudflare carries no jurisdiction restriction, and the machine that runs the nightly backup job is chosen by the host. Both hold a copy, never the live records. Pinning them is on our list; if your review needs it done before you sign, say so and we will do it and confirm it in writing. Vercel’s edge network also terminates a request close to the visitor, wherever the visitor is.
What is deliberately not on the list
- Browser push services (Apple, Google, Mozilla) — When a staff member turns on browser notifications, the alert goes to whichever push service their browser issued an address for — a short title and line such as "New inspection assigned", never a report, a photo or a resident's details. They are the person's own browser vendor, not a provider we chose.
- Unsplash — Stock photography for our own blog posts. It never receives anything of a customer's.
- Advertising and tracking networks — There are none. No advertising pixel, no third-party analytics script, and no customer data is sold or shared for advertising.
- AI model training — Nothing a customer puts into Sitesui is used to train a model, by us or by a provider.
Changes, and being told about them
This page is updated when the list changes, and the date at the top moves with it. Under DPA §2 we give at least 30 days’ notice by email before a new sub-processor starts processing customer personal data; a customer may object in writing and, if the objection cannot be resolved, terminate without penalty.
To be on that notice list, email hello@sitesui.app and say which address should receive it. You can also ask for the DPA signed, or for anything on this page in the form your own questionnaire wants it — the standard answers are already published, and how the data is protected is set out in full.
Questions about this policy? Email hello@sitesui.app and we'll get you a clear answer.