Privacy Policy
Last Updated: May 8, 2026
This Privacy Policy explains how ClinicianCompanion may collect, use, protect, retain, delete, and share information across websites, applications, APIs, PWAs, dashboards, prototypes, mobile experiences, and client services.
Information we may collect
Depending on the service, we may collect contact form submissions, account data, project data, uploaded files, technical logs, analytics data, cookies or local storage, email communications, support records, service records, and information needed to operate requested workflows.
For research, prototype, health-adjacent, or client-service workflows, data handling depends on the specific written scope and should not be treated as a regulated clinical workflow unless separately agreed.
How information is used
Information may be used to provide services, respond to requests, maintain accounts, support projects, improve reliability, debug errors, secure systems, maintain records, provide notices, and comply with applicable contractual or legal obligations.
Storage, protection, and retention
Reasonable administrative, technical, and operational safeguards are used where applicable, including access controls, least-privilege practices, logging, backups where appropriate, and deletion/export workflows where feasible. Retention periods vary by service type, contract, legal need, operational need, and user request.
Sharing and processors
Information may be shared with service providers, infrastructure providers, security tools, analytics providers, professional advisors, or client-authorized systems as needed to operate the service. Data is not sold as a standalone product. A Data Processing Addendum may be available for eligible client relationships.
HIPAA and BAA availability
Do not assume HIPAA compliance for a workflow unless it is documented in a written agreement. Audia Systems LLC maintains Business Associate Agreement templates for eligible healthcare, research, clinical, and covered-entity clients. Because every client relationship, technical implementation, and regulatory obligation is unique, BAAs are typically reviewed, developed, or modified to reflect the specific services, data flows, security requirements, compliance obligations, and operational responsibilities associated with a particular engagement.
Contact and operator
For privacy, security, accessibility, support, DPA, BAA, and policy questions, contact [email protected].
Operated by Audia Systems LLC, DBA Bailey Enterprises, within the broader GLC / Gwyn Legacy ecosystem.