Use caseData privacy, banking

Mapping the sensitive data you hold

4.1 million files, six sources, and a data map nobody trusts. ID scans and doctor's notes sit in old folders any employee can open.

Every source is read in place, nothing moves during the scanEach finding points to a folder, a file and a pageEvery fix has an owner and is checked by the next scan

The discovery reportDiscovery report

4.1 M files read where they sit, 0 moved. Each finding keeps its location, its category and the rights on its folder.

source · 6 sources, 3 nights of scheduled waves
Actions on this inventory
Each location

Sensitive data, wide rights · its owner decides the fix

01

The friction

At a glance

14,800 driver's license images sit in a 2016 scan folder that every employee can read. Nobody put them there to cause harm: a scan saved to a share, a spreadsheet exported for one campaign, a doctor's note filed next to a vacation planner. The privacy officer cannot set priorities without a map, and the IT director cannot lock a share without knowing what it holds.

This inventory reads the files themselves. The operations engine works through every source in place, the AI identifies personal and confidential information, and the report becomes the work list. The privacy officer checks the findings on a sample, and each data owner decides what happens to their own data.

Inventory INV-2026-01Operations engine
Six sources, one count. Each source with its volume, read in scheduled waves.
Discovery reportOperations engine
412,000 findings, 38 places. The report narrows the scan to the locations somebody has to fix, after a person has checked a sample.

One screen counts, the other turns the count into places to fix. Underneath both: the scope is agreed before anything runs, the findings are checked before anyone reports them, and every fix belongs to the person who owns the data. Dana's month follows, starting with the list of sources.

02

The scope

A scan is only useful if its scope is clear. Marcus and Dana agree on the sources and the categories before anything runs.

Step 1Discovery

The sources are listed, and nothing will move

Marcus Reed, the IT director, lists the sources with Dana Whitfield, the privacy officer: the document repository, three network drives, the SharePoint sites of the retail bank and an old scan archive. Each one is connected for discovery, which analyzes content where it sits.

Inventory INV-2026-01 · SourcesOperations engine
The scan reads. File dates and folder rights stay as they are.
The scan cannot damage what it readsNothing is moved, renamed or opened for writing. The data owners agree to the scan because it changes nothing.
Step 2AI check

The categories to look for are chosen

Dana picks what matters for the bank: account and card numbers, Social Security numbers, images of driver's licenses and passports, and health data, which HR must keep confidential and apart from personnel files. The AI will look for each of them in text, scans and images.

Account and card numbersSocial Security numbersDriver's license and passport imagesHealth data

She sets a confidence threshold. A finding below it goes to human review instead of the report.

Detection profileOperations engine
The profile is saved, so the next scan uses the same categories and the same threshold.
The privacy officer decides what counts as sensitiveThe categories are hers, written down and versioned, before a single file is read.
Step 3Operations

The scan runs in scheduled waves

The scan starts on Friday evening and works through the sources in waves. On the scan archive, Marcus limits the load so the old server stays responsive during the day. He follows throughput, errors and remaining volume while it runs.

Scan in progressOperations engine
If a worker stops, the others keep going, and the wave resumes where it stopped.
Four million files, without a crash or a restartAn interruption costs a batch, not the inventory. Nothing is read twice, nothing starts over.
03

The reading

The scan is finished. Dana turns a long list of findings into a short list of places that need attention.

Step 4Reporting

The report becomes the work list

The discovery report lists each location with the categories it holds and the rights inherited on its folder. Dana sorts on both. One line stands out: \\fs02\Credit\Scans_old holds 14,800 images of driver's licenses, and every employee can read it.

Discovery reportOperations engine
A location is serious when it holds sensitive data and wide rights at the same time.
The first fix goes where the exposure isDana starts with the folder that holds the most and lets the most people in.
Step 5Viewer

A sample is checked before the numbers are trusted

Before reporting anything, Dana opens 50 findings in the viewer. In a training deck, the account number flagged on slide 12 is the example account printed in the bank's own procedure. She marks it a false positive. Discovery had already listed 340 identical copies of the deck, and the same decision applies to them.

Training deck, payments.pdfViewer
Each finding opens at its page, in the browser, with nothing downloaded.
The committee gets figures a person has checkedTwo false positives out of fifty, both explained. The numbers hold up when someone asks how they were made.
Step 6Discovery

Health data where it should not be

The second priority is an HR team folder in Charlotte. The AI found 212 doctor's notes and three medical reports saved by managers next to the vacation planners. The HR repository already has a restricted class for exactly these documents.

\\fs03\HR\Team_CharlotteOperations engine
The scan only reports. Moves are decided in the plan, by the data owner.
Try this on your own estate: how many team folders hold documents that already have a proper, restricted home somewhere else?
The right home already existsThe fix is to file the doctor's notes where HR's rules and rights already apply.
04

The plan

A map earns its keep when each line has an owner and an action. The AI proposes, and each data owner rules on their own files.

Step 7Workflow

One action and one owner per location

For each location, the AI proposes one action: restrict access, move the files to the repository class that fits them, or delete copies that duplicate a filed original. Dana reviews the list, changes one move into a deletion, and assigns each line to its data owner with a due date.

Remediation planCase management
Each line is a workflow task, with its owner and its date.
Nobody fixes someone else's dataThe privacy officer sets the priorities. The head of each team decides what happens to the files their team created.
Step 8Operations

The owner approves, and the move is checked file by file

Mei Chen, head of credit operations, approves both tasks for Scans_old. The operations engine moves the 14,800 images into the loans class of the repository, with credit operations' rights and the class retention rule, and restricts the old folder. The reconciliation report compares what was expected with what arrived.

\\fs02\Credit\Scans_oldOperations engine
Source and target identifiers sit side by side on each line of the report.
A fix is done when the report says soEvery file has its line: where it came from, where it went, which rule applied. The next scan confirms the folder is clear.
Step 9Reporting

A report for the privacy committee

At the end of the month Dana presents the inventory: what was scanned, what was found, what is fixed and what is planned. The figures come straight from the discovery report, which exports as it is, and every line opens down to the folder it describes. From now on, the scan runs every quarter.

Inventory INV-2026-01Operations engine
The same profile runs every quarter, so the figures compare.
The map is kept up to dateA quarterly scan with the same profile shows what was fixed and what came back.
05

The verdicts

Every location in the report gets one of three tags. Dana reads the tag first, because it tells her who should hear about the folder next.

Clear

Nothing sensitive found

Or only false positives, checked by a person on a sample.

What follows: no action, the location is checked again next quarter.
Misplaced

Sensitive data in the wrong place

Doctor's notes in a team folder, ID scans outside the loans class. The proper home is named.

What follows: a move is proposed, the data owner approves it.
Exposed

Sensitive data, wide rights

The location holds health or ID data and too many people can open it.

What follows: access is restricted first, then the files are moved or deleted.
Where the AI stops

It moves nothing, deletes nothing and changes no folder right. Every change is approved by the data owner, carried out by the operations engine and written into the report line by line.

The AI reads, identifies and proposes. The plan names who acts on each location, and that holds across four million files.

06

In numbers

Counted on the first run of INV-2026-01. A bank with more shares, or older ones, will land on other counts.

0 filesmoved or changed while the scan ran across six sources.
50 findingschecked by a person in the viewer before any figure went to the committee.
1 ownerper location, with a task, a due date and a report that proves the fix.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

Three principles behind the figures

Zero blind spotsProductivityThe files themselves are read, so the map shows what is really there. The data map can then be checked against it.
Zero untracked fixesProcess reliabilityEach action is a task with an owner, and every file moved has its line in the report.
Decision supportA person decidesThe AI proposes the action. The privacy officer sets priorities and the data owner approves.
07

For your teams

Marcus runs the servers, Dana owns the map, and the team heads own the files. A scan this size needs all three on board.

Risk and compliance

Privacy officers

Asked where personal data sits, you can only answer from the data map.

  • The categories to look for are yours, versioned.
  • Findings are checked on a sample in the viewer.
  • Locations are read on what they hold and who can open them.
  • The report exports as it is for the committee.
IT and architecture

CIOs and IT directors

A scan of four million files sounds like a threat to servers you have to keep up.

  • Content is analyzed in place, nothing moves during the scan.
  • The load on a fragile source can be limited.
  • An interrupted wave resumes where it stopped.
  • Network drives, SharePoint and your repository through connectors.
Business operations

Data owners

The cleanup plan for your files was written by someone who has never opened them.

  • Each action on your data comes to you as a task.
  • You see why the action is proposed, with its source.
  • Nothing moves until you approve it.
  • The report shows each file that moved, and where.

Where to start

With one share. Pick the network drive your teams have used the longest, and run the scan on it alone. The findings on one share are enough to set the priorities for the rest.

The scan plugs into the network drives, SharePoint sites and repository you run today. Nothing has to be migrated first.

Let's talk

Scan one share and see what it holds

Choose one network drive or one repository folder. We will run the scan with your privacy officer and your IT team, and read the findings together.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.