Privacy at Adoptiv
clear, accountable, and CRM-aware.

This page summarizes how we handle personal data when you use Adoptiv for CRM, telephony, and automation — what we collect, why we use it, your choices, and how to reach us. It is not a substitute for legal advice or your DPA.

Privacy themes that map to the product.

Each block reflects how operators actually configure tenants — not generic SaaS boilerplate alone.

Information we collect

Account, billing, usage, communications, and content your users submit into the platform — including CRM records and call metadata.

Registration and profile details
Workspace and tenant configuration
CRM entities you create or import
Telephony metadata, recordings when enabled
Support tickets and diagnostics

How we use information

Provide, secure, and improve the service; troubleshoot; comply with law; and communicate about updates relevant to CRM and voice workloads.

Service delivery and authentication
Fraud prevention and abuse detection
Product analytics in aggregated form
Customer success and transactional email
Legal and regulatory obligations

Sharing & subprocessors

We share data with infrastructure and service providers who help us run Adoptiv — under contracts with confidentiality and security obligations.

Hosting and database providers
Email and notification vendors
Payment processors for billing
Support tooling with access controls
Updated subprocessor lists for customers

Your rights

Depending on jurisdiction you may access, correct, delete, export, or restrict certain processing — we honor applicable requests after verification.

GDPR-style rights where applicable
US state privacy rights where applicable
Appeal processes where required
Identity verification to protect accounts

International transfers

Data may be processed in the United States and other regions where we operate — using safeguards such as Standard Contractual Clauses when required.

Transfer impact assessments as needed
Customer DPAs for processor relationships
Documentation for enterprise legal teams

Retention & security

We retain data as long as needed to provide the service and meet legal duties — secured with encryption and access controls described in our Security overview.

Tenant-driven deletion workflows
Backup retention windows
Encryption in transit and at rest
Alignment with SOC 2 / ISO programs
app.adoptiv.ai / privacy

Who relies on this policy

Legal, security, and RevOps leaders reference privacy alongside technical controls.

Procurement & legal

Pair this summary with your DPA, order form, and regional addenda for a complete picture.

CX leadership

Understand how recordings, transcripts, and support data interlock with customer commitments.

Regulated industries

Use as a starting point — then layer HIPAA, financial, or regional programs with counsel.

Employees & admins

Workspace owners should know what profile and audit data exists for their org.

Related security resources

Privacy and security are adjacent — jump to the page your review needs.

01

Security overview

  • Encryption, uptime, and tenant isolation.
  • How technical controls support privacy claims.
02

Trust Center

  • Testing, incidents, and transparency.
  • How to engage our security team.
03

Certifications

  • SOC 2 Type II and ISO 27001 evidence.
  • Supports privacy-by-design narratives.
04

Compliance

  • TCPA, GDPR, HIPAA-ready themes.
  • Operational controls for regulated outreach.
Privacy Policy

Privacy cannot be an appendix to your CRM rollout.

When voice, AI, and CRM share one datastore, data subjects and regulators expect clarity. This policy is written to align with how Adoptiv actually processes information — so your legal team can bridge to DPAs and internal notices.

Start Free Trial
Adoptiv platform security

Request the full legal pack

Need executed DPAs, subprocessors, or SCCs? Contact [email protected] with your entity details and timeline.

Email [email protected]

See controls in action

Watch how RBAC, retention, and export tools map to the commitments in your agreement.

Schedule Demo

Putting policy into practice

Three steps teams follow after reading.

1

Align internal notices

Update employee and customer-facing language to reference Adoptiv processing activities.

2

Open a privacy thread

Email [email protected] for DPA execution, transfer questions, or data subject escalations.

3

Configure the tenant

Apply RBAC, retention, and integrations so day-to-day behavior matches your policy choices.

FAQ

Everything you need to know about Adoptiv

Quick answers to what sales teams ask most before getting started with Adoptiv.

SOC 2 & ISO 27001
3× Faster Dialing
10,000+ Teams

We process account, billing, usage, support, and communications data needed to operate the service — including metadata generated by CRM and telephony features your workspace configures.

Customer content you store in tenants (contacts, calls, recordings) is treated according to your agreement and role as controller or processor. We use aggregated telemetry to improve reliability and security.

Yes — submit requests via [email protected] or your account team. We verify identity and respond within statutory timelines, subject to exceptions allowed by law.

We use cookies and similar technologies where needed for authentication, preferences, and analytics on adoptiv.com properties. You can control many preferences through your browser.

Production systems run in audited data centers with encryption in transit and at rest. Enterprise customers may discuss regional needs during contracting.

Email [email protected] for privacy-specific questions and [email protected] for security incidents. We coordinate responses across teams when issues overlap.

Questions about privacy?

We connect privacy, security, and customer success so CRM and telephony deployments stay explainable to your stakeholders.

No credit card required
Cancel anytime
100% Human Support
Adoptiv privacy and data protection