Setup and control
Data protection requests, answered from the person’s record
The everyday work of UK GDPR, done from the person’s record. Staff can export everything held about someone, anonymise or erase them, keep records for as long as the organisation’s schedules say and no longer, and stop anything being removed while a legal hold is in place.
What it does
Requests from a person
- Export everything held about a person for a subject access request, including what was disposed of under a retention schedule.
- Anonymise a person, keeping the history without their identity, or erase them completely.
- A person marked “do not share” left out of everyday downloads and of data given to outside organisations.
- Staff can download the data held about their own account.
Keeping and removing
- Retention schedules for safeguarding concerns, allegations against staff and volunteers, criminal record check details, withdrawn consent, and records with no recent activity, each with its reason written down.
- Schedules start by reporting what they would remove; nothing is removed until the organisation switches them on.
- Every removal logged.
- Legal holds on a person or a programme, honoured by every schedule, anonymise and erasure.
The organisation’s records
- The privacy notice version, the policies relied on, and how criminal record information is handled.
- How long an adult’s consent lasts before it is asked again, and whether marketing consent is confirmed by email.
- Short privacy checklists recorded before the portal or website chat go live.
- A full export of the organisation’s data as spreadsheets, available even when a subscription is paused.
Control and safety
- Exporting a person, erasing them and setting a legal hold each need their own permission.
- Views of sensitive and restricted records, and of criminal record details, are logged.
- An erased person’s documents, messages and files are removed with them.
Works with
- Consent: consent history, which a subject access export includes.
- Roles, permissions and private records: restricted records and sensitive fields.
- Compliance checks: retention of DBS details.
- API: a deletions feed for systems holding copies.
Good to know
- Records are stored in the UK.
Call it what you call it
Organisations rename this to: Subject access requests, Right to be forgotten, GDPR, Data retention.
Which plan you need
See what each plan includes and its limits.
See how Affinux would work for your team
A 30-minute demo, shown with your type of organisation. Or start a free trial and explore with sample data.