Handbook
Genesys Cloud recording, retention, redaction and subject access
A detailed handbook for the people who decide what Genesys Cloud records, how long it keeps it, and who may hear or delete it. It covers capture, consent, policies, unclaimed recordings, the retention ceiling, archive and export, screen recording, storage, orphans, encryption, access, redaction, secure pause, PCI DSS, legal hold, subject access and retention schedules. Checked against Genesys sources on 16 November 2026.
In short
- Recording is off by default, but once enabled on a trunk every call is recorded and policies decide what is kept.
- Recordings matching no policy are kept indefinitely, and overlapping policies keep the longest retention by default.
- The maximum retention setting caps everything, including analytics, and once set it can never be returned to null.
- Automatic redaction is best effort and reversible by permission; secure pause and secure flows stop capture outright.
- Legal hold covers 1,000 conversations, and a complete subject access search must include orphans and archives.
01
Capture, retain, delete: the layering
This handbook is for the people who decide what Genesys Cloud records, how long it keeps it, and who may hear or remove it: data protection officers, compliance and records managers, quality leads, security teams and the administrators who configure it. Every statement about Genesys Cloud comes from Genesys's documentation, listed in the sources and checked on 16 November 2026. Where something is our own practice, it is labelled QVCCS practice. Nothing here is legal advice; recording law and retention obligations need your own counsel.
1.1 Three decisions with different owners
Most recording conversations start with how long we keep recordings, as if one setting gave one answer. In practice there are several independent controls, set on different screens by different people, and the usual failure is not that they are too strict. It is that they interact so the organisation keeps more personal data than anyone decided to keep.
| Decision | Question | Usual owner | Where it is set |
|---|---|---|---|
| Capture | Is this interaction recorded at all? | Telephony and platform | Trunk or phone settings, and the Architect consent action |
| Retain | How long is it kept, and is it archived? | Compliance and records management | Recording policies and the organisation ceiling |
| Delete | What removes it, and what can stop that? | Legal and data protection | Policy delete dates, legal hold and purge APIs |
1.2 The layering this handbook follows
- Recording is off by default; nothing is captured until it is enabled on a trunk or phone (part 2).
- Once enabled on a trunk, every call is recorded, and policies decide what is kept (part 5).
- A recording that matches no policy is kept indefinitely unless an organisation-wide ceiling is set (part 6).
- The ceiling overrides everything below it, and once set it can never be removed (part 6).
- Some limits no setting extends, such as the one-year cap on screen recordings and reduced detail for older interactions (part 8).
- Legal hold sits above all of it, and is capped at 1,000 conversations per organisation (part 12).
02
Capture: off by default, trunk-side and station-side
The opposite assumption is common in migrations from systems where recording ran at the carrier or PBX. In Genesys Cloud, nothing is recorded until someone enables it.
2.1 Capture broadly, then decide what to keep
Genesys states that by default policy-based recording is not enabled, so calls are not recorded. You can capture policy-based recordings trunk-side, station-side or both, and once recording is enabled, Genesys Cloud records all calls automatically, with recording policies deciding what to keep, save or delete. Trunk-side recording can only be enabled at the trunk level.
So the shape is capture broadly, match against policies, then retain, archive, delete or export, all under an organisation ceiling. If several queues share a trunk, every call on it is captured, and selective recording by queue is a retention decision, not a capture decision. Where a requirement is that some conversations must never be captured at all, the answers are a separate trunk, station-side recording per phone, the Architect consent action (part 4) or secure pause (part 11), not a policy.
2.2 Trunk-side and station-side
Trunk-side recording happens as calls pass through external telephony, which suits inbound, DID and outbound calls but misses internal calls such as agent to agent. Station-side recording, available since July 2025, is configured per phone or through phone base settings and captures each agent's perspective, including internal calls. Genesys explains that trunk-side produces one recording of what the customer hears, including the transfer path, while station-side produces a recording for each agent of what that agent hears.
| Trunk-side | Station-side | |
|---|---|---|
| Artefact | One recording per interaction | One recording per agent |
| Perspective | What the customer heard | What each agent heard |
| Internal calls | Not captured | Captured |
| Configured on | The trunk | The phone or phone base settings |
| Across divisions | One recording, audible to supervisors in either division with access | Several recordings, possibly in different divisions |
- Both need decisions on audio format and dual channel; trunk-side also needs compliance settings. Separate channels help transcription and redaction and let an evaluator hear one party, at a storage cost.
- Recordings can be stored in particular Genesys Cloud regions; for trunk-side, check the external trunks' region affiliation, and for station-side, the phones' sites.
2.3 Consults, transfers and screens
Consult Line Recording is a trunk setting. With it on, when an agent puts a customer on hold to consult a colleague, Genesys starts a new recording for the consult and also records when all three parties are together. Genesys notes the consult recording has no transcript. The moment an agent asks a colleague whether something is allowed is often where non-compliance becomes visible, and without consult recording it is inaudible.
Screen recording follows policies by queue: if a queue with screen recording transfers to one without, the screen recording ends at the transfer, so a supervisor may have more audio than video. Simultaneous interactions are streamed as one video and split at playback, and Genesys warns that if an agent is signed in to more than one desktop or web app, it records both screens but keeps only one, and you cannot choose which.
03
What gets recorded: types and the full inventory
Recording covers several different artefacts, with different starters, listeners and rules. A retention schedule that covers only call recordings covers most of the risk and misses the parts that embarrass people in an audit.
3.1 Three kinds of recording
| User recording | Policy-based recording | Snippet recording | |
|---|---|---|---|
| Started by | A user, one call at a time | Automatically, once enabled on the trunk | An agent, for part of an ACD call |
| Retention | Not set by policy | By policy: indefinitely, for a period then deleted, or deleted | A configurable default |
| Who can listen | The user who made it | Supervisors with permission, assigned evaluators, and agents reviewing their own evaluation | Supervisors with permission, and agents reviewing their own snippets |
- A user recording sits in one person's inbox, outside policy, outside evaluation and effectively outside disclosure, and Genesys excludes ad hoc recordings from storage allocation.
- Snippets are an excellent coaching tool, and a snippet of a health disclosure is the same personal data as the full recording.
- Policy-based recording is the compliance conversation: systematic, and with retention the platform will set to whatever it is asked.
3.2 Digital, transcripts and screens
Policies also record email, chat and message interactions as text, and the recording metadata API distinguishes media types and subtypes such as trunk, station, consult, screen and snippet. A transcript is a derived artefact that exists only if transcription runs, and follows its recording: archived when it is archived, deleted when it is deleted, along with its topic and sentiment events. A screen recording is a video of the agent's desktop, started by policy, and Genesys can record screens only during ACD interactions and, depending on policy, after-call work.
3.3 The inventory a retention schedule must cover
| Artefact | Retention governed by | Note |
|---|---|---|
| Policy-based call recording | Recording policy, under the ceiling | No upper limit by default |
| Policy-based digital recording | Recording policy, under the ceiling | Counts against storage, with attachments |
| Transcript | Follows its recording | Call transcripts do not count against storage |
| Screen recording | Recording policy | One-year maximum, including archive |
| User (ad hoc) recording | The individual | Outside policy and storage allocation |
| Snippet recording | Configurable default | Agent-initiated |
| Voicemail | Separately | Outside storage allocation |
04
Consent and notification
The mechanism is simple. The judgement behind it belongs to the client, and the platform will not make it for you.
4.1 The consent action
Genesys explains that an Architect action can ask inbound callers whether they consent to recording. If they say no, the media layer does not record at all; if yes, recording proceeds and policies apply as usual. The trunk must allow line recording and be set to obtain consent first. The capability dates from May 2017.
- Genesys does not begin recording before consent, and flushes queued audio before the Enable Participant Recording action runs, so nothing said before consent can be recovered.
- There is no action to disable participant recording later in the flow.
- The action only enables recording rules; after consent, the flow must transfer the call to a queue where recording is enabled.
- For conference calls, Genesys ignores the trunk's consent setting for station-side recordings and records each participant as they join.
- It works for inbound calls routed through Architect; outbound calls cannot ask for consent this way.
4.2 Notification is a legal decision
Notification and consent rules are a matter of national law, and in the UK of the controller's lawful basis and the caller's reasonable expectations. Genesys documents mechanisms, not jurisdiction-by-jurisdiction requirements. The recording announcement is a prompt played to callers, and its wording is a statement about processing personal data.
4.3 Test every entry point
Whether the announcement falls inside or outside the recording depends on configuration, and direct dial, transfers, callbacks, outbound campaigns, conferences and non-ACD calls each reach the recording layer differently. A design tested on one inbound route has tested one inbound route.
05
Recording policies: matching and actions
Genesys says policies specify which interaction recordings to retain or delete, and can also automate quality tasks such as creating evaluations or starting calibrations. One object therefore serves records management, storage and quality, which is efficient and creates a governance problem.
5.1 Matching criteria
A policy is configured per media type, with matching criteria and actions filled in separately for each, so one policy can have different rules for calls, email, messages and chat, and a forgotten media type is a gap.
| Criterion | Matches | Watch for |
|---|---|---|
| Conversation direction | Inbound or outbound | Outbound campaigns inflate volumes |
| Specific users | Named users | Staff changes silently empty a policy |
| Specific work teams | Interactions serviced by named teams | Team membership must be maintained |
| Time sets | Interactions in named time ranges | Out-of-hours often needs its own policy |
| Specific queues | Named queues | Genesys recommends no more than 250 queues per policy |
| Specific wrap-up codes | Named codes | Depends on agents applying codes |
| Date range | Interactions on certain dates | For temporary needs |
| Conversation duration | A specified duration | Includes queue time and after-call work |
| Customer participation | Whether a customer took part | Email and message only |
- Policies apply only to interactions after they are enabled. A seven-year policy switched on in March applies from March.
- Matching applies to the conversation as a whole, so after a transfer an evaluation may go to an unexpected agent; our quality management handbook covers the first-agent and last-agent rules.
- If an agent dismisses an email without replying, no recording is created for that agent and a policy cannot create an evaluation, although one can be assigned manually.
5.2 Actions
| Action | Effect |
|---|---|
| Retain | Keep for a number of days, or indefinitely; recordings must be retained for evaluations, calibrations and surveys |
| Do not save | Recordings are not kept; optionally delete even if another policy retains |
| Archive | Move to long-term storage, outside the storage allocation |
| Export | Send recordings, screen recordings, attachments and metadata to an AWS S3 bucket |
| Screen record | Start screen recording for matched interactions |
| Create evaluations | By interactions, evaluators or agents, or for calibration |
| Survey | Send web survey invitations for matched interactions |
- Genesys exports first and deletes second when both are set, and exports a recording only once; a second matching export skips it.
- A policy that creates evaluations needs the recording to outlive the evaluation cycle, or evaluators find an assignment with nothing to hear.
5.3 Genesys's own guidance
Genesys's retention best practice is unusually concrete: give each policy only the matching criteria its business use case needs, keep the number manageable, keep it focused, avoid overlapping and conflicting retention policies, and where overlaps exist, make sure the longer retention period is set. Its worked scenarios, from recording and retaining all inbound calls to extended retention for specific criteria, show how quickly estates become complicated.
06
Overlaps, unclaimed recordings and the organisation ceiling
Two documented behaviours explain most retention surprises, and one setting is the safety net under both. It is also a one-way door.
6.1 Longest retention wins
Genesys states that when overlapping policies exist and one retains a recording longer, it uses the longer one, if delete days are explicitly defined. It also explains that by default, if one policy retains a recording and another deletes it, the recording is kept, unless the deleting policy uses Do not save recordings with Delete even if another policy retains.
So adding a 30-day policy beside an existing seven-year policy does not shorten anything; the seven years still governs, and nobody notices. Forced deletion is available, but it is a blunt instrument that overrides every other policy, including those keeping recordings for evaluation or evidence.
6.2 Recordings nobody claims
Genesys's quality policies overview is plain: interaction recordings that match no policy are retained indefinitely, or up to the maximum interaction data retention time if one is set. The failure sequence is ordinary. Recording is on for the trunk, so everything is captured; policies cover the main queues; new or renamed queues and forgotten media types match nothing; and those recordings are kept for ever, unreported, until a subject access request finds them.
6.3 The maximum interaction data retention time
Genesys explains that when this is set, interaction data, meaning interaction records and their recordings, is not retained beyond it, and the 2022 release note adds that it deletes interaction detail records, recordings and related individual and aggregate analytics. It is set in days under Security and Compliance in organisation settings, with a minimum of 90 days for conversation detail data, and Genesys's feature table gives conversation data a range of 90 days to five years, undefined by default. Recordings outside any policy are deleted at the ceiling too.
Then the one-way door. The default is null; once set, Genesys says you can change it to a shorter or longer duration, but you can never set it back to null. Raising it later recovers nothing, and existing recordings keep their original dates unless changed through the recording bulk job API.
The controls are deliberately conservative. You cannot set a ceiling that conflicts with existing configuration: if historical interactions have deletion dates beyond it, or quality policies retain longer, Genesys notifies you and blocks the change until they are updated.
- Shorten quality policy retention to fit.
- Review existing deletion dates and adjust them in bulk if needed.
- Set the ceiling at the intended value.
- Check a sample of interactions to confirm their delete dates match the schedule.
07
Changing retention, archiving and exporting
Once data exists, changing how long it is kept is a project, not a setting. Archive and export are the two levers, and both are widely misunderstood.
7.1 Bulk changes
The recording bulk job API is the mechanism for every mass change: changing deletion dates, archiving, exporting and deleting. Shortening deletion dates schedules future deletions rather than deleting at once, which gives a window to correct mistakes, and also means a subject access request during that window sees data the organisation has already decided to discard. Legal hold (part 12) overrides policy deletion dates, so a bulk clean-up cannot remove protected conversations.
7.2 Archive
| Property | Effect |
|---|---|
| Storage | Archived recordings do not count against storage allocation |
| Retrieval | Restoring from long-term storage can take several hours |
| Restored copies | You set how long the restored copy is kept, and it counts towards storage |
| Transcripts | Archived with their recording |
| Export | Archived recordings can be exported without restoring, but this takes many hours; batch download needs restoring first |
| Date changes | Changing the archive date of an archived recording restores it until the new date |
- Archived data is not deleted data. It is still personal data, still disclosable and still subject to the ceiling.
- Restoration is slow, so archive is not a fast route to answering a subject access request on a one-month clock.
- The former limit on simultaneous restorations is no longer enforced.
7.3 Export to your own storage
The AWS S3 recording bulk actions integration lets a policy export recordings of any media type, screen recordings, attachments and metadata to a client's own bucket. Genesys notes that orphaned recordings are not exported unless recovered, that only one instance of the integration can be active, and that automatic export through a policy works only for interactions under 1.5 years old, while the bulk API reaches older ones. Export is how longer obligations are met: once in the client's bucket, retention and encryption become the client's decisions.
08
Ageing data and screen recording limits
Some limits no setting moves. They explain a category of the data has gone tickets that are not data loss at all.
8.1 What changes as interactions age
| Capability | Under 1.5 years | 1.5 to 5 years | Over 5 years |
|---|---|---|---|
| Search in the Interactions view | Yes | Yes | Yes |
| Interaction details and playback | Yes | Limited detail | Limited detail |
| Automatic export by policy | Yes | No | No |
| Bulk export, delete and archive by API | Yes | Yes | Yes |
| Analytics details API | Yes | No | No |
| Analytics aggregates API | Yes | Yes | No |
| Recording and speech analytics APIs | Yes | Yes | Yes |
- After 1.5 years you can still hear the call and read the transcript, but the interaction timeline and conversation events, such as who joined or left, are gone: the structure that turns audio into evidence.
- Separately, viewing interaction history from an external contact or organisation is limited to 365 days.
- Sentiment and acoustic data persist until the related recordings are deleted; SIP diagnostic captures are kept for 21 days; audit data for at least a year.
8.2 Screen recording's hard limits
Genesys states that screen recording policies have a one-year maximum retention, and that archived screen recordings are deleted after a year too; to keep them longer, move them to your own storage. After-call work screen recording stops at 60 minutes, and screens are recorded only during ACD interactions. Recording needs the Genesys Cloud desktop app, a browser with the Background Assistant installed, or on ChromeOS the Media Helper app, and on a Mac the operating system's screen recording permission.
09
Storage, and orphaned recordings
Retention decisions become commercial decisions through the storage allocation, and orphaned recordings are an operational fault with a privacy consequence.
9.1 What counts against storage
Genesys allocates data storage per seat under its fair use policy, varying by plan, by counting billable users of each licence type, and charges for use above the allocation. Its storage calculator estimates usage, though it does not consider historical execution data.
| Counts towards the allocation | Does not count |
|---|---|
| Policy-based call recordings | Archived policy-based items |
| Policy-based digital recordings and digital transcripts, with attachments | User (ad hoc) recordings |
| Policy-based screen recordings | Collaborate chats and voicemails |
| Historical execution data | Transcripts of policy-based call recordings |
- Archiving is the main lever, and Genesys added bulk archiving in November 2023 for organisations whose storage use reaches or exceeds the allocation.
- Call transcripts are outside the allocation and digital transcripts are not; on a messaging-heavy estate, email with attachments is often the fastest-growing item.
9.2 Orphaned recordings
Genesys defines an orphaned recording as one that remains on the Edge instead of being processed by Genesys Cloud. It is not attached to a conversation, so it does not appear in interaction details. Its example: if an agent does not add a wrap-up code, Genesys treats the conversation as unfinished, cannot apply a policy and marks the recording as orphaned. Orphans are listed in Recording Management, where each can be played, deleted, downloaded or reattached, and since 2017 policies can delete or reattach them automatically.
- Orphans are personal data outside the interaction record, invisible to interaction searches, analytics and most disclosure processes.
- On a BYOC Premises estate they sit on the client's own Edge, which matters to a data residency review.
- Genesys's export integration skips orphans unless they are recovered.
10
Encryption, divisions and who may listen
Confidentiality is normally assumed rather than designed. Three places need explicit decisions: key management, division boundaries and listening permissions.
10.1 Encryption and one documented gap
Genesys uses per-organisation encryption keys to protect call recordings, digital recordings and transcripts. Its note adds that screen recordings are encrypted in S3 with Amazon S3 managed keys instead. A client who has chosen to manage its own recording keys therefore does not get the same control over desktop video.
| Option | Available since | What it gives you |
|---|---|---|
| Genesys Cloud managed keys | Default | Per-organisation keys, generated and stored by Genesys |
| Local key management | July 2017 | Keys generated and stored on premises, for organisations that must manage their own keys |
| AWS KMS symmetric key | April 2022 | Keys from the customer's own AWS KMS |
- Keys can be rotated; Genesys records each new key pair and the person who generated it.
- Since August 2022, self-managed KMS also covers conversation data, with Architect's secured data actions for sensitive values in flows.
- Exported recordings in the client's S3 bucket use the bucket's server-side encryption, with optional additional encryption that the client must then decrypt itself; Genesys does not support PGP object encryption on exports in the FedRAMP region.
10.2 Divisions do not confine a recording
Genesys explains that a trunk-side recording covers the whole transfer path, which may cross divisions, so a supervisor in either division with access to the recording can hear all of it, including the other division's agent. Station-side recordings in one interaction can sit in different divisions, with the same result. Genesys's answer is access control at the recording segment level, which limits agents and supervisors to the segments relevant to them.
10.3 Listening permissions
Recording access is granular by media type: recording:recording:view for call recordings, recording:screenRecording:view for screen recordings, recording:snippetRecording:view for snippets, with separate permissions to delete, edit retention and restore. Orphaned recordings and legal hold have their own permissions. One permission matters more than the rest: Recording, Recording, ViewSensitiveData, which Genesys says lets a user hear and read the original, unredacted recording and transcript regardless of redaction settings, and which an administrator must grant explicitly.
11
Redaction, secure pause and payment cards
Redaction in Genesys Cloud means several unrelated mechanisms with different guarantees. Most conversations about it go wrong because two people mean two different ones.
11.1 Four mechanisms
| Mechanism | What it does | When | Guarantee |
|---|---|---|---|
| Automatic redaction | Masks detected entities in transcripts and recordings; the original remains behind a permission | After the interaction, through speech and text analytics | Best effort |
| Secure pause | Stops recording and transcription | During the call, started by the agent | Absolute, if used |
| Secure call flow | Prevents recording and agent access while the caller enters data | During the call, controlled by the flow | Absolute, by design |
| Card number filtering | Filters card numbers detected with the Luhn algorithm from digital text | Real time | Pattern-based |
11.2 Automatic redaction and its caveats
Two separate settings in organisation settings, for payment cards and for personal information, enable redaction in recordings and voice transcripts, and since March 2025 administrators can choose which entities to redact. Entities include card numbers and expiry dates, national identification numbers (covered only for Australia, Canada, the UK and the US), postal codes, names, locations, phone numbers, email addresses and other sensitive data. A name counts as card data if it appears near a card number.
- Genesys describes it as best effort.
- It works only where speech or text analytics is enabled for the interaction, so reducing transcription coverage reduces redaction coverage.
- Users with ViewSensitiveData can still access the original, so redaction is a default view, not destruction.
- Genesys recommends secure pause or secure call flows as the first line of defence.
- No recording policy deletes recordings because they contain sensitive data; Genesys's FAQ says to build a custom solution using the content search APIs to find them and the purge APIs to delete them.
11.3 Secure pause
Secure pause stops recording while the agent can still hear the customer, and instead of silence the recording plays a beep, so the recording itself shows that a pause happened, and for how long, without revealing what was said. It also stops transcription. Genesys's script configuration article still says secure pause is only available for ACD calls and callbacks, but the March 2026 release note and announcement extend it to all voice calls, including non-ACD calls and campaign callbacks to DIDs. We rely on the newer statement; check your organisation.
What has not changed is the human dependency: Genesys's announcement says agents must still activate secure pause manually when collecting sensitive information.
11.4 PCI DSS
Genesys states it is a Level 1 Service Provider, assessed against PCI DSS version 4.0.1, with the attestation available under a non-disclosure agreement, and that only features noted in its Report on Compliance may process, transmit or store card data. Its PCI page lists the validated features: secure pause, secure call flows, Genesys's own Dialog Engine bot flows, and a named set of third-party bot and text-to-speech services. Using features outside that list for card data is not covered by the licence. Genesys Cloud Voice, BYOC Cloud and BYOC Premises are all listed as compliant deployment models.
Enabling the PCI setting, through Genesys Customer Care, disables DTMF logging and media capture by the Edge, and Genesys stresses that compliant and non-compliant organisations are equally secure. Its customer responsibility matrix sets out which requirements fall to the customer, and third-party integrations add their own shared responsibilities.
12
Legal hold, and its 1,000-conversation ceiling
Genesys provides a proper legal hold, with one number attached that no organisation should discover during an investigation.
12.1 How protection works
Genesys explains that managers can protect recordings from deletion to comply with legal directives for litigation or investigations, or to keep training interactions indefinitely. Protection covers policy-based recordings of every media type and their screen recordings, applies at conversation level to all of its recordings, including future ones, with attachments and transcripts, prevents manual deletion and overrides policy deletion dates while it stays in place. Protection events are captured in the recording audit trail. It has been available since April 2020, applied from the Interactions view or per interaction, with separate permissions to apply and to revoke.
- Genesys states that 1,000 conversations can be protected per organisation.
- Protection does not apply to a conversation that has no recording.
- When protection is removed, any existing policy deletion date applies, so releasing a hold on a short-retention population can delete the recordings almost at once.
- There is no dedicated list of protected conversations; Genesys suggests saving a filtered Interactions view.
12.2 Holds larger than the ceiling
A thousand conversations is generous for a typical annual load of complaints and claims, and far too few for a systematic hold, such as a regulatory investigation of a department for a year or a data breach affecting many interactions. That is not a design flaw, since an unlimited hold would let anyone disable retention by accident, but it means large holds need a different mechanism, decided in advance.
- Export the population to the client's own storage first, through the S3 bulk actions integration.
- Protect the specific conversations that must stay live in the platform.
- Extend retention through a policy for the affected population if the hold is broad, which the retention schedule should anticipate as a legitimate requirement.
13
Subject access, erasure, and employees as data subjects
Genesys provides a purpose-built API for data subject requests. The harder questions are what a response must cover, what erasure can and cannot do, and how employees fit in.
13.1 The GDPR API and its timings
Genesys describes its GDPR API as the preferred self-service way to respond to requests to access, rectify or delete personal data, introduced in May 2018 for Articles 15, 16 and 17 and extended to CCPA requests in October 2019. Genesys says retrieving all personal data for an access request typically takes one to two days, and erasure or anonymisation no longer than 14 days.
Those are platform timings inside a client's legal clock. Under UK GDPR the period is one month, extendable for complex requests, and identity checks, review for other people's data and redaction are the client's own work and usually the slowest part.
13.2 What a response must cover
- The interaction record and timeline, subject to the 1.5-year and 365-day limits in part 8.
- Every recording, which may be several with station-side or consult recording.
- Transcripts, where transcription ran.
- Screen recordings, which show the agent's screen and may include other customers' data.
- Digital recordings and attachments.
- Snippets, ad hoc user recordings in individual inboxes, and orphaned recordings.
- Archived recordings, which need restoring, and copies already exported to the client's storage.
13.3 What erasure does not do
Genesys says customers cannot choose whether personal data is deleted or anonymised; some services delete and others anonymise. Users cannot delete their own call history, which follows the organisation's settings. And there is no policy mechanism for deleting recordings because of their content (part 11).
Short, defensible retention is the cheapest data subject rights operation available. An organisation that deletes recordings at 90 days has little to erase; one that keeps everything indefinitely must search the whole inventory for every request.
13.4 Employees are data subjects too
Genesys addresses an employee's erasure request directly: using its products requires processing employees' names, work phone numbers and email addresses, which for current employees is necessary for the customer's legitimate interests and may also be needed for other regulatory requirements, so Genesys does not recommend erasing personal data associated with an ongoing user. Its wording is limited to current employees.
A recording is about two people. A customer's request does not remove the employee from it, and an employee's request does not remove the customer's conversation where it is kept for quality, disputes or regulatory defence.
14
Designing a retention schedule, the audit trail, and what goes wrong
Everything in this handbook points at one document most organisations do not have: a retention schedule for customer conversations, translated into platform settings and kept accurate by review.
14.1 Six questions per population
| Column | Question | Set in Genesys Cloud by |
|---|---|---|
| Population | Which interactions? | Policy matching criteria |
| Purpose | Why do we hold it at all? | Nothing: this is the justification |
| Period | How long, and from when? | Policy retention days, under the ceiling |
| Owner | Who may approve an extension? | Process, not platform |
| Override | What can suspend deletion? | Legal hold |
| Cost | What does it cost to store? | The storage allocation |
- The purpose column makes the exercise work: a period with a reason survives a finance review, and always seven years does not.
- Every rule that depends on human behaviour, such as a policy matched on a complaint wrap-up code, needs a fallback that does not, such as the ceiling.
- Genesys's feature table gives interaction data a configurable range of 90 days to five years, while call and digital recordings have no upper limit of their own but are subject to the ceiling once it is set. Where an obligation is longer than the platform will hold data, the design is export to the client's own archive, with an owner.
14.2 Audit trail and disclosure
Genesys keeps customer audit data for a year, with export through its Amazon EventBridge integration. A client keeping recordings for years cannot answer who listened to one in year two from platform audit data alone. Disclosing a recording to an insurer, ombudsman, police force or relative is a new use of personal data with its own lawful basis, and downloading takes two clicks.
14.3 What goes wrong
| Symptom | Likely cause | Fix |
|---|---|---|
| Storage climbing with no explanation | Unmatched recordings kept indefinitely | Set the ceiling; review policy coverage (part 6) |
| A shorter policy had no effect | Longest retention wins in an overlap | Policy register; avoid shortening by addition (part 6) |
| The ceiling cannot be set | Policies or existing dates exceed it | Shorten policies, adjust dates, then set (part 6) |
| Someone wants the ceiling removed | It cannot return to null | Second-approver control on the settings page (part 6) |
| No recordings at all | Recording not enabled on the trunk | Trunk audit (part 2) |
| Recordings for a queue nobody chose | Trunk-side capture records every call on the trunk | Separate trunk or station-side capture (part 2) |
| Calls missing after consent | Caller declined, or call not sent to a recording queue | Review the consent flow (part 4) |
| Evaluation has no audio | Retention shorter than the evaluation cycle | Retention above cycle plus margin (part 5) |
| Incomplete subject access response | Orphans, user recordings or archives missed | Runbook against the full inventory (part 13) |
| Redaction did not work | No analytics on the interaction, or entity not covered | Check transcription scope; test on real calls (part 11) |
| Card numbers in a recording | Secure pause not used | Script button, pause metric or secure flow (part 11) |
| Screen recording missing or short | Endpoint software, two sessions, or a transfer | Endpoint standards; set expectations (parts 2 and 8) |
| Cannot hold a whole population | 1,000-conversation protection limit | Export, extend retention, protect specific matters (part 12) |
| Recordings vanished after a hold ended | Policy delete date reapplied on release | Check the policy before release (part 12) |
| Who listened? unanswerable after a year | Audit data kept for one year | Stream audit events out (part 14) |
Questions
Common questions
Does Genesys Cloud record calls by default?
No. Genesys states that policy-based recording is not enabled by default. Once it is enabled on a trunk or phone, Genesys records all calls automatically, and recording policies decide what is retained, archived, exported or deleted. Selective recording by queue is therefore a retention decision, unless you use a separate trunk, station-side recording, the consent action or secure pause.
How long does Genesys Cloud keep call recordings?
As long as your recording policies say. Genesys says recordings that match no policy are kept indefinitely, unless the maximum interaction data retention time is set, which then caps all interaction data and recordings. Screen recordings have a one-year maximum. When policies overlap, the longer retention wins unless a policy is set to delete even if another policy retains.
Can the maximum interaction data retention time be removed once set?
No. Genesys states the default is null, and once you set it you can change it to a shorter or longer duration but never back to null. It deletes interaction records, recordings and related analytics beyond the limit, and Genesys blocks setting it while policies or existing deletion dates exceed it. Decide it deliberately, with data protection and analytics owners.
Is Genesys Cloud automatic redaction enough for PCI DSS?
Not as the primary control. Genesys describes automatic redaction as best effort, dependent on speech or text analytics, and reversible for users with the ViewSensitiveData permission. It recommends secure pause or secure call flows as the first line of defence. Use redaction as defence in depth, and keep card data on features Genesys lists as PCI validated.
How many conversations can be placed on legal hold in Genesys Cloud?
Genesys states that 1,000 conversations can be protected per organisation. Protection overrides policy deletion dates and covers all recordings, attachments and transcripts in a conversation. For larger holds, export the population to your own storage first, then protect the specific conversations that must remain in the platform and extend retention through a policy if needed.
How quickly can Genesys Cloud answer a subject access request?
Genesys says retrieving personal data through its GDPR API typically takes one to two days, and erasure or anonymisation no longer than 14 days. Your legal deadline is separate, and identity checks, third-party redaction and restoring archived recordings, which can take several hours each, are your own work, so build them into the procedure.
Sources
- Limit interaction history for external contacts and organizations to 365 days – Genesys Cloud Resource Centerhelp.genesys.cloud
- Policy-based station-side call recording expands internal call coverage – Genesys Cloud Resource Centerhelp.genesys.cloud
- Secure pause available on all call types – Genesys Cloud Resource Centerhelp.genesys.cloud
- About Architect – Genesys Cloud Resource Centerhelp.genesys.cloud
- About call recording – Genesys Cloud Resource Centerhelp.genesys.cloud
- About the quality management integrations – Genesys Cloud Resource Centerhelp.genesys.cloud
- Quality policies overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- About recording – Genesys Cloud Resource Centerhelp.genesys.cloud
- About screen recording – Genesys Cloud Resource Centerhelp.genesys.cloud
- About security and compliance – Genesys Cloud Resource Centerhelp.genesys.cloud
- About the AWS S3 recording bulk actions integration – Genesys Cloud Resource Centerhelp.genesys.cloud
- Access control transactional objects – Genesys Cloud Resource Centerhelp.genesys.cloud
- Add the AWS S3 recording bulk actions integration – Genesys Cloud Resource Centerhelp.genesys.cloud
- Administrators – Genesys Cloud Resource Centerhelp.genesys.cloud
- AudioHook Monitor overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- Change encryption key now – Genesys Cloud Resource Centerhelp.genesys.cloud
- Configure secure pause actions in scripts – Genesys Cloud Resource Centerhelp.genesys.cloud
- Create a policy – Genesys Cloud Resource Centerhelp.genesys.cloud
- Data retention periods and export functionality by feature – Genesys Cloud Resource Centerhelp.genesys.cloud
- Enable automatic redaction of sensitive information – Genesys Cloud Resource Centerhelp.genesys.cloud
- Enable Participant Recording action – Genesys Cloud Resource Centerhelp.genesys.cloud
- Enable policy-based recording – Genesys Cloud Resource Centerhelp.genesys.cloud
- Recording encryption key overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- GDPR overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- General Data Protection Regulation (GDPR) – Genesys Cloud Resource Centerhelp.genesys.cloud
- Genesys Cloud and CCPA compliance – Genesys Cloud Resource Centerhelp.genesys.cloud
- Genesys Cloud and GDPR compliance – Genesys Cloud Resource Centerhelp.genesys.cloud
- Data storage charge examples – Genesys Cloud Resource Centerhelp.genesys.cloud
- Genesys Cloud fair use policy – Genesys Cloud Resource Centerhelp.genesys.cloud
- Interaction Recording Retention Policies Best Practices – Genesys Cloud Resource Centerhelp.genesys.cloud
- Interactions view – Genesys Cloud Resource Centerhelp.genesys.cloud
- Manage organization settings – Genesys Cloud Resource Centerhelp.genesys.cloud
- Pause a call recording to protect sensitive data – Genesys Cloud Resource Centerhelp.genesys.cloud
- PCI DSS compliance – Genesys Cloud Resource Centerhelp.genesys.cloud
- PCI DSS customer responsibility matrix – Genesys Cloud Resource Centerhelp.genesys.cloud
- Protect recordings from deletion – Genesys Cloud Resource Centerhelp.genesys.cloud
- Record ACD agent consult calls – Genesys Cloud Resource Centerhelp.genesys.cloud
- Call recording overview in Genesys Cloud – Genesys Cloud Resource Centerhelp.genesys.cloud
- Retention period for analytics data and recording – Genesys Cloud Resource Centerhelp.genesys.cloud
- Retrieve archived interactions – Genesys Cloud Resource Centerhelp.genesys.cloud
- Screen recording overview – Genesys Cloud Resource Centerhelp.genesys.cloud
- Set the maximum interaction data retention time – Genesys Cloud Resource Centerhelp.genesys.cloud
- Speech and text analytics – Genesys Cloud Resource Centerhelp.genesys.cloud
- Storage calculator – Genesys Cloud Resource Centerhelp.genesys.cloud
- Store recordings in local Genesys Cloud regions – Genesys Cloud Resource Centerhelp.genesys.cloud
- Understand voice transcripts – Genesys Cloud Resource Centerhelp.genesys.cloud
- View orphaned recordings – Genesys Cloud Resource Centerhelp.genesys.cloud
- Work with exported recordings in AWS S3 bucket – Genesys Cloud Resource Centerhelp.genesys.cloud
- Can I delete my call history in Genesys Cloud? – Genesys Cloud Resource Centerhelp.genesys.cloud
- Can I record an agent's screen during non-ACD interactions? – Genesys Cloud Resource Centerhelp.genesys.cloud
- Can I use a recording policy to delete recordings that contain sensitive data? – Genesys Cloud Resource Centerhelp.genesys.cloud
- Do archived recordings count against my org level storage allocations? – Genesys Cloud Resource Centerhelp.genesys.cloud
- Licensing and costs - What license do I need to use speech and text analytics? – Genesys Cloud Resource Centerhelp.genesys.cloud
- August 10, 2016 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- April 22, 2020 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- April 27, 2022 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- August 02, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- August 10, 2022 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- August 24, 2022 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- February 5, 2020 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- January 31, 2018 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- July 12, 2017 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- July 21, 2021 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- July 7, 2025 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- March 2, 2026 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- March 24, 2025 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- March 8, 2017 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- May 23, 2018 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- May 3, 2017 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- November 29, 2023 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- October 11, 2017 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- October 16, 2019 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- October 5, 2016 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- September 18, 2019 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- September 2, 2020 release notes – Genesys Cloud Resource Centerhelp.genesys.cloud
- Recording API (Platform API reference) – Genesys Cloud Developer Centerdeveloper.genesys.cloud
Keep reading
More guides
Building Genesys Cloud Architect flows: the advanced handbook
An advanced handbook for building Genesys Cloud Architect flows: variables, data actions, error handling, limits, secure flows, testing and version control.
Read the guideGenesys Cloud roles, permissions and divisions: the access control handbook
A detailed handbook to Genesys Cloud access control: permissions, roles, divisions, groups, conditions, ABAC, licence effects, OAuth clients and partner access.
Read the guideThe EU AI Act and UK GDPR for contact centres: what applies and when
What the EU AI Act and the UK's new automated decision rules mean for contact centres: AI disclosure, emotion analysis, agent monitoring, and key dates.
Read the guide