SUBPROCESSORS
Last updated: August 16, 2026
A subprocessor is a third-party service provider we use to help deliver Routerra, and who may process personal data as part of that work. This list covers the subprocessors used for our consumer product. A Teams-specific subprocessor list will be published alongside our Teams Data Processing Agreement.
If we make a material change to this list — adding or replacing a subprocessor — we reflect it on this page. Check back periodically, or contact us at info@routerra.io to be notified of changes.
1. Our subprocessors
| Vendor | Region | Purpose | Data touched |
|---|---|---|---|
| Clerk Inc. | USA | authentication & account management | email, name, OAuth identity, session data |
| Amazon Web Services | USA (us-east-1) | hosting: compute, database, file storage, geocoding/optimization functions; Textract OCR for photo imports | all product data; uploaded images (OCR) |
| OpenAI | USA | parsing imported files: OCR text and spreadsheet rows are processed by OpenAI models to extract stops (API — not used for model training per OpenAI API terms) | text content of user imports (may include recipient names/addresses/phones) |
| Google (Maps Platform) | USA/EU | geocoding, places autocomplete | address strings, coordinates |
| Mapbox | USA | maps, geocoding, directions | address strings, coordinates, map interactions |
| GraphHopper GmbH | Germany | route optimization matrices/directions | coordinates of stops |
| TomTom | Netherlands | live traffic data for routing | route coordinates |
| Lemon Squeezy (a Stripe company, merchant of record) | USA | web payments, checkout, billing portal, invoicing, tax | billing identity and payment details (processed and held by Lemon Squeezy; we never receive card numbers) |
| RevenueCat | USA | mobile subscription management (App Store / Play receipts) | app user id, purchase history, account email and display name |
| PostHog Inc. | USA (us.posthog.com) | product analytics & web error tracking | pseudonymous usage events keyed by account ID; billing events |
| Bugsnag (SmartBear) | USA | mobile crash reporting | crash data + account ID, email, name |
| Functional Software Inc. (Sentry) | EU ingest (de.sentry.io) | web/server error monitoring & consent-gated session replay | error data + account ID; masked replays |
| Tawk.to Inc. | USA | live support chat | chat content; email/name of signed-in users |
| Loops (loops.so) | USA | transactional & product email | email, first/last name, membership type |
| Netlify | USA | web hosting/CDN for routerra.io and app | request metadata |
| Cloudflare | USA/global | DNS/proxy for routerra.io | request metadata |
| Grafana Labs (Grafana Cloud/Loki) | EU/USA | infrastructure logs & metrics | server logs with account IDs |
| Slack | USA | internal error alerting | alert messages (account IDs only — no email addresses) |
| ipapi.co | — | IP-based country lookup for web-app defaults (units/locale) | IP address (processed transiently) |
| Apple / Google | USA | app distribution, in-app purchases, speech-to-text, push/OAuth platform services | per platform terms |
2. International transfers
We're based in Poland (EU) and our product backend is hosted in the USA (AWS us-east-1), so personal data is transferred internationally to deliver Routerra. Each vendor is engaged under a data-processing agreement incorporating the EU Standard Contractual Clauses and/or is certified under the EU-U.S. Data Privacy Framework.
3. Questions & the Privacy Policy
For how we handle personal data more broadly, see our Privacy Policy. For questions about this subprocessors list, email info@routerra.io.