Trust & Legal Center

Security Architecture & Controls

Technical overview of multi-tenant isolation, encrypted credential vaults, HTTPS transport, and security engineering practices.

Last Updated: 2026-08-04Analytics Brain AI
Fundamental Security Disclaimer
Factual Security Statement: While we implement industry-standard encryption and isolation controls, no method of transmission over the Internet or electronic storage is completely secure.

1. Security Foundations & Transport

Analytics Brain AI applies structured, defense-in-depth security principles across its cloud-native Next.js and Supabase infrastructure.

  • HTTPS / TLS 1.3: All web traffic and API endpoints strictly require HTTPS with TLS 1.3 encryption in transit.
  • OAuth 2.0 Framework: Integrations utilize standardized OAuth 2.0 authorization flows, preventing stored provider passwords.

2. Tenant Isolation & Row Level Security

Multi-tenant boundary enforcement is implemented at the core database level:

  • Every data table is strictly scoped by organization_id or project_id.
  • Supabase Row Level Security (RLS) policies validate organization membership for every database query.

3. AES-256-GCM Token Encryption

OAuth tokens and API credentials are protected via encrypted vault mechanisms:

  • Tokens are encrypted at rest using AES-256-GCM authenticated encryption with unique initialization vectors (IVs) and authentication tags.
  • Encrypted tokens reside within a restricted database schema (private.integration_credentials), inaccessible to public API roles.

4. Server-Side Secret Containment

Secret management strictly limits key access to server-side environments:

  • Service-role keys and encryption master keys reside exclusively in secure server environment variables.
  • Token decryption and refresh operations execute server-side within protected API routes.

5. Safe Logging & Dependency Management

Operational transparency is maintained alongside dependency hygiene:

  • Application loggers strip Authorization headers, refresh tokens, and encryption parameters.
  • Minimal third-party dependency footprints are maintained to reduce supply-chain attack surfaces.

6. Responsible Disclosure & Contact

We welcome security researchers to disclose identified vulnerabilities responsibly by contacting our security team at: ahmedomran12622@gmail.com