Subprocessor register
Providers that help run Trackely.
Last updated
4 November 2026
Trackely Ltd uses only the providers needed for the contracted deployment and enabled features. “Where enabled” means the provider does not receive a customer's data merely because it appears in this register. Customer-configured WMS, ERP, spreadsheet, webhook and API destinations are generally the Customer's own providers, not Trackely subprocessors.
| Provider | Service | Processing |
|---|---|---|
| Railway | Application hosting, managed database and object storage | All customer data held by the service, including proof-of-delivery photos, signatures and uploaded files |
| Google (Gmail / Google Workspace) | Email delivery | Recipient address, message content and delivery metadata |
| Google (Maps Platform) | Maps, geocoding, routes and optimisation | Addresses, coordinates and route context needed for the requested function |
| Google (Gemini) | AI-assisted features where enabled | Prompts and limited context submitted by an authorised user |
| OpenAI | AI assistant and voice transcription where enabled | Prompts, voice recordings and limited context submitted by an authorised user |
| Twilio | Operational SMS where enabled | Recipient number, message content and delivery metadata |
| Stripe | Subscription billing and payment administration | Customer account, billing contact and transaction references |
| Expo | Push notifications to the Android driver app | Device push token and notification content |
| Upstash or Railway Redis | Shared caching, rate limiting or job coordination | Technical identifiers and limited operational data needed for the configured function |
| Sentry | Application error diagnostics | Technical, device and error context configured for diagnostics |
| Resend | Alternative email delivery; not in use, available only if we switch email provider | None while not in use |
Locations and safeguards
Providers may use UK, EEA, US or other contracted processing locations. Where a transfer from the UK is restricted, Trackely uses an applicable adequacy regulation or contractual safeguard such as the UK International Data Transfer Agreement or UK Addendum, plus any required transfer assessment. Provider locations can change within their contractual terms.
Changes and objections
Active customers receive at least 30 days' notice before a new subprocessor processes Customer Personal Data where practicable. Customers may object during that period on reasonable data-protection grounds using the process in the DPA. Security or emergency replacement may require shorter notice.
Questions
Ask which providers apply to your deployment or request relevant transfer information at support@trackely.co.uk.