Skip to content
Adoptiv

Recordings, transcripts and consent - handled properly.

A calling platform holds some of the most sensitive material a business has: what customers actually said. Here is how that is protected, and what we have not certified yet.

GDPR
Processing addendum published
TCPA tooling
Included
SOC 2
Audit in progress
Hosting
Germany, US available

Stated plainly: the SOC 2 audit has not completed, there is no HIPAA business associate agreement, records sit in a single region rather than one you pick, and there is no setting yet that expires recordings or transcripts on a schedule. If any of that has to be in place before you can sign, tell us and we will give you the current timeline rather than a maybe.

Before the dial

The screening runs twice.

A list checked once at import goes stale, because numbers move onto the do-not-call register between your import and your campaign. So Adoptiv screens the list on the way in, and screens the number again on the automated outbound paths before it dials. Anything arriving the other way can carry the same checks inside its call flow.

Trip a check - the gate runs before the dialClear to dial

Every check passes, so the call places. The same checks run on calls coming in, and on calls another system asks for.

Controls

What you can actually configure.

Data

  • Encryption in transit
    TLS 1.2 or better on every connection, including the one carrying the audio.
  • Encryption at rest
    AES-256-GCM on the credentials and tokens we store for you. Disks and recording storage use the provider’s own at-rest encryption.
  • Tenant isolation
    Each customer’s records live in their own database schema, created with the account.
  • Separate audio channels
    Each side of a call records to its own channel, so a review can tell who said what.

Access

  • Role hierarchy
    Roles inherit down a tree you define, not a flat list.
  • Single sign-on
    SAML, plus Google and Microsoft, configured per tenant.
  • Sharing rules
    Grant cross-team access by rule rather than by exception.
  • Audit trail
    Who changed what, when, and what the value was before.

Calling

  • DNC screening
    Federal and internal registers, checked when the list lands and again before an automated call dials.
  • Litigator lists
    Known-litigator numbers flagged on the record, and a call flow can be set to drop them.
  • Calling windows
    Business hours and holidays enforced against your organisation’s time zone.
  • Abandonment cap
    Set per campaign, defaulting to 3%.
The pack

Everything a review asks for, already written down.

No form, no non-disclosure agreement before you can read a control, and no waiting for somebody to reply. If a question is not answered by one of these, write to security@adoptiv.com and we will answer it rather than send you a questionnaire.

If you connect a mailbox

Connecting Gmail or Microsoft 365 gives Adoptiv access to that mailbox, so it gets its own page rather than a line in a policy. We request one Gmail scope rather than several, tokens are encrypted at rest, and disconnecting revokes the token with Google and deletes the mail we hold that is not attached to a record.

Google user data policy →What we store, and for how long →

Security

Bring the questionnaire. We will fill it in.

Send the spreadsheet your procurement team uses and we will complete it against the pages above, then get on a call with whoever needs to sign it off.

Book a demoSee pricing

14-day trial · no card · migration included