How the platform handles access, data and the record.

Where it runs

The platform is designed to run in the carrier's own environment, and the carrier owns the code, the workflows, the data and the record. Google Cloud is the environment set up today.

Access

• Every command and query must declare its authorization. Automated checks on every push and in CI refuse code that doesn't.
• Every permission check is logged, including refusals.
• The same checks refuse any change that adds data reads or writes outside approved entry points.

Data isolation

The build checks refuse any change that skips tenant data isolation.

Health information

Fields marked as PHI are masked automatically in every log and trace.

The audit record

• Audit rows are append-only: no operating identity can delete selected rows.
• Retention is configured per record type (for example, six years).
• Every row is tied to the request that caused it and, where there is one, the AI decision that produced it and the human approval that confirmed it.

AI models

Models sit behind one interface. Anthropic is the provider wired today. When a workflow calls a model, the input it sends goes to that provider, and the record keeps what the model saw, which model and version answered, and what it recommended.

Certifications

Gen22 has no SOC 2 report or ISO 27001 certification today, and makes no HIPAA compliance claim. Send us your security questionnaire; we'll answer it item by item and walk you through any item on a call. What the platform does today is on the capability status page.

Reporting a security issue

Email hello@gen22.ai with "Security" in the subject line.