Subprocessor register

Providers that help run Trackely.

This register identifies the provider categories and named services that may process customer personal data for 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.

ProviderServiceProcessing
RailwayApplication hosting, managed database and object storageAll customer data held by the service, including proof-of-delivery photos, signatures and uploaded files
Google (Gmail / Google Workspace)Email deliveryRecipient address, message content and delivery metadata
Google (Maps Platform)Maps, geocoding, routes and optimisationAddresses, coordinates and route context needed for the requested function
Google (Gemini)AI-assisted features where enabledPrompts and limited context submitted by an authorised user
OpenAIAI assistant and voice transcription where enabledPrompts, voice recordings and limited context submitted by an authorised user
TwilioOperational SMS where enabledRecipient number, message content and delivery metadata
StripeSubscription billing and payment administrationCustomer account, billing contact and transaction references
ExpoPush notifications to the Android driver appDevice push token and notification content
Upstash or Railway RedisShared caching, rate limiting or job coordinationTechnical identifiers and limited operational data needed for the configured function
SentryApplication error diagnosticsTechnical, device and error context configured for diagnostics
ResendAlternative email delivery; not in use, available only if we switch email providerNone 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.