Consent, Privacy, and Data Handling
Which consent purpose Meta Sync reads, what data Meta actually receives, and what happens on an erasure request.
Ad Targeting Is Its Own Consent Purpose
Meta Sync only reads leads with an active ad targeting consent grant in Lead Hub — a separate purpose from email marketing or WhatsApp consent. A lead who's opted into email campaigns is not automatically eligible for Meta Sync, and opting into ad targeting doesn't make a lead eligible for email campaigns either.
Meta Never Sees Raw Contact Details
Phone numbers and email addresses are converted to SHA-256 hashes on SMLLR's own servers before anything leaves them. Meta receives only these hashes and matches them against its own user base — your leads' raw phone numbers and emails are never transmitted to Meta.
Suppressed Contacts Are Always Excluded
Any contact on your account's ad-targeting suppression list is automatically excluded from every sync, and removed from your Custom Audience if they were previously synced before being suppressed.
Erasure Removes Contacts From Meta Too
If a lead is permanently erased from Lead Hub (a deliberate, explicit erasure action), that erasure also removes them from your Meta Custom Audience if they'd been synced — not just from SMLLR's own database. This is the one exception to Lead Hub's usual data-retention rule, since a synced audience entry is derived personal data that shouldn't survive an erasure request.
Was this article helpful?