Trust · Recording & retention
A recording policy must identify which calls are eligible, who may access them, how long each applicable copy should remain, where it is stored, and who administers deletion and downstream use.
Configuration-specific: This page publishes no default or maximum retention period, storage allowance, recording rule, format, security or compliance assurance, legal conclusion, service level, or price.
Basic CDR, ACD reporting, enhanced reporting, PBX recording, recording retention, and post-recording handling remain distinct layers.
Verified service boundaries
The configured PBX recording service creates eligible audio. Recording is not implied by the presence of call-detail or reporting data.
Must be definedEligibility, notice, consent, policy, access, source behavior, and applicable legal guidance.
When the enhanced retention option is selected, recording-retention duration can be configured using extension, call direction, and call type.
Must be definedThe exact rules, applicable recordings, desired duration, access, deletion behavior, and resulting configuration.
Heritage’s recording handler can copy eligible recordings to compatible customer-designated Amazon S3-compatible storage, Backblaze B2, or SFTP.
Must be definedDestination administration, credentials, access, lifecycle rules, permitted content, available storage, deletion, and failure handling.
Copy-by-copy review
Copying a recording beyond the source service’s configured window can support long-term retention, but it does not make the destination automatically permanent.
Determine whether the call may be recorded and processed under the customer’s approved policy and applicable requirements.
Confirm how the selected PBX recording service creates, exposes, retains, and deletes the eligible audio.
Confirm whether the handler sends a compatible copy to the approved customer-designated destination.
Define who controls access, retention, deletion, capacity, credentials, monitoring, and response when delivery or storage fails.
Customer policy and legal review
The customer must establish appropriate notice, consent, authorization, internal policy, access, purpose, retention, and deletion requirements. Recording or copying audio to another destination broadens the data flow and requires review before activation.
Heritage does not use this page to state that one configuration satisfies a law, regulation, industry obligation, discovery duty, legal hold, employment policy, or customer contract.
Not inferred
No answer is supplied merely because recording, retention, or a compatible destination is available.
Return to the Trust CenterExact eligibility, audio format, creation timing, default retention, maximum retention, storage limits, deletion, export, and service availability.
Authentication, permissions, administrative access, encryption, logging, monitoring, data location, isolation, and incident handling.
Ownership, credentials, compatibility, capacity, lifecycle rules, backups, deletion, failures, retries, monitoring, and support responsibilities.
Notice, consent, lawful use, discovery, legal hold, compliance, contractual commitments, billing units, amounts, and service levels.
Review the actual requirement
Do not send recordings, transcripts, credentials, private customer information, medical information, or legal material through the public sales form.
