FieldSignal Sub-processors

Fieldsignal LLC uses the following third-party sub-processors to provide the FieldSignal service. Each processes personal data only to deliver its function, under a data processing agreement with us.

A row marked not yet enabled is listed ahead of activation, so that this page never lags the Privacy Policy that names the provider. Nothing is sent to a provider marked that way until this page records that it has been switched on. The agreement above is already in place for every provider listed, whether or not it is enabled.

For Team customers on our Data Processing Agreement, we will give at least 30 days' notice by email to the account owner before adding a new sub-processor, and will update this page at the same time.

Sub-processor	Purpose	Location of processing
Supabase (on Amazon Web Services)	Database hosting, authentication, and file storage for app data (notes, photos, checklists, team data)	United States (AWS US West, Oregon)
Anthropic	AI report generation — field data you include in a report request is sent to Anthropic's Claude API to produce the report	United States
PowerSync	Offline-first data synchronization between the app and our database	`[CONFIRM REGION]`
RevenueCat	In-app subscription management and entitlement status	United States
Stripe	Payment processing for team plans billed directly by Fieldsignal LLC	United States
Apple / Google	App distribution and in-app purchase billing for individual plans (independent controllers for payment data)	Global
Mapbox	Map display in the app, and the map snapshot captured on your device that appears as a figure in a generated report. The separately generated map image in reports is produced by Microsoft Azure Maps, listed below. We have turned off the Mapbox SDK's analytics collection, so it does not send your device's location or a session identifier for Mapbox's own analytics — see Mapbox's privacy notice	United States
Microsoft Azure Maps (Microsoft Corporation)	Producing the map image that appears in generated PDF and Word reports. Our servers send Azure the coordinates of the area shown, the outlines and markers to draw on it, and the text of any labels you placed on the map; the app itself does not communicate with Azure. In use since 19 September 2026: reports generated from that date carry an Azure map image, and the map image is produced by Azure from the data described above	European Union. Processing is pinned to Azure's North Europe region — the only region enabled on our account — so report map requests are processed in the EU
Resend	Transactional and product email delivery	United States
Expo (EAS)	App build and update delivery infrastructure	United States
Sentry	Error and crash reporting (may include device identifiers and diagnostic data)	United States
Vercel	Marketing website hosting (fieldsignal.com)	United States
Prighter Group (in the United Kingdom, Prighter Ltd)	Our representative in the European Union under GDPR Article 27, and in the United Kingdom under UK GDPR Article 27. Prighter operates the request portal named in section 1 of our Privacy Policy: where you use it, Prighter receives your request and the personal information in it, holds it, and passes it to us	`[CONFIRM — expected European Union and United Kingdom]`
Plausible Analytics (Plausible Insights OÜ, Estonia)	Website analytics for fieldsignal.com — cookieless and aggregate, with no cookies, no cross-site tracking and no individual profiles. Not yet enabled: the account is open and the agreement is in place, but the script is switched off and nothing is being collected. When it is switched on, this page is updated and the date above changes	European Union — Germany. No visitor data is transferred outside the EU

Weather data is retrieved from public weather services using approximate coordinates; no account information is sent to them.

Questions: info@fieldsignal.com