Preparing Opera AI
Loading your workspace…
Preparing Opera AI
Loading your workspace…
Explore how Opera AI implements PostgreSQL Row-Level Security, AES-256-GCM secret encryption, structured audit logging, and operational controls aligned to major privacy regulations.
Our data-handling controls are designed to support regional data-protection obligations wherever your customers are located.
Scope: Consent, notice, rights & grievance redressal
Supports Data Fiduciary / Data Processor separation, explicit notice, consent withdrawal, nomination, breach notification, and grievance redressal under India's DPDP Act, 2023.
Scope: Controller & processor obligations
Structures controller and processor roles, lawful bases, sub-processor disclosures, and data-subject rights (access, correction, erasure, portability) to align with the GDPR and UK GDPR.
Scope: Service-provider role & no data sale
Provides transparent notice of data practices, honours access and deletion requests, and never sells personal information or shares it for cross-context behavioral advertising.
Scope: LGPD, PIPEDA, APPI & similar principles
Applies core data-minimisation, purpose-limitation, and security principles where other regional privacy laws apply.
Scope: Gateway-hosted checkout & offline ledger
Opera AI never stores raw credit/debit card PAN or CVV data on its servers. Online payment links (when configured by a tenant) are hosted by PCI-compliant gateways such as Razorpay, while offline ledger entries record only transaction references.
Scope: Material change traceability
Material changes across workspace configuration, financial ledgers, and records are written to structured, append-oriented database audit logs with actor and trace identifiers.
We enforce strict multi-tenant isolation, secret encryption, and automated test gates. We are not ISO/IEC 27001, SOC 2, or PCI-DSS certified.
Every tenant-scoped table enforces PostgreSQL Row-Level Security (FORCE ROW LEVEL SECURITY), and the application executes as a non-privileged database role (operaai_app) without superuser or BYPASSRLS privileges.
Tenant API keys, webhook secrets, and third-party integration credentials are encrypted at rest using authenticated AES-256-GCM envelopes (enc:v1:) and transmitted exclusively over HTTPS/TLS.
Workspace media and documents are stored under tenant-scoped object keys with strict content-type validation, Content-Security-Policy sandboxing, and authenticated access checks.
Our TypeScript codebase runs continuous unit, schema, API-guard, and live Row-Level Security verification suites to prevent cross-tenant data leakage. This is an internal engineering practice, not an ISO certification.
Opera AI runs on managed cloud infrastructure (Vercel, Neon PostgreSQL in Singapore, Cloudflare R2 / Bunny.net, and Upstash Redis) with automated health checks. We do not guarantee a specific uptime SLA.
Workspaces support role-based staff permissions, HTTP-only session cookies, automatic session rotation on password reset, and optional TOTP two-factor authentication.
Opera AI relies on concrete, verifiable engineering controls at the database, cryptographic, and network layers rather than marketing badges. Review our Privacy Policy and Terms of Service for complete legal and sub-processor disclosures.
All tenant queries execute under the RLS-bound operaai_app role with FORCE ROW LEVEL SECURITY across tenant-scoped tables.
WhatsApp Cloud API webhooks (X-Hub-Signature-256) and outbound tenant webhooks (X-Opera-Signature) use HMAC-SHA256 verification, and internal scheduled jobs verify secrets via constant-time comparison over TLS.
Opera AI never trains its own AI models on tenant conversations or records; third-party model inference (Google Gemini, OpenAI, NVIDIA) is governed by provider API terms and your BYOK configuration.