Forms. CRM. WhatsApp. A more connected way to grow. Meet your platform ↗
security

Built for data that belongs to somebody else.

Review Insta AI 365 security information on workspace isolation, role permissions and integration credentials. Contact the team for a security review.

Workspace isolation

Every record belongs to a workspace, and the boundary is checked in the API on each request — not enforced by hiding things in the interface.

Role-based access control

Permissions decide what each person can read and change, and the same rules apply to the REST API and to Ira AI.

Field-level permissions

Individual fields can be restricted per role, so sensitive values stay hidden from teammates who should not see them.

Encrypted credentials

Integration secrets, OAuth tokens and webhook signing keys are encrypted with AES-256-GCM before they are stored, and are never returned to the browser.

Hashed passwords

Account passwords are stored as bcrypt hashes. They are never written to logs and cannot be read back out of the system.

Signed webhooks

Outbound webhooks are signed so you can verify they came from us. Inbound webhooks are signature-checked, and the workspace is resolved from our own records rather than from the payload.

Malware scanning on upload

Files are scanned before they are stored. If the scanner is unavailable the upload is refused rather than accepted unscanned.

Hardened file handling

Storage keys are validated against the owning workspace, and downloads are served with headers that stop a file being executed in the browser.

Audit trail

Sensitive actions are recorded, so a change can be traced back to the account that made it.

Encrypted in transit

All traffic to the application and the API is served over TLS.

What we do not offer today

  • Single sign-on (SSO). SAML, OIDC and SCIM provisioning are not implemented. Access is managed with accounts, roles and field-level permissions inside the workspace.
  • SOC 2 or ISO 27001 certification. We hold neither. We would rather say so than display a badge we have not earned.
  • A published uptime figure or SLA. We do not measure and publish availability, so we do not quote a number for it.

No system is unbreakable, and we make no claim to be. If one of these is a requirement for you, raise it on a demo call and we will tell you exactly where we stand.

Read privacy policy
A CLOSER LOOK

Understand who can access customer information

A CRM security review starts with the people and systems allowed to read or change records. Review workspace boundaries, roles and field permissions alongside your own account-management process. Give each teammate the access required for their work and review it when responsibilities change.

The controls described here are product information, not a third-party audit report. If your organisation has specific evidence, residency or contractual requirements, discuss them with the team before purchase. The privacy policy explains data handling, and the deletion page describes how to request removal.

Questions about CRM Security: Permissions & Workspace Controls

Does Ira follow CRM user permissions?

Ira is subject to the permissions of the person asking. The same access model applies to supported CRM actions; review your role setup before giving users access.

How can I review Insta AI 365 security before purchase?

Read the controls on this page and send the team your security requirements. Ask for the evidence and contractual information your organisation needs rather than assuming a certification from a feature description.

YOUR NEXT CHAPTER STARTS HERE

More meaningful conversations.
More momentum.

Bring your sales process together. Let your team move forward.

CRM + WhatsAppExplore plans →Book a demo ↗