Skip to content

Check your contacts for GDPR gaps

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.6.2 on 2026-11-15.

Any GDPR gaps in my contacts?

Ask in plain words. Quox reads ContactsQ's compliance bands and tells you how many contacts need attention, and in which band.

What you get: a count of contacts with no lawful basis recorded and of contacts in a special category, plus the other compliance bands, from ContactsQ’s own compliance read. You need: a signed-in profile. About 2 minutes.

The run here is on a scratch org seeded with fictional contacts.

quox · talking to Quox

Quick GDPR check on my contacts: how many have no lawful basis recorded, and how many are special category?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 5ms

◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 5326 duration ms · 7.2s

⛓ AEE │ envelope opened · ops.tool · quox_cli ok

⛓ AEE │ envelope opened · stream_success

14 contacts have no lawful basis recorded, and none are special category.

• No lawful basis: 14 contacts. The compliance read lists every ID, so the list isn't
  truncated.
• Special category: 0.

The same read shows nothing else needing attention: no overdue Article 14 notices, no
candidates expiring within 7 days, and no consents expiring within 30 days.

The 14 are the ones to fix. For each, record a lawful basis, such as consent, contract
or legitimate interest. Until then they're a gap in your Article 30 record. I can pull
the list with names, or look up the command for recording a basis, if you want either.

14.2s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.6.2, 15 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 15 Nov 2026 · test report mwh8km

Quox made one call, through its governed CLI tool, to ContactsQ’s compliance read. It reported 14 contacts with no lawful basis recorded and none in a special category, and added that the same read showed no overdue Article 14 notices, no candidates expiring within 7 days and no consents expiring within 30 days. It suggested recording a lawful basis for each of the 14 and offered to pull the list with names. It changed nothing.

compliance bands
quox contacts complianceBand                      Count    IDsnotice_overdue            0candidates_expiring_7d    0no_lawful_basis           13       ct_...a911,ct_...5038,ct_...consents_expiring_30d     0special_category          0Ⓠ CONTACTSQ │ contacts compliance │ notice_overdue=0 candidates_expiring_7d…
From a later run on the same scratch org. Counts move as contacts change: this read showed 13 with no lawful basis where the conversation above saw 14.

Each band is a count with the first few contact ids. no_lawful_basis is the contacts with no basis on record, and special_category is the contacts holding special category data. Add --json for every id in each band.

Quox did not count anything on its own. It ran the same compliance read that quox contacts compliance runs and reported the bands that came back. The conversation and the CLI read the same bands; the numbers are whatever your contacts hold at the moment you ask.

quox contacts compliance only reads and raises no approval. Run it and compare the no_lawful_basis and special_category counts with what Quox told you. If they disagree at the same moment, trust the CLI and tell us.

Nothing to undo: reading the bands changes nothing. Recording a lawful basis or a consent for a contact is what moves it out of a band; see Handle a privacy request.