Controls

Customer data isolation

Each customer's data is isolated at the database level: users only see data from their own company and teams.

Role-based access

Admin, Manager and Agent roles, plus custom roles, limit each user to what their job requires.

Multi-factor authentication

Available to every user with an authenticator app, and required for every access once enabled.

AI assistant limited to the user's permissions

The assistant only sees what the signed-in user is allowed to see, and cannot change data.

No staff access through the application

The application has no feature that lets Intract staff sign in as one of your users or open your workspace.

Secure invitations

Invitation and password links are single-use and expire.

Protected API keys

API keys are stored in a form that cannot be read back, even by Intract.

Encryption in transit

Every connection uses HTTPS with modern TLS; older protocol versions are refused.

Private file storage

Audio and files cannot be reached through a public link.

Integration credentials encrypted

Telephony credentials and webhook secrets are stored encrypted, and are not displayed again once saved.

Secrets management

Infrastructure secrets are kept in a dedicated, access-controlled vault, separate from the code.

No long-lived deployment credentials

Deployments and services authenticate with short-lived credentials rather than stored keys.

Browser security policies

Security headers restrict what the browser may load and stop other sites from embedding the application.

Cross-site request protection

Requests that change data are only accepted from the application itself.

Safe handling of external links

Links the application fetches on your behalf are checked so they cannot reach internal systems.

Abuse protection

Repeated attempts on sensitive actions are limited.

Content sanitisation

Content generated by the AI or entered by users is cleaned before it is displayed.

Verified integrations

Events from your telephony provider are verified before they are processed; unknown sources are refused.

Signed API requests

You can sign API requests so they cannot be altered or replayed.

Upload checks

Uploaded files are checked for type and size.

Automated testing

Every change goes through automated checks and tests.

Controlled database changes

Database changes are versioned, tested and approved before they reach production.

AI processing logged

Every call to an AI model is recorded.

Recording access logged

Every playback of a recording is logged.

Settings history

Changes to audio retention are logged and shown in your settings.

Webhook secret history

Actions on webhook secrets are logged and shown in your settings.

API key activity

Each API key shows when it was last used.

Audio retention you control

Set company-wide, with exceptions per team; audio past that period is deleted automatically. By default, audio is kept until you set a duration. Audio from Aircall or Vonage is not copied to Intract.

Assistant exports deleted automatically

Files the assistant generates are deleted after the period you set.

Assistant memory cleared

The assistant's working memory for a conversation is cleared after a period of inactivity.

Limited log retention

Logs are kept for defined periods, then deleted automatically.

30-day recovery window

Deleted audio and files can be restored for 30 days, then they are removed for good.

Deletion at the end of the contract

All of your company's data is deleted, including transcripts held by our transcription provider, and you receive a dated deletion report.

Immediate removal of members

A member removed by an admin loses access at once; their personal data in the workspace is deleted or anonymised.

Incident response plan

A written plan sets out how incidents are handled and how you and the supervisory authority are notified within 72 hours where the GDPR requires it.

Redundant storage

Audio and files are replicated to a second European region.