Sub-Processors

Last reviewed: 2026-05-17 · Review cadence: every 6 months

A sub-processor is a third-party service that processes personal data on behalf of MintGrid for our customers. This list excludes purely internal operational tools that never touch customer data. We notify customer admins by email at least 30 days before adding a new sub-processor that handles personal data, changing an existing sub-processor's data-handling role, or moving customer data to a new geographic region. See our Privacy Notice for the full picture of how we use this data.

Active sub-processors

Sub-processorRoleData it may seeRegionDPA
SupabaseDatabase, authentication, object storageIdentity, contact, project/geo, operational dataUS (default region)DPA
VercelApplication hosting, edge runtimeIdentity, contact, project/geo, operational data (in transit, logs)US + global edgeDPA
GroqLLM inference for the research pipelineProject/geo, operational data (prompt contents)USDPA
ResendTransactional email (authentication, invites, notifications)IdentityUS + EU optionsDPA
SentryError and performance monitoringIdentity (only if present in a stack trace; PII scrubbing enabled)US + EU optionsDPA
MapTilerMap tilesNone (anonymous tile requests)EU/CHDPA
GitHubSource control, CIIdentity (MintGrid workforce accounts only — not customer data)US + globalCovered by Microsoft's enterprise DPA

Industry data providers

These providers return public-record or commercial registry data into MintGrid on our customers' behalf — MintGrid does not send personal data to them, so they are tracked here for transparency rather than as sub-processors.

ProviderRoleNotes
Warren GroupMassachusetts deed / registry dataPublic records, commercial license
DataTreeNational deed / registry dataPublic records, commercial license
MassGIS / state OPM CAMA (CT)State GIS / parcel dataPublic records, free public API

Questions about this list? Email info@themintgrid.com.