This documentation is an operational starting point, not legal advice. Your organization must assess its purposes, legal bases, retention periods, notices, and any sector-specific requirements.
Which document applies?
The Web App Privacy Notice covers the business users who create, administer, pay for, or request support for a Cosmo account. It does not replace the privacy notice that you provide to people who interact with your agent.
Data processing by channel
Use this table as a review checklist. Confirm each category against your live configuration and current AVV before you publish your notice.
Your prompts, knowledge sources, uploaded documents, integration data, conversations, calls, and transcripts are customer content. Humanizing processes this content for your organization under the AVV.
Before you go live
1
Conclude the AVV
Conclude the AVV before Cosmo processes customer content or end-user personal data for your organization. Request the current AVV.
2
Document your processing
Define the purpose, legal basis, data categories, recipients, retention period, and deletion process for your actual configuration.
3
Inform end users
Clearly state that the person is interacting with an AI system. Make your privacy notice available at each relevant interface. Start with the privacy notice template.
4
Check Voicebot requirements
Assess the rules that apply to telephone services, call recording, consent, caller identification, and emergency communications. Do not describe a call as recorded unless recording is enabled and your organization has established a lawful process.
5
Verify the live experience
Test the final notice, links, opening message, enabled channels, and retention settings in the deployed experience.
Public legal documents
Web App Privacy Notice
How Humanizing processes Cosmo account, administration, billing, and support data.
B2B Terms
Contract terms, customer duties, and the separate AVV requirement.