Talk to us
Story 05 · For subjects

Leaving the company — and taking your face with you

Tom Andersen · 34 · software engineer leaving Acme Solutions after four years. Wants his photo removed from the Meet-the-Team page, LinkedIn, the brochures and the intranet. Has been Googling his name and seeing his old colleagues' employer-branded photos surface.

4-minute read Open the interactive demo
Step 01

Open Tom's record and trigger Article 17

On Tom's last day, Helle in HR opens Tom's record in Ansikt. Tom opted in when he joined four years ago, so Ansikt has been tracking his appearances ever since — every photo of him across the company is already grouped under his name.

Twelve photos. Internal events, conference talks, the Meet-the-Team headshot, intranet spotlights, brochure stock. Most were on shared drives nobody has audited in two years.

Helle clicks Mark as leaving — start Article 17 at the top of Tom's record. Ansikt looks up Tom's publication log — every channel his photos have been pushed to over four years — and the withdrawal task carries that list automatically. One task per photo, each carrying the channels it landed on. A clear queue rather than a panicked spreadsheet.

Try this yourself
Step 02

Marketing works the queue against the 30-day clock

Theo in marketing opens the Inbox. Twelve open Tom tasks — one per photo of him on file. Each task carries its own channel checklist: careers.acme.com, intranet, LinkedIn, brochures — three or four chips per row depending on where the photo landed. Colour-coded so the work left to do is visible at a glance.

Channel chips: orange for live and still needing a takedown, green for removed, grey for unreachable. The 30-day deadline is on every task. Tom's right to erasure is closing fast, and the queue makes that visible to the people who can actually clear it.

Try this yourself
Step 03

Tom verifies the work, channel by channel

Tom logs in with the magic link. Your active withdrawals sits at the top of his portal — one row per photo. Each row shows the channels that photo landed on: careers.acme.com, intranet, LinkedIn, brochures. Days-remaining on the left, the same channel chips Theo works against on the right.

Colour code matches: orange still live, green removed, grey unreachable. No write actions — Tom does not run the cleanup, he watches it. He does not have to take the company's word for it. The chips do.

Try this yourself
After the queue clears

Article 15 record

Acme prepares Tom's record — every photo Acme ever held, every channel it was on, when each one was removed, who removed it, with what evidence. Tom gets a copy. A downloadable archive Tom pulls himself is on the roadmap.

If a channel stalls

The audit trail is the foundation for a complaint to the relevant data-protection authority. An in-product escalation handoff is on the roadmap too.

That is the loop on the SMB side. Want to see how it works elsewhere?

The same workflow at an adult sports club, at a folkeskole, or from a player's side when a different controller picks her up entirely.

Customer side · S1 The same loop at an adult football club Customer side · S2 The school + the DPO doing it for a folkeskole Subject side · S6 The marquee one — auto-recognition across controllers Live demo Open the Inbox demo All stories Back to the tour
Different scenario? Talk to us