Privacy Policy
How AREEP collects, uses, and protects data — including healthcare-sensitive knowledge and conversations.
Last updated: 2025
This Privacy Policy explains how AREEP ("we", "our", "us") handles information when you use our AI-powered medical communication and knowledge platform (the "Service"). We process data to operate the Service securely and responsibly, with particular care because the Service may handle healthcare-related knowledge and conversations.
1. Information We Collect
1.1 Account data
When your organization uses the Service, we collect account data needed to create and manage workspaces, including names, work emails, roles, and workspace configuration.
1.2 Conversation data
The Service processes conversations routed through connected channels (such as WhatsApp, Telegram, Messenger, and web). This includes messages exchanged with AI agents and your team, which are stored so conversations can continue with context.
1.3 Uploaded knowledge files
Clients upload drug, product, and medical documents to build their knowledge base. These files are stored and indexed so AI agents can answer using retrieval-augmented generation (RAG). They are used only for the client's own workspace.
1.4 Usage analytics
We collect operational analytics such as message volume, token usage, deflection rates, escalations, and report output, to operate the Service and provide the dashboards and reports you rely on.
2. How We Use Data
- To provide, operate, and maintain the Service, including AI agents, retrieval, escalation, and reporting.
- To secure accounts and workspaces, including access control and abuse prevention.
- To produce the analytics, gap reports, and recommendations available in the product.
- To support and improve the Service in line with this policy.
We do not use your knowledge files or conversations to train models shared with other clients. Uploaded knowledge is used to power retrieval for your own workspace only.
3. Tenant Isolation
The Service is architected around strict tenant isolation. Knowledge files, conversations, settings, and API credentials for one client are separated from all other clients. This isolation is a core design principle, enforced at the platform level.
4. Security Measures
We apply reasonable administrative, technical, and organizational measures to protect data, including role-based access, separated credentials, access logging, and secure deployment practices. For more detail, see our Security overview.
5. Data Sharing
We do not sell personal data. We share data only with service providers who process data on our behalf to operate the Service, subject to confidentiality obligations, or where required by law.
6. Retention
We retain data for as long as needed to provide the Service and meet contractual and legal obligations. Contact us to discuss retention for your workspace.
7. Your Rights and Choices
Depending on your region, you may have rights to access, correct, export, or request deletion of your data. To exercise these rights, contact us using the details below.
8. Contact for Privacy Requests
For any privacy request or question, contact us through the Contact page or your account team. We will respond in a reasonable timeframe.
9. Changes to This Policy
We may update this policy from time to time. Material changes will be communicated through the Service or our website.