If you publish people, account for people.
Ansikt finds where each person appears, links each face to consent, and keeps the audit trail. So you can publish with proof, and answer when asked.
The Ansikt lifecycle
You publish photos of people.
But can you account for them?
Websites, SharePoint, Google Drive, S3 buckets, event archives, marketing campaigns. Photos accumulate across systems. Consent records — if they exist at all — live somewhere else. Keeping the two in sync by hand scales badly.
You published a thousand photos from the annual conference. You have no record of who agreed to appear in any of them.
See this case → The new shootPhotographer shot 400 photos at the gala. Six months later — which had consent records, and which photo is which?
See this case → The reused campaignMarketing wants last year's event photos in a paid ad. Original consent was for the event recap. Now what?
See this case → The expired consentConsent was given for two years. It expired in March. The photos are still live on three pages.
See this case →Photos became easy to publish. Accounting for them did not.
A school, club, newsroom or marketing team can put a face online in seconds. Months later, the consent record may live in a PDF, a spreadsheet, an inbox, or nowhere useful.
The law already says people can ask. Ansikt is the missing working view: who appears where, what they agreed to, what changed, and what you did about it.
Consent drifts. Photos don't.
Ansikt keeps them in sync.
Whether you are dealing with an existing archive, a new shoot, or an incoming request, all three routes feed the same consent-aware system. Connect your sources once. Every photo is recognised, every person is accounted for. * See how the lifecycle works →
Clean up an existing archive
Connect cloud drives, your CMS and SharePoint. Ansikt finds who appears where, so you can attach the consent you hold and see the gaps.
Shoot something new
Collect consent before publication. Each new image enters the system with the people, purposes and allowed channels tied together.
Operate when something changes
Handle a withdrawal, an expiry or an Article 15 / 17 request. Find the affected images, decide what changes, and export the audit trail.
* Faces under ~60px or heavily occluded are less accurate. See accuracy & limits →
A week of Ansikt, in one screen.
One view for consent gaps, expiring rights, pending reviews and takedowns. Open the console and see how Ansikt keeps the work visible.
Built with Danish pragmatism.
Ansikt runs on EU infrastructure, with EU providers. No US vendors. No customer data is shared with third parties.
EU providers only
Production infrastructure runs in the EU, on EU providers. No US vendors.
- EU infrastructure
- EU providers
- EU jurisdiction
No data sharing
No customer data is shared with third parties.
- No external data sharing
- No third-party model training
- Service processing only
Audit log on every action
Searches, exports and review actions are logged with user, timestamp and reason.
- Append-only audit trail
- Per-action attribution
- Exportable records
Tell us what your archive looks like.
We are speaking with organisations that publish people's photos and need consent, takedown, and DSAR workflows to hold together. We'll show the current product path and where your feedback would shape it.