Security

Security and data handling, in plain terms.

What leaves the browser, what we store, where it lives, and what never touches our systems. Everything on this page matches the shipped product.

The path of a prompt

Your browser

The extension checks the draft as it is typed and gates the send button.

Airentect gateway

Sydney, Australia. The full prompt arrives here for classification.

Classifier

Runs within Australia. Returns category, action and any PII spans.

Your console

The outcome is logged for your admins. What is stored depends on the action.

The full prompt is sent to us for classification. Whether it is kept afterwards depends on the action: redacted prompts are replaced with a placeholder; audited, warned and blocked prompts are retained for your review.

What we store, and what we never do

Redacted prompts aren’t kept

When policy redacts a prompt we store a placeholder, not the original text. Not even its hash is retained.

PII values never touch our database

Values found for redaction are returned to your browser and go no further. The redaction map lives in browser session memory and is destroyed when the browser closes.

Keys are hashed, access is scoped

Extension keys are stored as SHA-256 hashes. Every tenant table denies direct access at the database, and all reads are organisation-scoped on the server.

Where your data lives

System	Region	What it holds
Gateway & classification	Sydney, Australia	Prompts in transit; classification runs within Australia.
Database	Sydney, Australia	Audit logs, org configuration, directory.
Report email	Sydney, Australia	Scheduled and ad-hoc exposure reports.
Console & website hosting	Global CDN, US compute	Application serving; no prompt storage.
Sign-in	United States	Console admin accounts only, never extension user prompts.

Found something? Tell us.

Report security issues to security@airentect.com. We read every report, and genuine findings get a reply from the team, not a form letter.

Email security@airentect.com