Delete a single Meta lead via the API (GDPR issue)
We receive leads from Meta lead forms through Zernio (via the lead.received webhook) for recruitment automations we run for our clients. Under the GDPR our clients are the controllers, we’re their processor and Zernio is our sub-processor. That means we have to remove an applicant’s data after a fixed retention period, and right away when someone asks us to delete it.
For WhatsApp conversations this works now, with DELETE /v1/inbox/conversations/{conversationId}. For Meta leads there’s no equivalent: a lead and its form answers stay stored at Zernio until the account’s data is deleted as a whole.
Request: an endpoint like DELETE /v1/ads/leads/{leadId} that permanently removes one lead, including its field data, from Zernio’s storage. Returning 404 for a lead that’s already gone would let us retry safely.
This affects anyone who processes leads for clients in the EU. In recruitment it comes up in every security review, because applicants share personal details with an employer they don’t know yet.
The support team mentioned this is already an open request and should have linked our case (Jobfox) to it, but I couldn’t find the request here.
Log in to comment and vote
Comments1
Miquel Palet López
Nov 16
This is on our roadmap.