Data Handling Policy
This page summarizes how Qrousel handles customer data during discovery, pilot implementation, and ongoing support.
1) Data Minimization
We request only the fields required to design and operate the agreed workflow. Sensitive fields can be masked or tokenized before processing.
2) Access Controls
Access is restricted to assigned project contributors. Role-based controls and audit logs are used where client infrastructure supports them.
3) Retention & Deletion
Retention windows are defined per project. We support deletion workflows for temporary stores, logs, and intermediate artifacts.
4) Third-Party Model Providers
When external model providers are used, we configure enterprise-safe settings and align with client policy requirements.