Subprocessors · last updated October 2026
Subprocessors and every outbound call.
Hosted by Latent, eight subprocessors handle your data, listed first. In your VPC or on your hardware, Latent has no subprocessor in the default serving path and nothing leaves it. This page lists both, every outbound call the product can make, and the vendors the company uses for this website and for sales.
Hosted by Latent
These vendors process customer data when Latent hosts it.
| Vendor | Purpose | What it handles |
|---|---|---|
| Lambda | Cloud servers in the United States that run Latent's reader, the scoring service and its database | Prompts, answers, scores and account data, under your retention settings |
| Anthropic | Labels calibration samples as Latent's judge, and writes the rationale for a flagged answer when a reviewer asks for one | The calibration sample's text: source, question and answer. For a rationale, one flagged answer with its question and source |
| Stripe | Billing | Company name, address, tax id and card details. Card numbers go to Stripe directly and never reach Latent |
| Resend | Sign-in emails and email alerts | Your email address and the sign-in link, and for email alerts, the alert message to the addresses you set |
| GitHub | Sign-in | Your email address and GitHub account id |
| Sign-in | Your email address and Google account id | |
| Amazon Web Services (S3) | Nightly encrypted backups of the hosted database and audit logs, in the United States | The same prompts, answers, scores and account data, under the same retention settings |
| PostHog | Product analytics for the console and this website | Page views and sign-up clicks on runlatent.ai, without cookies; from the console and the service, account, organization and project identifiers, the plan, account events with their times and the names of console pages; the company and model from the endpoint waitlist, and the company from the agents waitlist. Never prompts, answers, source documents, API keys, email addresses or names |
In your VPC
With the default two containers running, no subprocessor handles your prompts, answers, activations or weights. These are the outbound calls any component can make. None of them goes to a Latent endpoint.
| Call | What it sends | Goes to | Who controls it |
|---|---|---|---|
| Model weights | A download request with your Hugging Face token. | Hugging Face | You. It runs on first start. After that you can block all egress from the host. |
| Usage reporting in vLLM and Hugging Face | vLLM's own usage statistics and the Hugging Face hub's telemetry headers. | The vLLM project and Hugging Face | You. Both are on in the base install. The hardening overlay, recommended for every new deployment, turns them off. |
| Labeling during calibration | The calibration sample's text: source, question and answer. | The provider you pick, with your key. latent calibrate uses Anthropic unless you choose otherwise. | You. Label with your own reviewers or a model you host, and nothing leaves. |
| Written explanations | The stored source, request and answer for one flagged request. | Anthropic, with your key | You. Off until you set LATENT_EXPLAIN_JUDGE=1. It then runs when a reviewer asks, or on each flagged answer if you turn on the gateway's judge response. |
| Alerts | Aggregates only. The body carries no content and no secrets. | Your webhook, Slack, PagerDuty or email | You. Only when a reviewer saves a destination. Private-network hosts are refused unless you allow them. |
| Stronger-model routing | A flagged request, re-issued. Your client's credential is never forwarded. | The endpoint you name | You. Gateway only, and off by default. |
| Dataset push | The labeled pairs you export, with their text. | Your Hugging Face dataset repo | You. Only when someone on your team presses Push on the Improve page, with a token they type. The token is never stored. |
| Telemetry to Latent | Nothing. | No one | There is no usage reporting, license check or phone-home, and no code that would send one. |
Your keys, your accounts. A call made with your key runs under your own account with that provider. If you turn one on, list that provider as a subprocessor of your own data.
What Latent receives
Hosted by Latent, Latent receives each prompt and answer the SDK sends, as listed on What Latent receives, and keeps them under your retention settings. In your VPC, it receives nothing unless you send it. Two cases come up.
- A report at the end of an Enterprise engagement, if you choose to share it with us.
- Activation statistics from your traffic, if you ask us to fit the calibration for you. The few-MB calibration file comes back to you. You can run the fit inside your environment instead.
Latent never receives, copies or transmits model weights.
The company
These vendors run the website and sales. None of them is part of the product. None of them sees your model's traffic.
| Vendor | Purpose | What it handles |
|---|---|---|
| Netlify | Hosts runlatent.ai | Standard server logs of requests to the site, the email, company and model you give the endpoint waitlist, and the name, email and company you give the agents waitlist |
| Cal.com | Booking calls with us | The details you enter when you book |
Contact
Questions about this list go to security@runlatent.ai. The full security detail is on the security page.