Extensions

Data Retention and Deletion Configuration

Conversations, records and logs are kept for as long as you decide, then deleted on schedule or on request.

Keeping every transcript and record forever feels safe until a customer asks you to delete their data, or a regulator asks why you still hold it. This add-on sets how long each type of data in your AI product is kept, deletes it on schedule, and adds a tested workflow for individual deletion requests. You decide the periods.

  • Keeps each type of data only as long as you decide
  • Handles individual deletion requests through one tested workflow
  • Documents the retention schedule for reviews
$1,500 10–20 working days
Archive boxes shrinking in size beside an hourglass, data kept for a set time then removed.

What it is

Data Retention and Deletion Configuration sets retention periods and deletion workflows for an AI product you already run, or are buying now. You decide how long each type of data is kept, and the product deletes it on schedule or when a person asks. Deletion is tested and the schedule documented.

Why businesses buy it

Data you no longer need is a liability: it can leak, it must be searched during requests, and many privacy rules expect you to justify keeping it. Deleting by hand across conversations, records and logs is slow and easy to get wrong. Configured retention does it on schedule, and a single workflow handles individual requests properly. The written scope sets a period for each data type, scheduled deletion, the request workflow, deletion tests and a documented schedule you can show reviewers.

Problems this solves

Customer data piles up in the product with no clear end date

This add-on sets retention periods for each type of data the product holds. You decide how long each type is kept, and the product deletes it on schedule.

Deletion requests are handled by hand and sometimes missed

A deletion workflow removes a person's data from the product when they ask. It is tested before launch, so you can show each request was carried out properly.

Staff cannot explain your data-keeping rules when asked

The retention schedule is documented in plain terms as part of the handover. Anyone answering a question from a customer or regulator has one written source to point to.

Scope card SKU UPM-A0029

Data Retention and Deletion Configuration

Everything this build includes, written down before you pay. Choose how you want it, own the code or license it yearly, then the delivery speed and any add-ons.

$1,500 one-time build price

What is included

Channel
As per the parent product
Integrations
As described in the add-on
Knowledge
As per the parent product
Workflows
Configures retention periods and deletion workflows
Languages
As per the parent product
Testing
Tested together with the parent product
Revisions
1 round
Handoff
Written handover report
Support
14 days after launch

A good fit if

Your product keeps transcripts, recordings or records indefinitely, and you would rather it did not.
Customers ask you to delete their data, and today that means hunting through systems by hand.
Your policy, or a customer's, sets how long certain data may be kept.
You can decide retention periods for each type of data the product holds.

Not the right fit if

You want personal data removed before it reaches AI models or logs at all. PII Redaction Layer redacts it.
You want a copy of your data kept safe, not deleted. Offline Export and Backup adds scheduled export.
You want data classified and handling rules enforced across AI workflows. AI Data Governance Assistant does that.
You need your data flows and controls documented for a review. Compliance Documentation Pack writes that up, though it is not a certification.

How it works

  1. Data types are listed. Conversations, recordings, transcripts, records and logs the product holds, and where each lives.
  2. Retention periods are set. You decide how long each type is kept.
  3. Scheduled deletion is built, removing data when its period ends.
  4. A deletion request workflow is added, so one person's data can be found and removed when they ask.
  5. Deletion is tested with the parent product, including a request for one test person, then reviewed with one revision round.
  6. Handoff. The retention schedule is documented, with a test report and a written handoff note.

What you provide within 72 hours

Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.

  • The order reference of the product being configured
  • Your retention periods for each type of data, or your policy that sets them
  • Who may approve an individual deletion request
  • Access to systems where the product stores data, shared securely in the way we agree at intake
  • One person who signs off the schedule
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.

Timeline

Start Data types and storage locations listed
Week 1 Retention periods agreed
Week 2 Scheduled deletion and request workflow built
Week 2 Deletion tested, including one person's request
Week 2 Your review and one revision round
Go-live Retention live, schedule documented
Delivery options, in working days (Monday to Friday) from completed intake. They can extend because of national or public holidays, technical issues outside our control (such as platform outages, third-party changes, account approvals or access delays), or natural disasters and other events beyond our control. If a delay happens, we tell you in writing with a new date.
OptionDelivery timePrice
Standard10–20 working days$1,500

What you receive at handover

  • Retention periods configured for each agreed type of data
  • A deletion workflow for requests from individuals
  • A documented retention schedule
  • A test report showing deletion working, plus a written handoff note

Expected benefits and how to measure them

  • Helps you keep data only as long as you decided
  • Can make deletion requests quicker and more consistent
  • Makes your data-keeping rules easier to explain
Deletion request turnaround
Log the date each request arrives and the date it is completed, before and after launch.
Data past its retention date
Each quarter, check a sample of records against the schedule and count any kept too long.
Missed requests
Compare requests received with requests completed each month and note any gaps.

Before you start: Record how much stored data the product holds and its oldest records. Note how deletion requests are handled today.

These are things to track, not promised results. Outcomes depend on your data, your team and your market.

Running costs

Retention can lower storage costs over time, since old data is removed. Anything the product already uses stays billed to your own accounts. We charge once for the configuration.

Ask about running costs

Custom requirements

Deleting data in systems the product does not control, legal holds that pause deletion, or different periods per customer are beyond this add-on. Note them at checkout for a written Change Quote. Larger or bespoke projects go through the Custom AI request form instead.

Request a custom version

Keep it running

Retention is covered by the parent product's maintenance, which grows in line with the add-on's price. Changing a retention period or adding a data type uses its monthly change hours.

Adds $75/mo to maintenance

Covered by the main product's maintenance, which grows by this amount.

How maintenance works

How this compares

Do it yourself with a SaaS toolHire a custom agencyUpmark Labs
Price Retention controls on a higher monthly tier An agency quotes data work Ours is one fixed price, shown before you buy
Periods One setting for everything Agreed in the project Ours sets a period for each type of data
Requests Handled by hand Depends on the brief Ours adds a workflow for individual deletion requests
Proof Trust the setting Depends on the brief Ours tests deletion and documents the schedule

Questions about this product

Who decides how long data is kept?

You do. We list every type of data the product holds and where it lives, and you set a period for each, usually based on your own policy or a customer's requirement. We can explain the options, but we do not set legal retention periods for you.

How does someone's deletion request get handled?

A person you name approves the request, and the workflow finds that individual's data across the places the product stores it and removes it. We test this with a test person before launch, and the test report shows what was found and deleted.

Will deleting data break the product?

No. Deletion is applied to records that have reached the end of their period, or that a person asked to remove. The product keeps working with the data that remains. Before launch we confirm the product still behaves correctly after scheduled deletion runs.

What should we decide before retention is configured?

Mainly how long each type of data should be kept: conversations, transcripts, records and logs. Your legal or privacy adviser may already have a policy, and we turn it into periods the product enforces. The add-on follows the delivery speed of its parent product, and faster speeds are available, each with a fixed price and date shown before you pay.

Does it delete data held in other systems, like our CRM?

Only where the product stores data itself, or where it has agreed access to delete. Records in your CRM or helpdesk that other teams own are outside this add-on unless agreed. Note them at checkout if they need including, for a Change Quote.

Does this make us compliant with data protection law?

It helps you put your retention policy into practice, but no add-on can make you compliant on its own. Compliance depends on your wider policies and decisions. For written documentation of data flows and controls, see the Compliance Documentation Pack, which is not a certification.

Keep data only as long as you mean to.

Add Data Retention and Deletion Configuration and your product deletes each type of data on the schedule you set, with a tested workflow for individual requests.

Works well with

Desk phone off the hook beside an appointment card and a brass bell, showing calls turned into bookings.
Inbound

AI Voice Receptionist

Answers calls, handles common questions, takes messages and transfers callers.

From $6,900 · License $2,450 first year Delivery in 20–30 working days
A clipboard beside a linked flow-node sculpture and looping sync arrows, showing a question resolved and logged.
Front Line

AI Customer Support Agent

Resolves customer questions across chat and email using your knowledge base and hands off complex cases.

From $8,300 · License $2,950 first year Delivery in 20–30 working days
Sound wave sculpture, clipboard and desk phone in a diagonal stack, representing troubleshooting a support call.
Inbound

AI Voice Customer Support

Resolves support calls using your knowledge base with human transfer.

From $9,700 · License $3,450 first year Delivery in 20–30 working days