We don't train on your data
Your prompts and Blueprints are not used to train any model. Anthropic is contractually prohibited from training on your data, and we don't train models ourselves.
Our security posture, subprocessors, and compliance stance.
Your prompts and Blueprints are not used to train any model. Anthropic is contractually prohibited from training on your data, and we don't train models ourselves.
The complete list of third parties that touch your data is short by design. See below.
Plugin binaries are Authenticode-signed on Windows, Apple-notarized on macOS. Release manifests are Ed25519-signed with keys held offline.
Every mutating tool in your editor asks for explicit approval — default per-call, overridable per-run or per-session.
Every mutating request is logged immutably. Exportable on request.
US-only or EU-only inference routing available on enterprise plans.
This is the complete list. We will notify customers in advance if it changes.
| Vendor | Purpose | Data | Region |
|---|---|---|---|
| Anthropic | LLM inference | Prompts + tool metadata (not retained beyond processing) | US / EU |
| Stripe | Payments | Billing email, payment method on file, invoice metadata | Global |
| Cloudflare | Edge, WAF, DNS, R2 storage | IP, user agent, request metadata | Global |
| Fly.io | API compute + managed Postgres | Full application database | US / EU on request |
That is our entire subprocessor list. We do not use Sentry, PostHog, Amplitude, Datadog, Resend, Mixpanel, or any other data-collecting vendor. Error reporting, product analytics, metrics, and status pages are all operated by us.
We maintain a self-assessed controls binder aligned with SOC 2 Trust Services Criteria. Evidence is refreshed quarterly via our internal audit script. Formal SOC 2 attestation is available on written request for enterprise customers; delivery timeline is typically 60–90 days after contract signing.
Email security@blueprintproai.app. We acknowledge within 24 hours and target initial assessment within five business days. See our security.txt.