Skip to content
Clovr

Trust center

Trust at Clovr.

Clovr handles sales conversations, the most candid version of how your team talks to customers. Treating that data with care isn't a feature, it's the job. This page documents how we collect, protect, and give you control over what we hear.

Minimize what we collect

We only record calls you have set up to be recorded: calls a rep starts from the app, or calls to a store line you route through Clovr Coach. Default retention is 90 days for audio, 24 months for transcripts. Both can be tightened workspace-wide.

Protect what we have

TLS 1.3 in transit, AES-256 at rest, mandatory MFA for every internal account. Production access is limited to a small, named group with audit logging on every read.

Give you control

Export your data any time. Delete a single recording or your whole account. See who in your team accessed what and when. You own the tape, not us.

Compliance

Certifications and data flow.

Clovr is built on infrastructure that collectively holds the certifications below.

SOC 2 Type II

Across every production system

ISO 27001

Hosting, edge, and source control

ISO 27017

Cloud-specific security

ISO 27018

Cloud-specific privacy of PII

HIPAA

Speech-to-text inference

HIPAA-eligible

Database and object storage

GDPR

All processing of EU personal data

PIPEDA

All processing of Canadian personal data

CCPA

All processing of California personal data

Where your data lives, by service.

The functional role, hosting region, and compliance posture of each system involved in delivering Clovr, without identifying the specific providers.

Service & purposeRegionCompliance
Application hosting and edge deliveryUSA (multi-region)SOC 2 Type II, ISO 27001
Primary database, object storage, backupsCanada (Toronto)SOC 2 Type II, HIPAA-eligible
Speech-to-text inferenceUSASOC 2 Type II, HIPAA
Large language model inferenceUSASOC 2 Type II
Identity and end-user authenticationUSASOC 2 Type II
DNS, CDN, DDoS protectionGlobal edgeSOC 2 Type II, ISO 27001
Transactional email deliveryUSASOC 2 Type II
Source control and dependency scanningUSASOC 2 Type II, ISO 27001

Live posture

Security controls, in production.

Every panel below is operational today. Each is monitored continuously; status reflects the current state of the system.

Infrastructure

Live
  • Application runs on a SOC 2 Type II cloud edge platform; traffic is served from the region closest to each user.
  • Production database is a SOC 2 Type II managed Postgres environment in a Canadian region (Toronto).
  • Daily encrypted database backups with 7-day point-in-time recovery.
  • DNS, edge caching, and DDoS protection through a SOC 2 Type II / ISO 27001 edge provider.
  • No customer data on developer laptops; all production access happens through hosted, audit-logged dashboards.

Encryption

Live
  • TLS 1.3 enforced for all transport. HTTP requests redirect to HTTPS, with HSTS enabled.
  • AES-256 for data at rest across the database, object storage, and backups.
  • Recorded audio files are private by default and accessed only through short-lived signed URLs.
  • Secrets and API keys held in encrypted environment vaults; never in source control or developer machines.

Authentication & access

Live
  • Customer authentication managed by a SOC 2 Type II identity provider, with optional MFA for end users.
  • Mandatory MFA for every Clovr team member on every internal production system.
  • Principle of least privilege: production database access is limited to founders plus a named on-call engineer.
  • Row-level security policies scope every database query to the authenticated organization.
  • Role-based access in the dashboard so reps, managers, and admins each see only what they should.

Application security

Live
  • Automated dependency scanning on every change, with critical advisories blocking the build.
  • Every change runs through CI before deploy: linting, automated correctness checks, and a production build, plus the full deterministic test suite on the messaging engine.
  • Content Security Policy and modern security headers on every customer-facing surface.
  • Authenticated API routes verify the session on every request; no anonymous writes.
  • A failing test, lint error, or critical dependency advisory blocks the deploy.

Data minimization

Live
  • We only record calls a store has set up to be recorded: calls a user starts from the Clovr app, and calls to a store phone line the dealership routes through Clovr Coach. Recording notices follow the rules where the store operates.
  • Default retention is 90 days for raw audio and 24 months for transcripts. Both are configurable down to 7 days for audio.
  • Customer recordings are never used to train AI models, neither ours nor any third party's. Contractually enforced with every inference provider.
  • PII redaction available on transcripts before they're shared outside the team.

Privacy & consent

Live
  • Recording consent prompt is configurable per jurisdiction (one-party vs. two-party consent).
  • Audible disclosure available for two-party consent jurisdictions.
  • Data subject access requests (PIPEDA, GDPR, CCPA) honored within 30 days; contact hello@useclovr.ai.
  • Data residency: customer data stored in Canadian regions by default. EU residency available on enterprise plans.

SMS messaging (Clovr Dealr)

Live
  • Clovr Dealr is our text-messaging assistant for automotive dealerships; it responds, on the dealership's behalf, to people who inquire about vehicles.
  • Consent is collected at the point a person submits an inquiry. Opt-out (reply STOP) is honored immediately and permanently, and HELP returns support information.
  • No mobile opt-in data is ever shared with third parties or affiliates for marketing. Numbers are shared only with the service providers that deliver the messages, solely to operate the program.
  • An automated assistant helps respond, with a dealership team member available to follow up. Message frequency varies and message and data rates may apply; consent is never a condition of purchase.

Personnel & operations

Live
  • All Clovr employees and contractors sign confidentiality and acceptable-use agreements before access is granted.
  • Background checks for any role with production access.
  • Annual security awareness training, including phishing drills.
  • Quarterly access reviews; departing personnel are deprovisioned the same day.

Incident response

Live
  • Documented incident response plan with defined severity tiers and communication paths.
  • On-call rotation for the engineering team; uptime monitoring across hosting and database.
  • Material incidents communicated to affected customers within 72 hours of confirmation, in line with PIPEDA breach reporting expectations.
  • Public post-mortem published for any incident that impacts customer data or causes meaningful downtime.

Frequently asked

The questions we get most.

Does Clovr record my sales calls?

Only the ones you have set up to be recorded: calls a rep starts from the Clovr app and, if your store routes its phone line through Clovr Coach, calls to that line, with a recording notice wherever the law requires one. Nothing else is captured.

How long do you keep the recordings?

By default, raw audio is retained for 90 days and transcripts for 24 months. Both windows are configurable down to as little as 7 days for audio and 90 days for transcripts on any paid plan.

Who at Clovr can see my data?

Production database access is limited to two founders and a named on-call engineer, and we keep an audit log of every admin query. Routine support is handled without engineers needing to read transcript content unless you explicitly grant access on a specific ticket.

Do you use my recordings to train AI models?

No. Customer recordings, transcripts, and coaching artifacts are never used to train Clovr models or any third-party model. This is contractually enforced with every inference provider we use, and is the default on the plans we operate under.

Where is my data stored geographically?

Customer data is stored in a Canadian region (Toronto) by default. EU residency is available on enterprise plans by request. AI inference happens in the US; only the audio for the specific call being processed transits there, never the broader dataset.

How is consent handled for call recording?

Recording consent is configurable per workspace and per jurisdiction. We support a one-party-consent mode (silent disclosure) and a two-party-consent mode (audible disclosure plus written notice). The product warns reps when they're calling into jurisdictions that legally require two-party consent.

Do you share phone numbers or SMS opt-in data?

No. For the Clovr Dealr text-messaging program, mobile information and opt-in consent are never shared with third parties or affiliates for marketing. Numbers are shared only with the service providers that deliver the messages, solely to operate the program.

How does someone stop receiving texts from Clovr Dealr?

Reply STOP to any message. Opt-out is immediate and permanent unless the person opts back in. Reply HELP for help, or call (905) 288-8210.

Is the dealership messaging automated?

Clovr Dealr uses automated technology to help respond to vehicle inquiries, with a dealership team member available to follow up. Message frequency varies, message and data rates may apply, and consent is never a condition of purchase.

Are you GDPR, PIPEDA, and CCPA compliant?

Yes. We honor access, correction, deletion, and portability requests from any data subject in any jurisdiction. Send the request to hello@useclovr.ai and we'll fulfill it within 30 days, sooner where statutorily required.

Can I get a copy of all my data?

Yes. Workspace admins can request a full export at any time. The export ships as a downloadable archive containing audio (original format), transcripts (JSON), and coaching artifacts (JSON), with a manifest mapping each record to the original call.

What happens to my data if I cancel?

On cancellation we retain your data for 30 days in case you reactivate, then hard-delete everything: database rows, audio files, search indices, and backups (purged on the next backup rotation, no later than day 37). You can request earlier deletion at any point.

Do you support SSO?

Yes. Google Workspace and Microsoft Entra ID are supported on every plan. SAML for other identity providers is available on enterprise plans.

Do you perform penetration testing?

Third-party penetration testing is planned. Day-to-day we rely on continuous static analysis, dependency scanning, and routine internal red-teaming.

How are admin actions logged?

Every dashboard write produces an immutable audit event. Workspace admins can review who viewed, exported, or deleted a recording from the audit log in settings, with a 12-month retention window.

What's the easiest way to get a DPA or security questionnaire signed?

Write to hello@useclovr.ai. We typically return signed documents within two business days.

Updates

Recent changes.

Material changes to controls, compliance, or data handling get logged here. Anything else, write to hello@useclovr.ai.

April 2026

Mandatory MFA for Clovr team accounts

Every internal account on every production system now requires a hardware-backed second factor.

March 2026

Configurable retention windows

Workspace admins can now set per-workspace retention for raw audio (down to 7 days) and transcripts (down to 90 days).

February 2026

Row-level security audit

Completed a full review of database access policies; added missing scoping to two read paths and added regression tests for every table.

January 2026

Trust Center published

First public version of this page. Tracking real controls, real compliance, real gaps.

Resources

Documents and contact.

Privacy Policy

How we collect, use, store, and share personal data across the Clovr platform.

Read policy

Terms of Service

Service-level commitments, acceptable use, and contractual terms for using Clovr.

Read terms

Request documents

DPA, subprocessor list with provider identities, security questionnaires (SIG Lite, CAIQ Lite), and our providers' SOC 2 reports, all available under NDA.

Email us

Talk to a human

Vulnerability disclosure, custom DPA terms, enterprise residency questions, anything else.

hello@useclovr.ai

We answer them ourselves.

Security inquiries go to a person on our team, not a ticketing queue. Reasonable response time is one business day; vulnerability reports get the fastest response we can manage.

Get in touch