Everything your security team will ask, answered here.

LeoTrace reviews code in the cloud, so it sends code. Here is exactly what, where it goes, how long it stays, and the certificates behind it.

What is sent, turn by turn

WhenWhat is sentNever sent
Every turnMetadata: git name and email, repository remote, agent and model, token counts, timing, platform and plugin versionCode or your prompt
A turn that changed codeThe changed lines, the full text of those files, the local helpers they import (one hop, capped at 128 KB), and your promptThe rest of the repository
After the agent is toldThe code before and after the fix, and the agent's reply
Sweep, only when you run itThe whole files that hold open scanner findings
AlwaysSecret files (.env, keys, credential stores) and symlinks

AI model providers4

They run the AI models behind LeoTrace, for any part of the service, and may receive any customer data a task needs. None may use it to train their models. Every task and the data each one receives are listed in the sub-processor list.

Amazon Web Services (Amazon Bedrock)Any part of the service, as the main model, a fallback or a backupEuropean UnionEntered through London, may run in other EU regions
Provider retention
Not stored by AWS; invocation logging is off
Anthropic (API and Claude)Any part of the service, as the main model, a fallback or a backupUnited States
Provider retention
Deleted within 30 days, unless flagged for a usage policy breach or required by law
OpenAI (API and Codex)Any part of the service, as the main model, a fallback or a backupUnited States
Provider retention
Abuse monitoring logs kept for up to 30 days
Google Cloud (Vertex AI, and open models on LeoTrace’s own Google Cloud servers)Any part of the service, as the main model, a fallback or a backupEuropean UnionVertex AI EU endpoint; LeoTrace’s own servers in the Netherlands
Provider retention
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 storage5

Fly.ioHosts the review serverUnited KingdomLondon
Customer data it receives
Customer code, while in transit and being processed
VercelHosts the customer dashboard and staff consoleUnited KingdomLondon
Customer data it receives
Dashboard pages and the data they read from the database
MongoDB AtlasDatabase for review records, accounts, licences and dashboard loginsUnited KingdomLondon, on AWS
Customer data it receives
Stored review data, account data and customer code kept under our retention periods
Amazon Web ServicesCloud infrastructure, including the servers behind MongoDB Atlas and any LeoTrace serversUnited Kingdom and European Union
Customer data it receives
Customer data stored or processed on that infrastructure
CloudflareDNS for leotrace.io, and network protection if we route traffic through itGlobal network
Customer data it receives
None today

Product services6

ResendSends product email: invites, verification, password resets, trial reminders and the weekly summaryUnited States
Customer data it receives
Recipient email address and the email. No keys, code or finding detail
PostHogProduct analytics and session recordings on the customer dashboardEuropean UnionPostHog EU cloud
Customer data it receives
Page views, clicks and screen recordings, with code, findings, repositories and people blocked from capture
GitHubSign-in option on the dashboardsUnited States
Customer data it receives
The standard sign-in exchange
GoogleSign-in option on the dashboardsUnited States and European Union
Customer data it receives
The standard sign-in exchange
MicrosoftSign-in option on the dashboardsRegion of the user’s Microsoft tenantWith some processing in the United States
Customer data it receives
The standard sign-in exchange
Slack (LeoTrace’s own workspace)Internal notifications about sign-ups, pilots and alertsUnited States
Customer data it receives
Account name, repository name, rule name, severity and counts. No code or finding text

Business systems that hold customer account details4

StripeTakes payments and runs subscriptionsEuropean Union and United States
Customer data it receives
Billing contact, company details, subscriptions and invoices. Card details are held by Stripe
AttioCustomer records and account settingsGoogle CloudAttio does not publish the region
Customer data it receives
Contact names, job titles, business email addresses, company records and account settings
DocusignSigns order formsThe Docusign data centre for the account’s region
Customer data it receives
Signatory names and email addresses, and signed documents
Google WorkspaceEmail, documents and support correspondenceUnited States and European Union
Customer data it receives
Whatever a customer sends us by email, including any code or findings shared in support

To get notice of changes, email [email protected]. The security contact on each paid account is subscribed automatically.

Documents

GDPR

Our role
For the code and other content LeoPrevent reviews on a paid plan, the customer is the controller and LeoTrace is its processor. LeoTrace is the controller of account, billing and contact details, usage monitoring and product analytics, as our Privacy Notice explains.
Data processing agreement
Our Data Processing Schedule is Schedule 1 of the LeoPrevent Terms of Service, so it applies as soon as the terms are accepted, with nothing separate to sign. Enterprise customers can agree their own data processing terms in their contract.
Transfers to the US
Reviews run on Amazon Bedrock in the EU. Some providers on our sub-processor list are in the United States, including Anthropic and OpenAI, which may also process customer code. Where personal data goes to a country without UK adequacy regulations, we use the UK International Data Transfer Agreement or the EU Standard Contractual Clauses with the UK Addendum. Email [email protected] to ask which applies to a specific provider.
Data requests
Email [email protected] and we will reply within one month. If your request concerns data we process for one of our customers, we pass it to that customer, as the controller, within two business days.
ICO registration
LeoTrace Ltd is registered with the Information Commissioner’s Office under registration number ZC063220.

Questions security teams ask

No. We don't train models on your code, and our terms say so.

Yes. Excluded repositories send nothing at all.

Not today. Reviews run in our cloud.

Need something for your review? Ask us for it here.

Our ISO 27001 certificate, the statement of applicability, or answers for your security review.

What do you need?