Handling data subject requests: a manual process, Osano, DataGrail and Transcend compared
When a customer asks what data you hold or asks you to delete it, the clock starts. What a request process has to do, when a spreadsheet is enough, and how three request platforms differ.
The first request
An online retailer gets an email through its contact form: a customer in California wants to know what personal information the company holds about her and wants it deleted afterwards. Nobody on staff has handled one before. The customer’s data is in the e-commerce platform, the email marketing tool, the help desk, the accounting system and an export someone made for a promotion last spring.
If the California Consumer Privacy Act applies to the business, the response is due in 45 calendar days, according to the California Attorney General, with one extension of another 45 days if the business tells the consumer. Under the GDPR, Article 12(3) requires a response without undue delay and in any event within one month, extendable by two further months where necessary, with the person told about the extension within the first month. Whether either law applies depends on the business, its size and where its customers are; that is a question for counsel. The practical problem is the same everywhere: find the person’s data in every system, verify who is asking, respond on time and keep a record.
What any request process has to do
Whether it runs on a spreadsheet or a platform, the process needs six steps:
- Intake. A clear way to submit a request, and a way to recognize one that arrives by ordinary email.
- Verification. Confirm the requester is who they say they are before you hand over or delete anything. A request from an impostor, answered without checking, hands one customer’s data to someone else.
- Discovery. Find the person’s data in every system on your data map, including vendors who hold it for you.
- Action. Export, correct, delete or opt out, system by system, with exceptions for data you must keep by law.
- Response. Tell the person what you did, in plain language, by the deadline.
- Record. Keep a log of each request, the dates and what was done. It is your proof if a regulator asks.
Step 3 depends on a data map. If you do not know which systems hold customer data, no tool will find it for you; the platforms below can help with discovery, but they still need to be connected to your systems.
Option 1: a manual process
For a business that receives a handful of requests a year, a manual process is reasonable:
- a web form or a dedicated mailbox for requests,
- a one-page procedure listing every system to check and who checks it,
- a verification step, such as confirming through the email address or account already on file,
- a spreadsheet log with received date, due date, extension date if any, systems checked and response date.
It costs staff time instead of license fees. The risks are missed deadlines when the one person who knows the procedure is out, and missed systems when the data map is out of date. Put the due date on a shared calendar the day a request arrives.
Option 2: Osano Subject Rights Management
Osano positions its product as covering the whole workflow, from identity verification through communication, fulfillment and data delivery. Its product page says localization and ID verification help screen out inappropriate or fraudulent requests, that automated data discovery searches connected data stores for the requester’s data, and that the product is meant to help teams answer each request inside its deadline, with configurable timelines and internal deadlines. Osano also advertises a “No Fines, No Penalties” guarantee, which it says applies if a fine is incurred while managing requests with Osano’s workflows and processes. Pricing is not published; the page says it is tailored to volume, deployment scale and add-on modules.
Good fit: a small or mid-sized business that also wants consent management and other privacy tools from the same vendor.
Ask about: which of your specific systems connect, and what the guarantee’s terms actually cover.
Option 3: DataGrail Request Manager
DataGrail says Request Manager automates access, deletion and opt-out requests, collects them through branded web forms, and verifies requesters with what it calls Smart Verification, using data the company already holds. It describes processing requests across internal, third-party and AI systems, a single dashboard for tracking, and built-in project management for working with internal teams and vendors. DataGrail’s page points to more than 2,000 integrations and lists a separate Live Data Map product. Pricing is not published.
Good fit: a business with many SaaS tools holding customer data, where the integration list is the deciding factor.
Ask about: how verification works for customers without an account, and how requests are handled in systems that have no integration.
Option 4: Transcend DSR Automation
Transcend says its DSR Automation verifies every requester, automates intake, verification and fulfillment so staff handle only exceptions, logs every action and tracks deadlines. It describes “thousands of integrations,” support for systems without an API including legacy ones, and translating each request into the identifier each system uses, such as a user ID, account number or advertising ID. It handles requests for your own customers and requests forwarded by businesses you process data for. Its request automation acts on systems found by its separate Data Discovery and Classification product. Pricing is not published.
Good fit: a business with a technical team, many data systems and higher request volumes.
Ask about: how much setup your engineers will need to do, and which parts require the separate discovery product.
Side by side
| Manual | Osano | DataGrail | Transcend | |
|---|---|---|---|---|
| Intake | Form or mailbox | Localized forms | Branded forms | Automated intake |
| Verification | Your own step | ID verification | Smart Verification | Verifies every requester |
| Discovery | Your data map | Automated data discovery in connected stores | Integrations; separate Live Data Map | Integrations; separate discovery product |
| Integrations claimed | None | Connected data stores (no count on the page) | 2,000+ | Thousands, plus custom |
| Published pricing | Staff time | No | No | No |
How to choose
- Count your requests. A few a year and a short system list: start manual, but do it properly. Dozens a month: a platform pays for itself in staff time and missed deadlines avoided.
- Count your systems. Ask each vendor to show a live connection to the five systems that hold the most customer data. The integration count on a website matters less than whether your systems are on it.
- Test verification. Ask how a request from someone with no account is verified, and what happens when verification fails.
- Check the record. Ask to see the audit log for a closed request. That log is what you will hand a regulator.
- Remember the vendors. Your processors and service providers may hold copies. Your contracts should require them to help with requests; under GDPR Article 28, a processor must help the controller respond to data subject requests as far as possible.
When to get help
If you have never mapped where customer data lives, start there. A data map makes a manual process work and makes any platform faster to set up.
Want to talk it through? Book a free 30-minute call with Security Medic Consulting.
Sources
- California Attorney General, California Consumer Privacy Act (CCPA), updated August 28, 2026 (accessed 2026-11-05).
- GDPR, Article 12, Transparent information, communication and modalities (accessed 2026-11-05).
- GDPR, Article 28, Processor (accessed 2026-11-05).
- Osano, Subject Rights Management (accessed 2026-11-05).
- DataGrail, Request Manager (accessed 2026-11-05).
- Transcend, DSR Automation (accessed 2026-11-05).