DATA SEGREGATION FRAMEWORK

GDPR Data Isolation

Operational Standard • Vault Engine v1.2

ReviewAI implements strict logical multi-tenant database isolation parameters. This document explicitly outlines our data segregation mechanisms to ensure total compliance with GDPR data boundary mandates.

1. Logical Multi-Tenant Segregation

Our database architecture utilizes strict row-level security (RLS) policies within our PostgreSQL cluster. Every review payload, location metric, and Google token string is forcefully tagged with a unique, encrypted tenant_id identifier, making cross-account data bleeding structurally impossible.

2. Serverless Encryption Matrices

All authorization tokens received from external Google API callbacks are encrypted at rest using AES-256-GCM configurations. Decryption keys sit inside a separate, sandboxed system memory vault that is only accessible during active review sync actions.

3. Automated Purge Protocols

In complete alignment with GDPR Article 17 ("Right to erasure"), disconnecting a Google profile from our dashboard initiates a structural cascade-delete command. All saved cache strings, review logs, and token parameters are fully purged from active memory and physical disks within 48 hours.