1. Security Architecture Overview
Valorenode is engineered in Portugal as a security-first, multi-tenant SaaS platform. Our architecture assumes zero trust at every layer — from browser client through API gateway, AI inference pipeline, and persistent storage. Legacy review tools bolt security on as an afterthought; Valorenode embeds isolation, encryption, and audit into the foundational schema.
2. AES-256 Data-at-Rest Encryption
All persistent data — review content, AI conversation history, analytics aggregates, and audit logs — is encrypted at rest using AES-256-GCM. Database volumes are encrypted at the storage layer (Supabase/AWS), and application-level envelope encryption protects sensitive fields with per-organization data encryption keys (DEKs) wrapped by a master key in our EU-hosted KMS.
- Key rotation: DEKs every 90 days, master key annually
- Encryption in transit: TLS 1.3 minimum on all endpoints
- Backup encryption: AES-256 with separate key hierarchy
3. Multi-Tenant Isolation Protocols
Tenant isolation is enforced at the PostgreSQL Row-Level Security layer with FORCE RLS on every organization-scoped table. JWT custom claims carry organization_id and role, validated on every query. The Supabase service role key — which bypasses RLS — is restricted to audited server-side operations with explicit organization scoping and is never exposed to client bundles.
4. AI Pipeline Security
OpenAI API calls originate exclusively from server-side gateways. Prompts are minimized to field-level allowlists, responses are schema-validated before persistence, and PII scrubbing runs when ENFORCE_GDPR_DATA_MASKING is active. API calls use store:false to prevent model training on customer data.
5. Incident Response
Our incident response plan follows NIST SP 800-61 guidelines adapted for EU operations. Detection, containment, eradication, recovery, and post-incident review phases are documented with assigned roles. Security contact: security@valorenode.com.