LinearPilot
Data Privacy

Your data. Your rules.

Every SaaS tool wants a copy of your data. LinearPilot keeps yours accounted for — AI providers named in writing, no-training terms, sensitive fields encrypted with AES-256-GCM, and an audit trail of every AI action.

Masked
Sensitive fields masked
No training
Providers named in writing
Your files
On your own storage
Zero
Training on your data
AES-256
Encryption at rest
On-prem
File agent, outbound-only
The difference

Most platforms vs LinearPilot

Without LinearPilot
With LinearPilot
Your data stored on vendor servers
Files can stay on your own storage via the on-prem agent
AI queries sent to third-party APIs
Providers named, no training, full audit trail
No visibility into who accesses your data
Sign-ins, billing changes, and AI activity logged
Vendor lock-in makes migration painful
Your data, your format, export anytime
You see every provider

AI with the providers named

LinearPilot tells you which AI providers process your data and what reaches them. Unlike tools that bury it in a policy, the list is a page you can read, and it changes before a new provider is added.

  • Every provider named on a page you can read
  • A curated model allowlist — no Chinese-origin weights
  • External providers are opt-in, with PII masked and restored
What's in the box

Privacy controls, not privacy promises

Prompt-injection detection

A model screens AI inputs for injection attempts before they ever run.

Curated model allowlist

Only vetted models are routable — no Chinese-origin weights.

Company-scoped isolation

Every query that reads or writes your records is scoped to your company before it runs.

Record-level visibility

Decide who can see each record, not just each app.

Multi-factor auth

Time-based one-time codes on top of every password.

How it works

Data protection at every layer

1

Sensitive fields encrypted at rest

Credentials, tokens, and personal identifiers are encrypted with AES-256-GCM before they're stored.

2

Encrypted in transit

TLS protects data in transit — even internal API calls are encrypted.

3

You decide when AI is on

AI features stay off until someone turns them on, and the setting is per user.

4

External AI sandboxed

When you opt into an external provider, sensitive fields are masked before sending and restored in the reply. The provider sees placeholders, not the real values.

5

Full audit trail

Sign-ins, billing changes, and AI activity are logged to an audit trail. You can export your own account history at any time.

Compliance

Built for regulated industries

We hold ourselves to the controls regulated teams need — and we describe each one exactly as it stands today, without overreach.

  • Sensitive fields encrypted with AES-256-GCM at rest, TLS in transit
  • Data export, erasure requests, and a record of processing
  • Record-level access controls, with an audit trail for account and AI activity
  • No certification claimed today — a signed data processing addendum on request

Take control of your data

Named providers, no-training terms, full audit trails. Free to start.

Start Free Trial