Trust center
How Loops protects the calls you send us
Loops reads your agents' calls to grade them. Here is exactly what it can touch, where the data lives and who can see it.
Need security answers, our subprocessor list or an agreement to review? Choose "Security packet" on the form and we'll reply with what we have.
Compliance
SOC 2
Planned Loops has not been audited yet, so there is no SOC 2 report to share.
HIPAA
Loops takes no health information until a BAA with you is signed.
GLBA
For lenders and servicers, a DPA is available on request to support your Safeguards Rule oversight of service providers.
Agreements on request
Ask for an NDA and DPA and sign them before any key changes hands. We complete your security questionnaire on request.
Your regulations
Loops checks calls against the FDCPA, Reg F, TCPA and HIPAA rules you approve. It doesn't read dial logs or consent records, so it can't check rules that need them, such as call frequency and consent. It supports your program; it doesn't replace your counsel.
Access to your platform
- Reads finished calls. That means transcripts, tool-call records and call details from your platform, plus human calls you upload as transcripts. Loops stores no audio. All of it is covered by the same storage, encryption, retention and deletion terms below.
- The narrowest key your platform allows. Where a key can be limited to reading, as on Retell (History: Read) and ElevenLabs, give us that one. Where it can't, as on Vapi, we recommend sending finished calls by webhook and giving us no key at all; if you'd rather give a key, Loops uses it only to read calls.
- Never writes to your agent. Loops' connectors can only read: they refuse any request that would change a prompt, flow, setting or phone number. Your team makes every change.
- Places no calls. Loops reads only calls your agent has already made, and compares releases on live calls.
- Revoke any time. Revoke the key and Loops stops at once.
Your data
- Stored in the US. Call data is stored on systems in the United States. The team that may access it works from India.
- Encrypted with TLS 1.2 or higher between your browser or platform and Loops, and AES-256 at rest.
- No training. Loops trains no model on what you send, and no call text reaches a model provider until a written data processing agreement with that provider is in place.
- Retention you set, and deletion on request. You keep your report whether or not you continue after the free audit.
- Logged views. Each time someone opens a call in Loops, it is written to your workspace's access log.
- Subprocessors. The list is available on request.
This website
- The site's own code sets no cookies and runs no analytics, and its fonts are served from useloops.ai itself. The one script from elsewhere is Cal.com's booking calendar, on /call. See the cookie policy.
- HTTPS everywhere, with a content security policy, HSTS and frame, referrer and content-type protections.
- Policies: privacy, cookies, terms.
Report a security issue
If you believe you've found a vulnerability, tell us through the form (choose "Report a security issue"; no industry needed) and we'll reply with a secure way to send the details. Please give us reasonable time to fix it before sharing it publicly, and don't access data that isn't yours. We won't take legal action against good-faith research that follows this policy. Our security.txt points here.