Data Policy

1. Data Architecture

ViberOS uses a multi-tenant architecture with strict data isolation. Each organization's data is stored in isolated database schemas with separate encryption keys. Agent memory, task history, workflow data, and audit logs are fully segregated between tenants.

2. Data Classification

ViberOS classifies data into four categories: Public (agent skill definitions, workflow templates), Internal (task logs, analytics), Confidential (business data processed by agents, API keys), and Restricted (PII, financial records, credentials).

Guardrails automatically detect and apply appropriate handling rules based on data classification. Restricted data triggers additional encryption and access controls.

3. Data Processing

Agent tasks process data within your tenant boundary. When agents interact with external AI models (Claude, Gemini, OpenAI), only the minimum required context is sent. We do not use your data to train AI models. In-house model deployments process data entirely within your infrastructure.

4. Data Residency

You may select your preferred data residency region during onboarding. ViberOS supports deployment in US, EU, and APAC regions. Data does not leave your selected region unless explicitly configured through cross-region integrations.

5. Backup & Recovery

All data is backed up daily with point-in-time recovery capability. Backups are encrypted and stored in the same region as your primary data. Recovery can be initiated through the Control Center or by contacting support.

6. Data Deletion

You may delete individual tasks, agent memory, or entire datasets through the ViberOS dashboard. Account deletion triggers complete data removal within 30 days, including backups. A certificate of deletion is provided upon request.

7. Contact

For data-related inquiries, contact data@viberos.ai.