Subprocessor register
Providers that help run Trackely.
Last updated
25 July 2026
Trackely Ltduses 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 and managed database hosting | Production service infrastructure |
| Amazon Web Services or Railway Object Storage | Object storage | Proof-of-delivery photos, signatures and uploaded files; the active provider depends on deployment |
| Maps, geocoding, routes and optimisation; Google Cloud or Gemini features where enabled | Addresses, coordinates, route context and feature prompts needed for the requested function | |
| Stripe | Subscription billing and payment administration | Customer account, billing contact and transaction references |
| Resend | Transactional email delivery | Recipient address, message content and delivery metadata |
| Twilio | Operational SMS where enabled | Recipient number, message content and delivery metadata |
| OpenAI | AI-assisted features where enabled | Prompts and limited context submitted by an authorised user |
| Upstash or Railway Redis | Shared caching, rate limiting or job coordination where enabled | Technical identifiers and limited operational data needed for the configured function |
| Sentry | Application error diagnostics where enabled | Technical, device and error context configured for diagnostics |
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.