Follow the information through the actual deployment.
Website enquiries, CRM records, support tickets and model requests may pass through different services. Before production, document which fields are collected, the business purpose, the receiving systems and the people permitted to inspect them.
A general architecture diagram does not establish a universal data location, training policy or retention period. Those details must be checked for the selected accounts, providers and contracts.
Collect what the task needs.
An initial enquiry usually needs enough information for a relevant response, not confidential attachments or a complete customer history. Define the minimum fields and avoid copying sensitive records into routine logs and notifications.
- Name a business owner for the information.
- Distinguish public knowledge from restricted account data.
- Specify which tools may read or change each record.
- Keep unnecessary contact details out of analytics events.
Set retention by record type and system.
Agree the purpose and retention approach for enquiry records, conversation history, operational logs, backups and any third-party processing. Identify how deletion and access requests are handled across connected systems.
No single retention period is promised by this page. The final privacy and processing documents must reflect the actual service, applicable obligations and operational capabilities.
Review the lifecycle when the workflow changes.
Adding a communication channel, model provider or business application can change where information goes. Revisit the data map, permissions and operator guidance when those dependencies change.
Ask ZARIS to describe the proposed information flow and identify any provider decisions still requiring confirmation before deployment.
Questions? Contact [email protected].
