Service Providers and Subprocessors

Classification warning

Provider contractual roles, account settings, processing locations, subprocessors and transfer mechanisms require lawyer and provider-account verification. Inclusion here does not by itself classify every provider as a processor.

Processors/subprocessors — draft classification

• Vercel — hosting, deployment, application delivery and runtime services. Active. General locations and contractual role to verify.
• Supabase/PostgreSQL — primary application database; primary project region configured in Zurich. Active. Support, backup, subprocessor and transfer details to verify.
• Resend — transactional email when configured. Active where production configuration enables it. Contractual role and locations to verify.

Other third-party providers or recipients

• Google Maps Platform — Routes, Geocoding, Places, Weather and Google Maps directions links. Active features. Google is not automatically labelled a subprocessor; role and transfer treatment require review.

Planned but inactive

• Stripe — proposed future payment provider. Not currently active; no card-payment flow is connected.

Data categories

Depending on the feature, providers may receive account/contact routing information, transactional email content, technical request metadata, addresses/place identifiers, coordinates, route inputs or forecast target information. Provider keys remain server-side.

Last reviewed

Source review: 18 August 2026. Contract and provider-account verification: pending.