1
Scope
This page lists the third-party services currently evidenced in the Field Mox website codebase. The repository is a static Astro site and does not contain the application backend or a contractual vendor inventory, so it cannot by itself verify every subprocessor used by the Field Mox product. We distinguish website providers from customer-data subprocessors and do not claim that a provider processes data the website does not send to it.
2
Providers evidenced in the website code
| Provider | Purpose | Information potentially received | Classification |
|---|---|---|---|
| Vercel | Hosting, deployment, CDN, and delivery of the static Field Mox website | Website requests and standard hosting/security logs; this repository does not expose application-database credentials or customer records | Website infrastructure provider; no application-data subprocessor relationship is verified by this repository |
| Featurebase | Support, feedback, and feature requests | Details a visitor chooses to submit in the linked support portal | Linked external service; no application-data subprocessor relationship is verified by this repository |
3
Other website services
These services are referenced by the public website but are not treated here as subprocessors of Field Mox customer application data:
- Google Tag Manager: website tag delivery and measurement configuration. The data handled depends on the tags configured in the GTM container.
- YouTube: embedded product videos; loading an embed can send standard browser and viewing data to YouTube.
- Google Fonts: web-font delivery from Google’s font domains.
- Euverify: the GDPR badge verification link. The badge image is hosted locally in Field Mox; verification opens Euverify in a separate tab.
4
Changes and questions
The services used by Field Mox may change as the website and product evolve. We update this page when the provider scope materially changes. For questions about subprocessors, contact support@heffl.com.