Summary
sub-processors-v0.1.md
TradeBoard uses the following providers to operate the service.
| Provider | Purpose | Data processed | Notes |
|---|---|---|---|
| Cloudflare | Hosting, DNS, security, admin access protection | Technical request data, admin access data, Worker runtime data | Beta provider. Account region, log retention and transfer details to be confirmed before paid launch. |
| Supabase | Authentication, database, file storage | Account data, deal data, files, auth data | Beta provider. Project region, backup settings, storage settings and transfer details to be confirmed before paid launch. |
| Resend | Transactional email | Email address, message content, delivery metadata | Used for operational emails, invitation emails and delivery status information. |
| Swiftcomplete | Address lookup | Address search queries and selected address data | Used when address lookup is requested. |
| what3words | Location search/conversion and map components | Location search queries, coordinates, what3words addresses and related technical data | Used when location features are requested or displayed. |
| Google Maps | Map display, directions and related map services | Map interaction data, location data and technical data | Used where maps or route directions are displayed. Not used as site-wide analytics. |
| DVSA MOT History API | Vehicle MOT lookup | VRM, vehicle lookup data and technical request data | Used when MOT lookup is requested. Confirm supplier terms and whether this should be treated as a sub-processor or public-sector lookup source before paid launch. |
TradeBoard may also connect to broker or customer-configured systems, such as TipsTrade API imports, where an authorised broker enables that integration. Those integrations should be reviewed separately because they may be customer source systems rather than TradeBoard sub-processors.
TradeBoard may update this list as providers change. Material changes should be reviewed and communicated through the legal update process.