Use caseData privacy
A former customer asks for every piece of data you hold on him. State law gives 45 days, and masking other people out eats most of them.
One question finds his documents across the repositoryThird-party data is proposed for masking, a person approvesThe case keeps a record of exactly what left
The question returns 176 documents under his name, his two policy numbers and his old claim, each with its document class.
source · the repository, 5 document classesMasks still to approve · the AI lists where, page by page
Nov 3: Brian Holloway's request lands on the customer portal. His data sits in two policies, an old claim, scanned letters and emails filed on other cases. Today the privacy analyst opens each one, reads every page for other people's names, and tracks the deadline in a spreadsheet. The 45 days go into reading, page after page.
Turn the order around. One search lists everything about him, the AI proposes what to mask on each page, and the deadline lives on the case. The analyst and the privacy officer decide on every document and every mask, and the case remembers who decided what.
Put the work list next to the request queue and the calendar of this request shows: the deadline is set the day the request arrives, the scope is known on day two, and every page that leaves has been approved by a person. Below, Brian's request in the nine moves Keisha and Laura actually made.
The clock starts the day the request arrives. First, know whom it concerns and where his data sits.
Brian Holloway fills out the privacy form on the customer portal on Nov 3. The portal calls the repository API: a consumer privacy case is created, with his message as the first document and a due date 45 days later.
Keisha compares what Brian wrote in the form with his former policy record: date of birth, mailing address in Columbus, policy number. They match. She then records on the case every identifier the search will use.
Keisha asks the assistant, in plain words, for every document that carries one of those identifiers. The question becomes a query on the repository. The answer is a table, each row naming its document class, and she exports it to Excel for the file.
The search runs with Keisha's own rights. The privacy team was given read access to the five classes concerned, and nothing outside them comes back.
Finding the documents is half the work. Now each one is checked, and other people are taken out of it, page by page.
Six results carry the same name, a date of birth in 1958 and an address in Dayton. Keisha opens two of them in the viewer, confirms it is another customer, and sets all six to Out of scope with one reason written on the case.
The 2021 claim file names the other driver, her phone number and a witness. In the viewer, the AI flags each of them as personal data about someone else and proposes a mask. Keisha accepts the masks on the driver and the witness, and keeps the body shop's name, which is business information.
Two items are more than a mask: an internal email where a claims adjuster gives an opinion about Brian, and a note from the legal department on a past dispute. Keisha sends both to the privacy officer's approval queue. Laura Bennett keeps the email with the colleague's name masked, and asks the legal department before deciding on the note.
Every mask is approved. What remains is the letter, the delivery and a record a regulator can read.
A right-to-know answer covers more than a copy: the categories of data, why they are held, who received them and how long they are kept. Keisha asks the assistant for a cover letter. The draft takes each of those points from the data inventory and the retention schedule, and cites them. She rewrites the opening and checks every heading.
Laura approves the pack on Nov 26. The masked copy is published to Brian's account on the customer portal. He reads it in his browser and downloads it the same evening. The original files never leave the company's infrastructure, and the masks travel with the export.
The case closes. Tom Becker, the records administrator, can show at any time which documents went out, in which version, which masks were applied, and who approved each one. If Brian writes again next year, the team starts from this list.
On any given day, Brian's request sits in one of three states. Each state tells Keisha what she does next, and who else has to look.
In scope or out, masked or clear, each one has a decision and a name.
Then: the privacy officer signs the pack and the copy is published.The AI lists the pages where it proposed a mask that nobody has approved yet.
Then: the analyst accepts, extends or rejects each one.A legal note, another person's opinion. The analyst flags it with her reason.
Then: the privacy officer decides, and the reason is written on the item.It withholds nothing, sends nothing and masks nothing on its own. Keisha approved every document that left, and Laura signed the pack, each under her own login, with her name on the case.
The AI searches, flags and drafts. The rules live in the case itself, so they still hold when requests arrive by the dozen.
Counted on Brian's request, answered on day 23. A company with more applications holding customer data will count higher.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
Brian's request crosses three desks before his copy goes out, and each desk worries about something else.
Most of your 45 days go into searching and reading, page after page.
You sign a response you never had time to read in full.
Each privacy request lands on your desk as one more extraction job.
With one closed request. Take an access request your team answered by hand last year, and run the search and the redaction review on the same documents. You will see the difference on material you know.
Nothing new to install around it: the portal, the case files and the documents are the ones you run today.
Your move
Bring a closed access request and a sample of its documents. We will run the search and the redaction review with your privacy team on that material.