HeiGin

Security & trust

Transparent about what's built and what isn't.

HeiGin is early. Rather than listing badges we haven't earned, this page explains our security model and clearly marks what is still being confirmed.

Our approach

Each topic is labelled by where it stands today.

Core design principleDetails being confirmed

Data access and permissions

Being confirmed

Team members see the customer data their role allows. Role and permission details for the pilot are being finalised.

Agent permissions and approvals

Core design principle

Agents act only within the scope granted to them. Outbound and sensitive actions require human approval by default.

Visibility into agent activity

Core design principle

Every agent proposal and action is recorded with its reason and, where applicable, who approved it.

Data handling and retention

Being confirmed

Retention periods, deletion processes and where data is stored are being documented and will be published here.

Integration access

Being confirmed

Connected tools are intended to request only the access an integration needs, and can be disconnected at any time.

Certifications and compliance

Being confirmed

We do not currently claim any security certifications. We'll list them here if and when they are achieved.

Questions

Have a security question?

Ask us directly at office@heigin.com. We'd rather give you a straight answer than a vague one.