Article 15 and 17, on the 30-day clock.
A DSAR is one phase of the photo-consent lifecycle. Do consent-at-capture upstream and the downstream answer will be trivial. Until then, here is how Ansikt helps you answer.
Two requests. Same panic.
A subject wants every photo of themselves. An auditor wants the consent basis for every published image. Both arrive without warning. Both come with a clock.
"I want every photo of me from the last five years." Where do you even start?
"Show me your consent basis for each published image." Your spreadsheet won't cut it.
One request. Two endings.
A subject asks for every photo of themselves. Toggle between the manual process and the Ansikt response to the same request. Same person, same archives — very different ending.
- 01 Email IT for an export of every cloud drive that might contain photos +3 days
- 02 Skim folders by hand. Open every "events 2023" archive. Hope the filenames helped. +9 days
- 03 Email Comms for the website CMS. Ask Marketing about old campaigns. +5 days
- 04 Build a spreadsheet of "photos checked." Worry it's incomplete. +7 days
- 05 Send what you have. Pray nothing surfaces in old SharePoint. day 28
- 01 DSAR arrives. Open Ansikt and paste the requester's reference photo. 5 sec
- 02 Every connected source is already scanned. Search returns every match. 0.4 sec
- 03 Review uncertain matches, confirm or reject. Audit trail captured automatically. ~6 min
- 04 Export a regulator-ready PDF with every appearance, source URL and confidence. 10 sec
- 05 Reply to the requester. Day 1 of the 30, not day 28. done
Search an existing archive. 0.4 seconds.
A working mock of the Ansikt console. The fictional archive holds 12,418 images across seven sources. Pick a name to see what a search returns when recognition has already done the work.
One phase of a bigger loop.
A DSAR is the symptom. Consent drift is the cause. The legal mapping has its own page.