Sub-processors
Version 1.0 · Effective 1 August 2026
Letora uses the following providers to run the platform. Role classifications are set out per provider below.
| Provider | Service provided | Role classification | Processing purpose |
|---|---|---|---|
| Vercel | Application hosting, edge network and request logging for letora.ai | Processor/sub-processor for relevant hosting, edge and logging activity | Running the platform; serving web and API traffic; operational logs |
| Supabase | PostgreSQL database and file storage | Processor/sub-processor for database services | Storing platform data agents enter or import — properties, tenancies, contact details, compliance records, documents and photos |
| Clerk | Authentication for agent accounts | Processor for end-user authentication data; independent controller for defined account information | Sign-in, session management and account security for agent users |
| Anthropic | AI model API (commercial API) | Sub-processor where used through the commercial API on Letora's instructions | Processing text submitted to AI features — import field mapping and the AI assistant — on Letora's instructions |
| Twilio | WhatsApp messaging | Processor for message content and delivery data in relevant services; possible controller processing for specified telecom/account purposes | Delivering workflow notifications and portal links; message content and delivery data |
| Stripe | Subscription billing and payment processing for Letora's own fees | Mixed processor/controller | Processing agent subscription payments, invoicing and tax |
| GoCardless | Direct Debit collection (bank payments) | Ordinarily independent controller for payer and merchant payment data — NOT listed as an Article 28 sub-processor for its regulated payment service | Payer and merchant payment data for its regulated payment service |