Effective date: November 11, 2026 Last updated: November 11, 2026
Clinet answers phone calls for businesses that cannot afford to mishandle a caller's information. This page explains how we handle data, how our platform is built, and how you can reach our security team. It is written for the people who evaluate us before they trust us: operations leads, compliance officers, and the security reviewers who sign off on new vendors.
Clinet is the trading name of SOCII LABS LLC, a Wyoming limited liability company.
Our approach in one sentence
We designed Clinet to hold as little sensitive data as possible, to keep a clear record of who did what, and to be honest about what we have in place today.
How the platform is built
Clinet does not store call recordings, transcripts, or Protected Health Information. Our voice provider, Retell, is the system of record for call content. When an authorized user needs a transcript or call detail, Clinet retrieves it on demand rather than keeping a copy.
What Clinet stores on its own platform are operational logs: audit logs, request logs, and clinic activity logs. These records are kept free of call content and health information. They let a customer see what happened — which agent ran, when access was granted, what actions were taken — without accumulating sensitive caller data on our side.
This design means that the most sensitive data has fewer places to live, and the record of access stays intact.
Data protection
- Encryption in transit. All traffic between your browser, the Clinet platform, and our providers is encrypted using TLS (HTTPS).
- Access control. Account authentication is handled through our identity provider, Clerk. Access to customer data is scoped to the customer's own organization.
- Audit logging. Access and key actions are recorded in audit logs so activity can be reviewed.
- Least data. Because call content lives with our voice provider and our logs exclude it, a large class of sensitive data never reaches Clinet's storage.
We describe our current measures plainly and do not claim protections we have not implemented. If a specific control matters to your review, ask us at [email protected] and we will tell you where we stand.
Infrastructure and hosting
The Services run on established cloud infrastructure from Amazon Web Services (AWS) and Google Cloud Platform (GCP). Customer data for the Services is hosted in the United States. These providers maintain their own industry security certifications and physical and network safeguards for the infrastructure we build on.
Subprocessors
We use a focused set of providers to deliver the Services, each under a contract that requires them to protect data and use it only to provide their service to us. Our primary providers include Retell (voice and call-content system of record), AWS and GCP (hosting), Clerk (authentication), Twilio and SendGrid (communications and email), Cal.com (scheduling), Twenty (CRM), n8n (workflow automation), and Loops (marketing email). The current list is maintained in our Privacy Policy.
Where our providers process health information on our behalf, we put the required agreements in place with them.
Compliance posture
We are direct about where we are.
- HIPAA. We align our platform and operational practices with HIPAA. We sign a Business Associate Agreement (BAA) with healthcare customers before any Protected Health Information is involved. Because Clinet does not store PHI, the surface area we handle is narrow.
- Certifications. Clinet does not currently hold a third-party security certification such as SOC 2 or ISO 27001. Our infrastructure providers (AWS, GCP) and our voice provider (Retell) maintain their own certifications, and we can share relevant documentation to support your review.
- Privacy law. We handle personal information in line with applicable privacy laws, including GDPR, UK GDPR, and U.S. state privacy laws. A Data Processing Agreement is available for customers who need one.
If your security or procurement team needs documentation — our subprocessor list, a completed security questionnaire, or provider certifications — email [email protected].
Shared responsibility
Security is a partnership. Clinet protects the platform and the data we hold. Customers are responsible for:
- Keeping account credentials confidential and managing who in their organization has access.
- Configuring call recording and retention settings, and the privacy mode of their voice agent, to match their needs.
- Meeting the consent and call-recording laws that apply to their calls and their jurisdiction.
- Choosing what information their callers are asked to provide.
Reporting a vulnerability
If you believe you have found a security vulnerability in Clinet, we want to hear from you.
- Email: [email protected]
- Please include enough detail to reproduce the issue, and give us a reasonable chance to investigate and fix it before any public disclosure.
- Please do not access, modify, or delete data that is not yours, degrade our service, or run automated scans that disrupt other users.
We will acknowledge legitimate reports, keep you updated on our progress, and credit researchers who want recognition. We will not pursue good-faith research conducted under this guidance.
Incident response
If we become aware of a security incident that affects personal information we control, we will investigate, take steps to contain and remediate it, and notify affected customers and authorities as required by law and by our agreements.
Contact
Security team and vulnerability reports: [email protected] Compliance: [email protected] Privacy: [email protected]
SOCII LABS LLC (trading as Clinet) 30 N Gould St, Ste R Sheridan, Wyoming 82801 United States