Clingeo · Legal & Trust
Security at Clingeo
Product safeguards, customer responsibilities, and security reporting.
Draft reviewed November 21, 2026
Clingeo is a business tool for clinic marketing analysis and content workflows. This page describes source-supported product safeguards and the boundaries of security claims; it is not a certification or service-level agreement.
1. Data scope
Clingeo is a business marketing and content service, not a patient-record, patient-intake, appointment-management, or clinical-care system. Do not submit patient records, identifiable patient case histories, HIPAA protected health information (PHI), or other sensitive information about identifiable patients. Public availability does not make a patient story appropriate for upload.
Clinic-site measurement requires an approved installation scope and an assessment of visitor-data context. The absence of a patient database does not make all visitor events anonymous or automatically outside health-data requirements.
2. Product access safeguards
The application includes authenticated workspace access, account and project scoping, permission checks for content operations, and database row-level access policies. Privileged service operations require separate access controls. Review and publishing permissions depend on the relevant roles and workflow state.
These source-supported features do not by themselves prove the effectiveness of every production control, deployment configuration, staff-access practice, or incident process.
3. Integration credentials
The WordPress connector implementation encrypts application passwords with AES-256-GCM before storage. That statement concerns those connector credentials; it is not an assertion of end-to-end encryption or application-level encryption of every record. Protect and revoke customer integration credentials when they are no longer needed.
4. Suppliers and operational assurance
External infrastructure and processing services are involved in delivering the product. The supplier register and DPA must reflect actual services, regions, access, retention, and security schedules.
Claims about transport or at-rest controls, MFA, key management, backup restoration, penetration tests, SOC 2, ISO certification, or uptime require current evidence for their stated scope. No such certification, blanket HIPAA warranty, or contractual response time is created by this page.
5. Customer responsibilities
- Use individual accounts and the least access needed for each person.
- Protect credentials and remove unused team members or integrations.
- Review content, sources, and permissions before publication.
- Keep patient information, secrets, and unnecessary personal information out of inputs and support messages.
6. Reporting a concern
Use the contact page for a general inquiry or to ask for an appropriate privacy, legal, billing, accessibility, or security contact. Do not send patient information, credentials, identity documents, or other sensitive evidence through an ordinary inquiry. A secure follow-up method must be arranged where needed.
Ask for a security reporting route and describe the affected feature at a high level. Arrange a secure channel before sharing sensitive evidence. This page is not authorization to test systems, access another tenant’s data, perform disruptive scans, or participate in a bug bounty. The operator must identify a monitored reporting contact and triage process.
Contact and related documents
Contact Clingeo for an appropriate inquiry route. Please do not include patient information or credentials.