ConveRact · trust
ConveRact Data Privacy and Workspace Architecture
ConveRact data privacy depends on clear workspace boundaries, controlled access, and an agreed deployment configuration. Customer conversations, uploaded files, and business records need handling rules appropriate to their sensitivity.
Plan your ConveRact data privacy workflowFree integration. No installation charge or one-time ConveRact fee. Plan, usage, third-party, and custom development costs may apply.
Keep data within the correct business context
Conversations and related records are scoped to a tenant. Team roles govern access, and attachment endpoints require authorization. Developers must maintain tenant and customer identity boundaries when integrating custom applications.
Understand external processing
Enabled messaging, payment, email, and AI services can involve external processing. Review the privacy policy and deployment configuration for your intended use. This page does not promise a particular residency region or zero retention across every external service.
Plan retention and customer requests
Agree on what is collected, who can export or delete it, and how requests reach an accountable owner. Avoid collecting unnecessary sensitive data in chat. Confirm the operational retention policy before using a workflow for regulated information.