LeoTrace · Sub-processors

This page lists the service providers that LeoTrace Ltd uses, or may use, to provide LeoPrevent and LeoLearn. It is the Sub-processor Page referred to in our Terms of Service and data processing schedule, and each customer approves the sub-processors listed here on the date it accepts our terms.

We list every provider that might process customer data in providing the service, including providers we have set up but do not yet use for all customer traffic, so that a change of provider is already covered. Which AI provider handles a given review can change from day to day, and is chosen by LeoTrace.

Changes and notifications

We give at least 14 days’ notice before a new or replacement sub-processor starts processing personal data, by updating this page and emailing everyone subscribed to changes. The security contact on each paid account is subscribed automatically. Anyone else can subscribe by emailing [email protected]. Where we have to replace a provider urgently to protect personal data or keep the service running, we tell subscribers within five business days and the customer can still object. Our Terms of Service explain how a customer can object.

AI model providers

These providers run the AI models that review code. None of them may use customer data to train its models.

Sub-processor	What it does	Customer data it receives	Location	Provider retention
Amazon Web Services (Amazon Bedrock)	Runs the models that select rules, check code and re-check fixes for every review	The changed code, prompt, helper code, the fix and the agent’s reply	European Union (entered through London, may run in other EU regions)	Not stored by AWS; invocation logging is off
Anthropic	Fallback when Amazon Bedrock cannot answer, backup model when the main model declines a fix check, and finding titles, Repository Context and pilot reports	Customer code for any review that falls back to it, and repository content for Repository Context, where a customer switches it on	United States	Deleted within 30 days, unless flagged for a usage policy breach or required by law
OpenAI	Model inference, including Codex used by LeoTrace staff to check findings	Customer code and findings, where used for a review or a finding check	United States	Abuse monitoring logs kept for up to 30 days
Google Cloud	Gemini models through Vertex AI, and open models that LeoTrace runs on its own Google Cloud servers	Customer code, for any review routed to it	European Union (Vertex AI EU endpoint; LeoTrace’s own servers in the Netherlands)	Cached for no more than 24 hours, and Google may log prompts to detect abuse; LeoTrace’s own servers keep nothing after the review

Hosting and data storage

Sub-processor	What it does	Customer data it receives	Location
Fly.io	Hosts the review server	Customer code, while in transit and being processed	United Kingdom (London)
Vercel	Hosts the customer dashboard and staff console	Dashboard pages and the data they read from the database	United Kingdom (London)
MongoDB Atlas	Database for review records, accounts, licences and dashboard logins	Stored review data, account data and customer code kept under our retention periods	United Kingdom (London, on AWS)
Amazon Web Services	Cloud infrastructure, including the servers behind MongoDB Atlas and any LeoTrace servers	Customer data stored or processed on that infrastructure	United Kingdom and European Union
Cloudflare	DNS for leotrace.io, and network protection if we route traffic through it	None today	Global network

Product services

Sub-processor	What it does	Customer data it receives	Location
Resend	Sends product email: invites, verification, password resets, trial reminders and the weekly summary	Recipient email address and the email. No keys, code or finding detail	United States
PostHog	Product analytics and session recordings on the customer dashboard	Page views, clicks and screen recordings, with code, findings, repositories and people blocked from capture	European Union (PostHog EU cloud)
GitHub	Sign-in option on the dashboards	The standard sign-in exchange	United States
Google	Sign-in option on the dashboards	The standard sign-in exchange	United States and European Union
Slack (LeoTrace’s own workspace)	Internal notifications about sign-ups, pilots and alerts	Account name, repository name, rule name, severity and counts. No code or finding text	United States

Business systems that hold customer account details

These providers hold the details of our relationship with each customer, such as contacts, contracts and billing. They do not receive customer code, except any code a customer sends us by email, which Google Workspace holds.

Provider	What it does	Customer data it receives	Location
Stripe	Takes payments and runs subscriptions	Billing contact, company details, subscriptions and invoices. Card details are held by Stripe	European Union and United States
Attio	Customer records and account settings	Contact names, job titles, business email addresses, company records and account settings	Google Cloud (Attio does not publish the region)
Docusign	Signs order forms	Signatory names and email addresses, and signed documents	The Docusign data centre for the account’s region
Google Workspace	Email, documents and support correspondence	Whatever a customer sends us by email, including any code or findings shared in support	United States and European Union

Integrations a customer switches on

These connect LeoPrevent to services the customer already uses. They are the customer’s own providers, not LeoTrace’s sub-processors, and nothing moves until the customer switches them on.

Integration	What moves
GitHub App	The committer list for invites and, for pull request checks, the changed files. LeoTrace posts review comments and a check
Linear, Jira Cloud	Flaw title, rule, severity, repository, file and line, one line of explanation and a link. No code
Aikido, Snyk, SonarQube Cloud, XBOW	LeoTrace reads the customer’s findings in the files being changed. No code is sent
Slack (customer’s workspace)	Weekly counts, as in the weekly email

Contact

Questions about this page, or a request for the transfer mechanism that covers a specific provider: [email protected].

LeoTrace Ltd, company number 16743564, 124 City Road, London EC1V 2NX.