Paste your CRM field list. Get back what each field is, what it owes, and what you can feed to AI.
Every field classified: personal data or not, the lawful basis it needs, how long to keep it, and whether it can go into an analysis model as it stands. Plus a draft record of processing per object. First run needs no account and nothing you paste leaves your browser.
| Field | What it is | AI use |
|---|---|---|
| Health Notes | Health or medical information. Special category. | never |
| Lead Score | Lead score. Profiling: needs a basis and a notice. | with a basis |
| Email Opt Out | Opt-out flag. Keep for ever, never delete. | usable |
| Description | Free text. Nobody knows what is in it. | never |
| Passport Number | Government identifier. Should not be here. | never |
| Industry | Firmographic. Not personal data. | not personal |
Paste the fields, not the data
The list from your CRM's fields screen is enough: object, field name, type. Names are matched against a dictionary of what CRM fields actually hold, and a field nobody can name is flagged rather than guessed. If you paste a records export instead, fill rates are read and the values themselves can overrule the name (a "notes" column full of email addresses is contact data).
See what each field owes
Personal data or not. Special category or confidential. The lawful basis a controller usually relies on for it. A retention rule you can actually run. And the verdict the CRM project needs this quarter: usable for AI analysis as it stands, needs a basis and a notice first, or never.
File the record
Per object, a draft record of processing (GDPR Art. 30, CPRA recordkeeping) built from the fields you hold, the gaps that need closing before the AI project starts, and the controls the register is evidence for, with the artefacts an auditor accepts for each.
Why a register and not a data-discovery platform
The funded tools want to scan every system you own before they show you anything. Your CRM's field list already exists, and the person who administers it can paste it in a minute. What that list lacks is the column that says what each field is under privacy law and whether it can go anywhere near a model. That is the column this builds, from the names you already have, with no scanner, no connector and no account.