RevivalOps

Data Handling · the custody path, and the facts a review asks for

Where your data goes. What never happens.

The custody path of one CSV export, end to end. Then the facts a data protection review asks for, each stated once. Nothing on this page is a forecast or a claim about results.

THE FLOW

01

Your CRM

Your system, your credentials. Nothing is installed in it and nothing connects to it.

02

One CSV export

You produce it, once, from the agreed field scope. Manual export. No standing connector on the standard path.

03

Operator workstation

Deterministic rules, run locally by the operator. Not uploaded to third-party processing services for analysis.

04

Sealed snapshot

A static file, delivered to you. Your export is deleted or returned at delivery, confirmed in writing.

WHAT NEVER HAPPENS, AT ANY STEP

THE FACTS

PROCESSING
Deterministic rules. Raw exports are never treated as generic model input.
RETENTION
Your export is deleted or returned when the Snapshot is delivered. Confirmed in writing, without you asking. Working copies are deleted 30 days after the engagement ends.
ACCESS
One bounded CSV export of agreed fields. No standing connector, no credentials, on the standard path.
PAPERWORK
One signature. The data processing agreement rides as Annex A inside the engagement agreement. Never a second envelope.
LOCATION
Processed on operator-controlled hardware. Data region: EU/UK.
SENDING
The deliverable is static. Nothing in it can contact anyone. Diagnosis never writes to your CRM.
SCOPE
The export contains only the agreed fields. Full personal names are withheld from the delivered read.