Allo

Call Recording Compliance

Configure Allo's compliance tools for call recording laws in the US, EU, and beyond

Updated on

Allo's compliance tools

Allo gives you four tools to stay compliant with recording laws. Mix and match based on your needs.

The consent message plays to inbound callers before the call connects, for example: "This call is recorded for quality and training purposes." The consent message works on inbound calls only. Allo does not play a consent message on outbound calls.

Who it's for: Teams receiving inbound calls that need to notify callers.

How it works:

  • You set it up yourself, as a Play announcement step in the line's call flow
  • Placed first, right after Incoming call, the message plays before the phone rings, so the caller hears it before anyone picks up
  • You write the wording, and can record it, upload an audio file or let Allo read the text out
  • It applies per line: add the step to every line that needs a consent message

Open the line's call flow

Go to web.withallo.com, then Settings and Numbers, and pick the line. In the Call flow section, select Open designer.

Or open the call flow in Allo directly, then select Open designer.

Add a Play announcement step first

Make Play announcement the first step after Incoming call, before any menu or ringing step.

Write the message

Write the consent text. The text is required, even if you then add a recording or upload a file. See recordings and audio.

Save

Select Save. The message plays from the next call. Call the line yourself to check it.

For more on the designer, see call flows.


US recording laws

Federal law (one-party consent) allows recording if one party consents. But when calls cross state lines, the stricter state's law applies. For outbound sales teams calling all 50 states, this matters.

Recommendation for outbound sales teams

If your team calls all 50 US states:

  1. Enable consent message for all inbound calls, which covers you everywhere
  2. Enable privacy mode for outbound calls: no audio stored, transcripts + AI summaries still sync to your CRM
  3. Train your team to verbally disclose recording at the start of outbound calls to dual-consent states

This gives you the best of both worlds: full AI intelligence for sales coaching, zero audio liability.

Coming soon: state-level automatic compliance

Allo is building area-code-based compliance rules. This will let you automatically apply different recording settings based on the state you're calling.

Example: Calls to California numbers automatically use privacy mode, while calls to Texas numbers record normally.

This feature is on the roadmap. Contact support for updates or to join the early access list.


EU & international

GDPR / European Union

Recording requires a legal basis, typically consent or legitimate interest.

Key requirements:

  • Inform callers before recording starts
  • Document your legal basis
  • Provide access to recordings on request
  • Honor deletion requests (right to erasure). GDPR recommends 30 days
  • Data processing agreement (DPA) available from Allo

France (CNIL):

  • CNIL enforces strict consent rules
  • Consent must be freely given, specific, and informed
  • Recordings used for training must be anonymized or consented to separately
  • Allo's Mistral AI option keeps processing with a European provider

Visit our Trust Center

Canada (PIPEDA)

Federal PIPEDA follows one-party consent for calls. But provincial laws add requirements:

  • Quebec: Stricter privacy law (Law 25). Consent required for recording.
  • British Columbia & Alberta: PIPA applies. Similar to PIPEDA but with provincial enforcement.

Recommendation: Enable consent message for all Canadian inbound calls.

Other countries

Recording laws vary widely. For country-specific guidance:

  • Check local telecommunications authority rules
  • Consult legal counsel in target markets
  • Contact Allo support for configuration help

Allo supports numbers in 50+ countries. We can configure compliance settings per number.


AI & transcription compliance

Real-time transcription and AI analysis receive the same legal treatment as call recording. The same consent that covers recording also covers transcription.

Key considerations:

  • BIPA (Illinois): Speaker identification (voiceprints) may qualify as biometric data under BIPA. If you handle calls with Illinois residents, consult legal counsel about biometric consent.
  • AI disclosure laws: California (AB 2013) and Texas require disclosure when AI is used to analyze calls. Your consent message should mention AI analysis.
  • AI-generated summaries: Treated as derived data. Same retention and access rules apply as for recordings.

Data retention

Default: Recordings and transcripts are kept indefinitely in your Allo account.

Custom retention: Contact Allo support to set auto-deletion after a specific number of days.

Regulatory benchmarks:

RegulationGuideline
GDPRDelete when no longer necessary. 30 days recommended for call recordings.
CCPARespond to deletion requests within 45 days.
HIPAA6-year retention minimum. BAA available for healthcare customers.
SOX7-year retention for financial records including call records.

FAQ

Can I keep transcripts but delete recordings?

Yes. Enable Privacy Mode: audio is never stored, but transcription and AI summaries work normally. Transcripts sync to your CRM as usual.

Can I set compliance rules per state or area code?

Not yet. This feature is on the roadmap. For now, contact support to configure privacy mode per line or user.

Can callers opt out of recording mid-call?

Not yet via an automated mechanism. Agents can manually note opt-outs. Contact support for custom workflows.

Where is my data stored?

Encrypted at rest and in transit on Allo's secure infrastructure. SOC 2 compliant. Visit our Trust Center for details.

What about HIPAA?

We sign a Business Associate Agreement (BAA) with healthcare businesses. It is a paid add-on on the Business and Ultra plans.

HIPAA and BAA →

Can I auto-delete recordings after X days?

Yes. Contact support to configure custom retention periods. Common settings: 30 days (GDPR), 90 days, or 1 year.


Need help?