Skip to main content
Ontelis home
See a demo
Ontelis home

Control what agents see, field by field

Mask decides what Ontelis stores, what each person or agent sees and what may leave your data plane. Named people approve every change.

MaskPolicies
Mask policy US-COM v14
EHR-derived feed · Approved by Halvane’s privacy officer, Mon Oct 12, 2026
Store gate
Mask policy US-COM v14, store gate, one EHR-derived record
FieldWhat Ontelis holdsStore treatmentClass
Patient nameNot ingestedDo not ingestPatient
Patient IDP-7f3aPseudonymizePatient
Birth date1961Generalize to yearPatient
ZIP021Generalize to three digitsPatient
DiagnosisThe ICD-10 codeKeep as codePatient
Prescriber NPIThe NPI, refreshed by syncKeepLicensed third-party, HCP personal
Fill date2026-W14Week only, under Halvane’s Expert DeterminationPatient
Safe Harbor alone would allow only the year for the fill date. Three-digit ZIP is kept only where that area has more than 20,000 people, otherwise 000.
One record from an EHR-derived feed, after the store gate. HCP is a healthcare professional; NPI is the National Provider Identifier.

Trusted by 2 out of the 5 largest life sciences companies

Every field is classed before it is stored.

Mask reads the labels you already keep in Purview, Collibra, BigID or Snowflake, and proposes a class for the rest. A data steward confirms each one. New fields stay out until classed.

Decide what Ontelis holds, per field.

Keep a value, point to it, swap it for a token, generalize it or drop it. Tokens are looked up in your own vault, never made by hashing a name.

Each reader sees only what their purpose allows.

Every request declares a purpose. The same record reaches an analyst with patient detail, a rep’s agent as counts only and Copilot not at all.

Masked data stays masked wherever it goes.

Treatments follow each value into context packages, decision records, the ledger and model prompts. Patient data goes only to endpoints inside your boundary, and no model is trained on it.

Named people change each rule.

Tightening takes one signature. Loosening patient data needs the privacy officer and a passing re-identification check. Ontelis staff can propose, never approve.

Prescribing data stays out of anything of value.

Speaker picks, consulting, advisory boards and grants cannot use prescribing-derived fields, and a lineage check proves it. Linkage and re-identification blocks hold even if you ask to lift them.

“What won over our compliance team wasn’t the speed. It was that the agent shows its work, stops at Draft, and tells you when it doesn’t know.”

Head of Marketing OperationsOne of the top five US biopharma companies

What Mask does not do

  • Certify HIPAA de-identificationYour privacy office or an outside expert decides; Ontelis stores and enforces the decision.
  • Capture consentThat stays in OneTrust or the CRM.
  • Act as company-wide data loss preventionMask controls what Ontelis stores, serves and sends.
  • Write your privacy policyYour privacy office sets the rules a Mask policy enforces.

Where Mask fits

Mask shapes each context package and sets which models an agent draft may use.

  1. 01TriggerAgents
  2. 02 · This pageContext packageContext Graph, with IntuitionDB and Mask
  3. 03 · This pageAgent draftAgents
  4. 04Govern checksGovern
  5. 05Decision cardWorkspace
  6. 06Write through ConnectConnect
  7. 07LedgerGovern
  8. 08Outcome to IntuitionDBIntuitionDB

Watch Ontelis at work

Short walkthroughs of agents doing commercial work, from the first draft to the person who signs off.

Trace a share loss to access or field

Analytics & Insights · Commercial analytics agent · 4:06

0:00 / 4:06

Customer stories

One of the top five US biopharma companies

Brand teams get HCP answers in under 30 seconds

Read the story
One of the top 10 global pharma companies

Email campaigns cut from 131 effort-days to 46

Read the story

Data masking and pseudonymization

Ontelis Mask controls, field by field, what Ontelis stores, what each person or agent sees and what may be sent to an AI model or an outside agent. It's how data masking and pseudonymization work in Ontelis: a patient ID can be held as a random token, a birth date as a year and a patient name not at all. A data steward confirms each field's class, and named people at your company approve every rule change.

Security and data

Data in Mask
The pseudonymization lookup table sits in the customer’s vault under a separate key role, so the people who operate Ontelis cannot reverse tokens.
Vendor documents
Ontelis provides: a SOC 2 Type II report, an ISO 27001 certificate, a HIPAA business associate agreement wherever Ontelis processes PHI, a data processing agreement with transfer clauses, and a sub-processor list.
Models
Ontelis builds no foundation model. No model is trained on customer data, except an opt-in adapter that never leaves the customer’s data plane.
Your controls
Ontelis’s posture as a vendor is kept separate from Govern, which holds your own controls.

Control what agents see, field by field

See a demo