Privacy Policy
Privacy practices for a healthcare AI workflow platform.
This policy describes how CouncilAI handles account information, clinical workflow content, audit logs, and other data used to provide a secure, healthcare-focused AI service.
Healthcare notice
If your organization uses CouncilAI with protected health information, your organization remains responsible for deciding what data is submitted and for meeting its patient-facing legal obligations.
Separate order forms, BAAs, DPAs, and implementation settings may add more specific privacy and security obligations.
Applies to
Clinicians, staff, administrators, and organization representatives using CouncilAI and related support channels.
Data handled
Account details, uploaded documents, prompts, generated content, audit logs, security telemetry, and support records.
Primary uses
Authentication, access control, clinical workflow support, document processing, security, compliance, billing, and support.
Requests
For privacy requests, start with your organization administrator or the CouncilAI contact listed below.
1. Overview and scope
LinkThis Privacy Policy explains how CouncilAI (“CouncilAI,” “Council,” “we,” “our,” or “us”) collects, uses, discloses, and protects information when you access or use the CouncilAI web application, APIs, integrations, document-processing tools, support channels, and related services (collectively, the “Service”).
CouncilAI is designed for healthcare organizations and professionals. Depending on how your organization uses the Service, we may act as a service provider, processor, or business associate to your organization, and your organization may be the party primarily responsible for deciding what information is submitted to the Service.
If your organization has a separate order form, business associate agreement, data processing agreement, or other written contract with CouncilAI, that agreement controls if it conflicts with this Privacy Policy.
2. Information we collect
LinkWe collect information directly from users and organizations, automatically from devices and browsers, and from service providers and integrations that support the Service.
| Category | Examples | Typical purpose |
|---|---|---|
| Account and organization data | Name, email address, role, organization, approval status, multi-factor authentication details, and login history. | Account creation, authentication, RBAC enforcement, support, and administration. |
| Clinical and workflow content | Prompts, chat messages, uploaded files, templates, document metadata, knowledge-base content, and generated outputs. | Document retrieval, summarization, template filling, clinical productivity workflows, and user-requested outputs. |
| Usage, device, and audit data | IP address, browser type, device identifiers, session timestamps, feature usage, search activity, admin actions, and audit logs. | Security, fraud prevention, troubleshooting, analytics, and tamper-evident compliance logging. |
| Support and communications | Emails, tickets, onboarding notes, account notices, and training or implementation feedback. | Customer support, incident response, service updates, and relationship management. |
| Billing and commercial data | Plan details, invoices, payment-related metadata, and contract records. | Subscription management, procurement, tax, and financial reporting. |
3. How we use information
LinkWe use information we collect to:
- Provide, operate, maintain, and improve the Service and its healthcare workflow features.
- Authenticate users, enforce role-based permissions, and manage account provisioning and approval flows.
- Process prompts, documents, templates, search queries, and retrieval-augmented generation requests at the direction of users and organizations.
- Monitor performance, investigate incidents, detect misuse, and maintain system integrity and audit trails.
- Communicate with customers about service updates, support requests, security notices, and account administration.
- Manage contracts, invoices, usage reporting, and other commercial operations.
- Comply with legal obligations, resolve disputes, and enforce our agreements and policies.
- Create aggregated or de-identified analytics where permitted by law and contract and where the data no longer reasonably identifies an individual.
4. AI, document, and knowledge-base processing
LinkCouncilAI uses large language model, document processing, retrieval, and search workflows to respond to user requests. To do that, the Service may temporarily or persistently process prompts, uploaded files, template content, extracted text, metadata, embeddings, citations, and generated outputs.
Depending on configuration, documents may be segmented, embedded, indexed, stored in organization-scoped or conversation-scoped stores, and later retrieved to support search, summarization, drafting, or question-answering.
- Users and organizations are responsible for choosing what content to upload or submit.
- Generated output may reflect the inputs provided, configured models, and retrieved source material.
- AI-generated content can be incomplete or inaccurate and should be reviewed by qualified personnel before clinical, operational, or compliance use.
5. Healthcare and regulated data
LinkThe Service may be used by covered entities, business associates, clinicians, and healthcare staff. If you submit protected health information or other regulated data, you represent that you have the legal authority and contractual basis to do so.
- Your organization remains responsible for patient notices, consents, minimum necessary determinations, and other legal obligations that apply to the data it chooses to submit.
- Where applicable, a separate business associate agreement, data processing agreement, or similar contract governs additional privacy and security commitments for regulated data.
- The Service is not intended for direct-to-consumer patient emergency communications or automated clinical decision-making without human review.
8. Data retention
LinkWe retain information for as long as reasonably necessary to provide the Service, honor customer instructions, comply with legal and contractual obligations, maintain audit and security records, resolve disputes, and enforce our agreements.
- Customer content may remain available until deleted by the customer, removed under retention settings, or deleted at the end of the contractual relationship.
- Audit, fraud-prevention, and security logs may be kept longer where needed for compliance, incident response, or legal obligations.
- Backups and archived copies may persist for a limited period before they are overwritten or deleted.
9. Security and safeguards
LinkWe maintain administrative, technical, and physical safeguards designed to protect information against unauthorized access, use, alteration, and disclosure. These measures may include encryption in transit, access controls, session management, role-based permissions, audit logging, environment segregation, and monitoring for suspicious activity.
No security program can eliminate all risk. You are responsible for safeguarding your devices, credentials, and any local copies of information exported from the Service.
10. Your rights and choices
LinkDepending on your relationship with CouncilAI and the laws that apply, you may have the right to request access to, correction of, deletion of, export of, or restriction of certain personal information.
- If your account is provided through a healthcare organization or employer, start by contacting your organization administrator or privacy office because that organization may control the account and submitted data.
- We may request information needed to verify your identity and authority before processing a request.
- We may decline or limit requests where required or permitted by law, contract, security obligations, or the rights of others.
11. International transfers
LinkCouncilAI may use service providers or infrastructure in the United States and other countries. If information is transferred across borders, we take steps designed to ensure the transfer is subject to appropriate safeguards consistent with applicable law and contractual commitments.
12. Children
LinkThe Service is intended for professional and organizational use, not for children. We do not knowingly offer the Service directly to children or knowingly collect personal information from children for consumer use of the Service.
13. Changes to this Privacy Policy
LinkWe may update this Privacy Policy from time to time. When we do, we will post the updated version on this page and update the effective date above. If changes are material, we may also provide additional notice, such as within the Service, by email, or through your organization administrator.
14. Contact us
LinkFor privacy questions, data requests, or complaints, contact your designated CouncilAI support contact or organization administrator. If you use CouncilAI through a healthcare organization, you should generally contact your organization administrator, privacy office, or designated support channel first.