We don't look day to day. When it matters, you can trace it.

Admins don't routinely see the content of conversations. What's recorded is a history of actions — who did what, and when. When you need it, you can trace it back through the query API.

Who, when, what — recorded and queryable.

Actions are recorded as audit events, available through a query API.

Image

Who this page is for

Legal & compliance

Need to be able to trace usage after the fact.

IT teams

Checking who did what, and when.

Security reviewers

Want to query for unusual activity.

What's included

Who, when, and what

The actor, timestamp, and content of each action are recorded as an audit event.

Search on screen or ask the AI

Under Audit Log in Settings, filter by period, kind of event and person. You can also ask the AI, for example "show me this month's Legal Hold events", and it sets the filters.

Tamper-evident (hash chain on key records; integrity checks run by our team)

Key records (Tier 1) are linked in an append-only hash chain (standard on Business and above). Our team runs the integrity checks.

Retention tiered by importance

Audit-log retention is split into 3 tiers by importance: 7 years for critical events such as sign-ins, permission changes, GDPR deletion and Legal Hold; 1 year for operational-governance events (7 years for Enterprise anomaly events); 90 days for operation logs.

From event to review

Event occurs

An action is taken.

Recorded

It's captured as an audit event.

Query

Query via API.

Start with the free plan and try three modes — Chat, Compare, and Debate.

Start free
Language日本語English