LinearPilot
Enterprise Security

Your data. Your rules. Always.

Named AI providers under no-training terms, encryption at rest and in transit, and access controls at every layer. Every claim on this page maps to code we ship.

Security architecture

Three layers of protection.

Your data is protected at every level — from the AI engine to the database to external integrations.

1

Masked before anything leaves

Your AI runs on providers we name on our Sub-processors page, under API terms that exclude your data from training their models. Sensitive fields are masked before a request leaves; Data Shield adds name and identifier masking.

Learn about Private AI
AI Processing
Your workspace
Sensitive fields are masked here, before the request leaves
Sensitive fields encrypted
AES-256-GCM at rest — credentials, tokens, personal identifiers
Named providers only
Listed on our Sub-processors page, under no-training terms
2

External AI sandbox

When you use external AI models like ChatGPT or Claude, LinearPilot masks sensitive fields before sending. Emails, phone numbers, card and ID numbers, and addresses are swapped for placeholders, and the real values are restored in the reply you see.

See the data flow
Sample record — for illustration
1
Your data
Sarah Chen, Acme Corp, $47K
2
Sent to AI
[CONTACT], [COMPANY], $47K
3
AI responds
[COMPANY] paid $47K last quarter
4
You see
Acme Corp paid $47K last quarter
3

Security controls that ship today

The controls these frameworks call for — encryption, tenant isolation, field masking, and full audit logs — ship in code today. Formal SOC 2 and ISO 27001 certification is not yet in place, and a signed DPA is available on request.

Request compliance details
Compliance Status
SOC 2 Type II
Not yet certified
GDPR
Practices in place
HIPAA
BAA on request
ISO 27001
Not certified
What's in the box

What's actually in the box

The security controls that ship in LinearPilot today — each one backed by working code.

Multi-tenant isolation

Every query that reads or writes your records is scoped to your company in the application before it runs, so one company's rows never appear in another's results.

Record-level visibility

Inside your company, individual records can be limited to the people and groups you choose.

Two-factor sign-in

Time-based one-time codes (TOTP) add a second factor on top of the password.

AES-256-GCM at rest

Sensitive fields are encrypted at rest with authenticated AES-256-GCM.

Breached-password blocking

New passwords are checked against Have I Been Pwned and rejected if they've already leaked.

PII masked before external AI

When a request goes to an external model, emails, phone numbers, and ID numbers are swapped for placeholders and restored only in your view.

Per-plan AI governance

Admins decide which AI capabilities and sensitive categories each plan and app can use.

Managed provider accounts

LinearPilot holds the provider accounts and their keys, so there is nothing for you to obtain or rotate. You pick the LinearPilot tier that answers, on any plan.

Audit engine

Security-relevant actions are written to an audit trail you can review.

Hardened request layer

Middleware blocks SSRF, throttles brute-force logins, and rate-limits abusive traffic.

Trust & compliance

Built for regulated industries.

Healthcare, finance, legal — the controls each of them asks about, described exactly as they ship.

Healthcare

Record-level access controls, sensitive fields masked before anything reaches an AI provider, and an audit trail for account and AI activity.

Financial Services

Sensitive fields encrypted at rest with authenticated AES-256-GCM, data in transit encrypted with TLS, and security-relevant actions written to an audit trail.

Legal

Attorney-client privilege stays protected with named AI providers under no-training terms, sensitive fields masked before anything leaves, and per-matter access controls.

Security without compromise.

Get enterprise-grade security from day one. No add-ons, no extra cost.