FieldWorksHQ

Legal

Subprocessor List

Last Updated: March 26, 2026

This page lists key subprocessors and service providers that FieldWorks may use to deliver the Service. Actual use may vary by environment, feature set, and customer configuration.

Core Service Providers

| Provider | Purpose | Data Categories | Transfer / Location Notes | | --- | --- | --- | --- | | Supabase | Hosted PostgreSQL database infrastructure and related platform services | account data, organization data, project data, audit data, metadata | Current preview environment verified in Canada; vendor operations may involve additional jurisdictions under vendor transfer terms | | Stripe | subscriptions, invoicing, refunds, checkout, customer portal, billing operations | billing contacts, subscription metadata, invoice metadata, transaction records | Stripe may process data in multiple jurisdictions under its legal and transfer terms | | Resend | transactional email delivery | recipient email addresses, email content, delivery metadata | Vendor may process data in the United States and other regions under its legal terms | | AWS / S3-compatible storage provider | file and document storage | uploaded files, object keys, attachment metadata | Storage location depends on configured bucket and provider setup | | Vercel | application hosting, deployment infrastructure, analytics and performance tooling | IP address, request metadata, usage telemetry, performance analytics | Vendor may process data in multiple jurisdictions under its legal terms | | Sentry | error monitoring and application observability | error events, request metadata, operational telemetry, limited user context if configured | Vendor may process data in multiple jurisdictions under its legal terms | | Microsoft | optional OAuth authentication | authentication identifiers, account profile details returned by Microsoft | Only applies if Customer uses Microsoft sign-in | | Esri / ArcGIS Location Platform | optional basemaps, geocoding, and user-linked ArcGIS Online overlay layers for Project Map View | map request metadata, geocoding queries, ArcGIS account identifiers, customer-selected layer metadata | Only applies when Map View or ArcGIS Online linking is used; linked overlay feature data is requested directly from Esri using the authenticated user's token and is not cached by FieldWorks |

Notes

  • FieldWorks shares only the information reasonably necessary for each provider to perform its service.
  • Some providers act as processors for FieldWorks. Others may independently act as controllers for certain compliance, fraud-prevention, or payment-network obligations under their own terms.
  • FieldWorks may update this list from time to time as vendors or product functionality change.

Questions

If you need current information about subprocessors or data processing terms, contact support@fieldworkshq.com.