Subprocessor List

Last Updated: August 28, 2026

This page lists the key subprocessors and service providers that Ontario Engineering Solutions Inc., doing business as FieldWorks, may use to deliver the FieldWorks Service. Actual use may vary by environment, feature set, and customer configuration. Some services load only when a customer or user enables an optional feature, and some load only after a website visitor consents to analytics cookies.

Core Infrastructure and Platform

| Provider | Purpose | Data Categories | Location / Transfer Notes | | --- | --- | --- | --- | | Vercel | Application hosting, deployment, edge network, and consent-gated product analytics and performance measurement | IP address, request metadata, usage and performance telemetry | Vendor may process data in multiple jurisdictions under its legal and transfer terms | | Supabase | Hosted PostgreSQL database and S3-compatible object storage for uploaded files, photos, audio, and documents | account data, organization data, project and workflow records, uploaded files and attachments, audit data, metadata | Database infrastructure verified in Canada for the current environment; vendor operations may involve additional jurisdictions under vendor transfer terms | | Sentry | Error monitoring and application observability (configured not to capture personal information by default) | error events, request metadata, operational telemetry, limited user context if configured | Vendor may process data in multiple jurisdictions under its legal terms |

Payments

| Provider | Purpose | Data Categories | Location / Transfer Notes | | --- | --- | --- | --- | | Stripe | Subscriptions, checkout, invoicing, tax calculation, refunds, customer portal, and billing operations | billing contacts, subscription and invoice metadata, transaction and refund records | Stripe may process data in multiple jurisdictions under its legal and transfer terms. FieldWorks does not store full payment card numbers |

Communications

| Provider | Purpose | Data Categories | Location / Transfer Notes | | --- | --- | --- | --- | | Resend | Transactional and marketing email delivery | recipient email addresses, email content, delivery metadata | Vendor may process data in the United States and other regions under its legal terms |

| Provider | Purpose | Data Categories | Location / Transfer Notes | | --- | --- | --- | --- | | Google (Google Analytics 4 and Google Ads) | Website analytics and advertising conversion measurement, loaded only when a visitor consents to all cookies | online identifiers, device and browser data, page and event data, campaign attribution parameters | Google may process data in the United States and other jurisdictions under its legal and transfer terms |

Vercel Analytics is also gated behind "All" cookie consent and is provided by Vercel (listed above under Core Infrastructure). Vercel Speed Insights (also provided by Vercel) is cookieless, identifier-free performance measurement and runs independently of consent.

Authentication (optional)

| Provider | Purpose | Data Categories | Location / Transfer Notes | | --- | --- | --- | --- | | Microsoft | Optional Microsoft (Entra / Azure AD) single sign-on | authentication identifiers and account profile details returned by Microsoft | Only applies if a user chooses Microsoft sign-in | | Google | Optional Google single sign-on (separate from analytics above) | authentication identifiers and account profile details returned by Google | Only applies if a user chooses Google sign-in |

Mapping and Location (optional)

| Provider | Purpose | Data Categories | Location / Transfer Notes | | --- | --- | --- | --- | | Esri / ArcGIS Location Platform | Optional map 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 | | MapLibre demo tile service (OpenStreetMap-derived basemaps) | Fallback map basemap tiles in environments where ArcGIS basemaps are not configured | IP address and tile request metadata sent to the tile host when a map loads | Publicly hosted map tile service; requests are made directly from the user's browser |

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, payment-network, or advertising obligations under their own terms.
Optional providers (single sign-on, ArcGIS, and analytics) engage only when a customer or user enables the related feature or, for analytics, consents to all cookies.
FieldWorks may update this list from time to time as vendors or product functionality change. Where required by contract, business customers receive advance notice of new subprocessors as described in our Data Processing Addendum.

Questions

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