Security

Confidential by design

Penomic runs on your own documents, inside your account. They are never used to train a model, and never shared. This page is exactly what happens to your data, and what never does.

Request access See where it goes
The wall

Two things cross the line. Everything else stays where you put it

Your Penomic account
In

Your data room. Your questions. Encrypted on the way in.

Out

The model, the memo, the deck. Each figure cited to a file that stayed inside this box.

Never crosses back out

The files themselves. Anything a model could learn from them. Any view of them for another customer. The source Alex cites in the memo is the same document that never left this account, which is why confidentiality and sourcing are one fact here, not two features.

The covenant

Your data is used to do your work, and for nothing else. Every provider we rely on is held to the same limit.

The two clauses a General Counsel checks: purpose limitation, and flow-down to every subprocessor.

The honest comparison

The assistant your team already pastes into, and Alex

You already know your analysts paste confidential decks into a consumer chatbot. Here is the honest mirror, peer to peer.

A general-purpose assistant

On many consumer plans, by default, what your team types and the files they attach can be used to improve the system. The content sits in a shared environment, and turning that off is on you, if the plan allows it at all. Locked-down enterprise tiers exist, but the default runs the other way.

Alex

Your documents are never used to train a model, on any plan. Each firm’s data is isolated and never pooled with another’s. There is no default working against you, and no setting you have to remember to switch off.

The difference is the default, and who carries the burden of turning it off.

Chain of custody

Follow one file

financials.xlsx, from the Project Atlas room
→encrypted in transit, stored in your account, read by Alex, uploaded to no model.
the figure Alex pulls, $4.2M EBITDA (illustrative)
→cited back to that file, tab 3 — the source Alex names is a document that never left your account.
the memo she returns
→yours; not added to a training set, not visible to any other customer.
you delete the room six months later
→it is gone, and there is no second copy living inside a model.

Illustrative. The file and figure stand in for your own.

For your security team

What your security team gets, in the order they ask for it

01

A data processing agreement, signed at onboarding, with the no-training limit flowing down to every provider we rely on.

02

Your account, isolated. No firm’s data is pooled with another’s.

03

Access scoped to your team. Sign in with Google, LinkedIn, or a one-time email code, with session timeouts.

04

Regional data handling and custom deployment, settled during procurement rather than bolted on afterward.

05

Governance and audit trails scoped to the engagement. SSO is on the roadmap for Enterprise, stated honestly, not as shipped.

Talk to us about procurement
Access by request

See exactly where your data goes before you send a file

Every account is isolated, every document stays yours, and nothing trains a model you do not own. Bring a live file and we will walk you through it.

Request access

Confidential by design · runs on your own documents · never used for training

contact@penomic.ai·New York