Security Overview

All data travelling between your browser, our servers, and channel APIs is encrypted with TLS 1.3. We enforce HTTPS on every endpoint - HTTP requests are rejected, not redirected.

All database rows, file uploads, and backups are encrypted using AES-256. Encryption keys are managed by our cloud provider's Key Management Service (KMS), rotated annually.

OAuth access tokens are encrypted at the application layer using AES-256-GCM with a per-tenant encryption key derived via HKDF (HMAC-based Key Derivation Function). This means your WhatsApp token is encrypted with a key that is mathematically derived from your tenant ID - it is cryptographically impossible for another tenant's decryption process to read your token, even if they had access to the raw database.

N8N webhook secrets and API keys are stored encrypted with the same per-tenant HKDF derivation. They are never logged, never returned in API responses, and are only decrypted in-memory at the moment they are needed.

InfrAgent AI runs on Supabase (Postgres database and authentication), Hetzner Online GmbH (application servers, Germany), and Vercel (Next.js frontend). Our hosting providers hold ISO 27001 and/or SOC 2 Type II certifications.

Primary hosting is in Germany (EU), giving UK, EU and international customers EU data residency by default. Transfers to vetted sub-processors outside the UK/EEA are protected by the UK IDTA and EU Standard Contractual Clauses. An India region for DPDP data-localisation preferences is on our roadmap.

All tenant data lives in a dedicated PostgreSQL schema (schema: ia) with Row Level Security (RLS) enforced at the database engine level. Every query automatically filters to your tenant_id - a misconfigured API endpoint cannot accidentally return another tenant's data.

Automated database backups run every 6 hours with 30-day retention. Point-in-time recovery (PITR) is available for the last 7 days. Backups are stored in a separate geographic region from production data.

Only two InfrAgent AI engineers have production database access. Access requires multi-factor authentication (MFA), is logged to an immutable audit trail, and is reviewed quarterly. No employee can access customer conversation content without a documented, time-limited access request.

We use zero third-party analytics tools that receive your customer data (no Mixpanel, no Amplitude on business data). Infrastructure providers (Supabase, Hetzner, Vercel) have access only to the encrypted data they host - not to the encryption keys.

All tenant API calls are authenticated via Supabase JWTs with short expiry (1 hour). Service-level API calls use a separate Service Role Key that never leaves the backend server. No credentials are ever exposed to the browser.

All npm and Python dependencies are scanned daily with automated tools. Critical security advisories trigger an immediate patch process with a 48-hour SLA.

We commission independent penetration testing on an annual cycle as part of our ISO 27001 and SOC 2 certification programmes. Summary reports are available to enterprise customers under NDA.

We welcome security researchers. If you discover a vulnerability, email support@infragentai.com. We commit to acknowledging reports within 24 hours and resolving critical issues within 7 days. We do not pursue legal action against good-faith researchers.

We run 24/7 automated anomaly detection on all API endpoints, database queries, and authentication events. Unusual patterns (bulk data exports, off-hours access, geographic anomalies) trigger immediate alerts.

In the event of a confirmed data breach affecting your tenant, we will notify you by email within 72 hours - meeting both UK GDPR and DPDP Act requirements. Notification will include the nature of the incident, data affected, and steps taken.

Every confirmed security incident receives a written post-mortem shared with affected tenants within 30 days. We do not bury incidents in footnotes.

WhatsApp, Instagram, Facebook, and Gmail tokens are monitored for expiry. Tenants receive email and in-app warnings 7 days, 3 days, and 1 day before a token expires. An expired token disables the channel but does not delete any conversation history.

Platform-level encryption keys are rotated annually. Per-tenant HKDF-derived keys are re-derived automatically on rotation - no re-encryption of stored data is needed.

When a tenant disconnects a channel or deletes their account, all associated tokens are immediately purged from the database. Token deletion is synchronous - there is no window during which a revoked token could be used.