Legal
Sub-Processor Register
Last updated · Version subprocessors-2026-10-28
About this register
To run Smart Site Plan we rely on a small set of trusted third-party service providers ("sub-processors") that may process personal data on our behalf. We require each of them to protect personal data to a standard consistent with our Data Processing Agreement and to use it only to provide their service to us. This page is the current list.
Most of these providers process data in the United States. Where a provider receives personal data from the European Economic Area, the United Kingdom, or Switzerland, the transfer is covered by the safeguards described in our DPA, such as the Standard Contractual Clauses (with the UK and Swiss adaptations) or the EU-US Data Privacy Framework where the provider is certified.
Core providers
These providers are part of the standard operation of the Service for every customer.
| Provider | Purpose | Data categories | Location |
|---|---|---|---|
| Railway | Primary cloud hosting for the API and managed databases (PostgreSQL/PostGIS, MongoDB, Redis). | All platform data: account, project, spatial, GPS, and usage records. | United States |
| Vercel | Hosting and global edge delivery for the web application, including the approximate location (from IP address) used to set the starting map view and the privacy regime of a visit. | Request and log metadata, including IP address and the approximate location derived from it. | United States |
| Cloudflare | Object storage (R2) for uploaded files and exports, plus CDN, DDoS protection, and bot mitigation (Turnstile). | Uploaded files and images, export bundles, IP address. | United States |
| Stripe | Payment processing and subscription billing. | Name, email, and billing details. We never store full card numbers. | United States |
| Resend | Delivery of transactional and account email (verification, security, billing, invitations, alerts, and product updates you have not opted out of). | Name and email address. | United States |
| Axiom | Structured server-log ingestion and retention, used to operate, debug, and secure the Service. | Server log data, which may include IP address and account identifiers. Sensitive fields are masked or scrubbed before ingestion. | United States |
| Better Stack | Uptime monitoring: our servers send a periodic heartbeat while the platform is healthy, so an outage pages us. | No personal data. The heartbeat is a bare request from our servers and carries no user, account, or request content. | United States |
Feature-specific providers
These providers are engaged only when you use the related feature or enable the related option, so data flows to them only in that context.
| Provider | Purpose | Data categories | Location |
|---|---|---|---|
| ATTOM Data Solutions | Property and parcel data lookups. | The address or coordinates you query. No account identifiers are sent. | United States |
| Twilio | SMS delivery for SMS-based two-factor authentication. | Phone number, only if you enable SMS two-factor authentication. | United States |
| AI processing through the Gemini API for Site Plan AI (turns a site boundary and development program into a dimensioned concept site plan); Ask anything (reads what you ask for, finds and reviews the public government datasets that answer it, and carries out the request); Ask anything image tracing and fitting (traces what a project image shows into map features and lines an image up with the aerial map); Plan digitizing (reads utility plans into map layers of pipes and structures); Open data catalog labeling (labels and checks public government map layers in our open data catalog ahead of any request); Internal product analytics (summarizes how the product is used for our own team). Also optional OAuth sign-in and Search Console reporting for our public pages. | For Site Plan AI: a numeric summary of the site geometry, the development program, any submittal requirements you paste in, and any site or plan images, aerial captures, or map captures you provide or ask it to read. The parcel street address and identifier (APN) are left out of these prompts. For Ask anything: the text of your request, the earlier requests in the same conversation, the places you name, the names of your project's layers and groups when a request names one, and the names, fields, and sample records of the public datasets it considers. For Ask anything image tracing and fitting: the project image you ask about (for example a drone photo, a site photo, or a plan picture), Esri aerial imagery of the same ground, and the outlines already traced on it. For Plan digitizing: the pages of the plans you send (PDF pages or pictures, sent as images), including whatever the sheets print, such as project names, addresses, engineers, and dates. For Open data catalog labeling: the listings, field names, and sample records of public government map layers. No customer content or account data is sent. For Internal product analytics: aggregated usage statistics: counts and revenue totals by feature, page, journey, plan, country, and category, including the categories of searches that found nothing. Groups of fewer than five people are removed, and account, visitor, and project identifiers, email addresses, names, network addresses, and anything a person typed (searches and feedback) are stripped before anything is sent. No account identifiers are sent with AI requests. Images are never used to identify people. This content is sent to Google through the Gemini API and processed under Google's Gemini API terms, which allow Google to retain it for a limited period to detect abuse and policy violations. For sign-in: email and basic profile. | United States | |
| US Census Bureau (Geocoder) | Locating street addresses to coordinates for results we keep, such as the place an Ask anything request is about or where an imported plan is placed. | The address strings you ask us to locate. No account identifiers are sent. | United States |
| Photon (komoot) | Reverse-geocoding GPS coordinates to place names when you run a live location tracker. | The GPS coordinates recorded by a live location tracker you start. No account identifiers are sent. | European Union (Germany) |
| Esri | Basemap imagery, public open-data feature services, and address geocoding and search. | Map view requests, and the address strings or coordinates you geocode or search. No account identifiers are sent. | United States |
| OSRM (project-osrm.org) | Route planning between the stops you choose in the route planner. | The waypoint coordinates on a route you build. No account identifiers are sent. | European Union |
| Anthropic | AI analysis (Claude) for document and image analysis and assistant features. These features are not currently enabled, so no data is sent to Anthropic today; it stays listed for transparency and applies when they are turned on. | When enabled: the content you submit for analysis, such as documents and images, and any location data embedded in them. | United States |
Map and data providers
The Service also displays basemaps and open and public data from providers such as map-tile and government GIS services. Map and tile requests are not tied to your account identity, and open or public data you discover is owned by its provider and subject to that provider's own terms and attribution requirements.
Our AI provider develops the models behind our third-party AI features and publishes its own disclosures, including about the data used to train those models, on its website. We do not train models on your content. This content is sent to Google through the Gemini API and processed under Google's Gemini API terms, which allow Google to retain it for a limited period to detect abuse and policy violations. What Google may do with that content is governed by those terms, as described in our Privacy Policy. Images are never used to identify people. Some AI runs on our own servers rather than a provider: the image-classification model that ranks Open Data search results evaluates rendered previews of public map layers and sends nothing to a third party.
Changes and notice
We update this register when our sub-processors change. Customers under a Data Processing Agreement may request advance notice of new sub-processors and can object on reasonable data-protection grounds as described there. Questions? Email privacy@smartsiteplan.com.