# Audience data sourcing & compliance

How Zernio sources, hashes and gates customer-list audience data per ad platform and region, and the fields you send to declare it.

Upload a customer list to declare where the data came from, whether you have consent, and each contact's region. Zernio hashes every identifier, maps them to each platform's native fields, and enforces the rest.

## The principle

You own the lawful sourcing. You are the data controller for the list you upload; the ad platform is your processor or an independent controller for the match.

You warrant that you collected the data lawfully and may use it for advertising. Zernio adds hashing, native-field mapping, and consent enforcement on top.

<Callout type="warn">
No platform accepts raw email or phone from Zernio. Send plaintext to our API; we normalize and SHA-256 hash each value before upload. We never transmit unhashed PII to a platform.
</Callout>

## What we do with your data

- **Hash.** Email is lowercased and trimmed, phone reduced to digits, then both are SHA-256 hashed. Only the hash leaves Zernio.
- **Map data source.** `dataSource` becomes Meta's `customer_file_source`. For Google it must be `first_party`; `partner_provided` or `both` makes Google reject the audience.
- **Map consent.** `consent` becomes Google's native consent object. On Meta, a California contact is uploaded with Limited Data Use (LDU).
- **Gate.** A contact in a consent-required region without granted consent is dropped before upload, on every platform, so non-consented EEA data is never sent.

## By platform

Each platform treats sourcing and consent differently. Where a native field exists, your declaration flows into it; otherwise Zernio enforces the rule before upload and the platform's own terms govern.

| Platform | Data source | Consent | Hashing | List minimum / retention |
|---|---|---|---|---|
| <PlatformName slug="meta-ads" /> | `customer_file_source` (native) | LDU for California (native); EEA gated by Zernio | SHA-256, all identifiers | No create minimum; raw list deleted after match |
| <PlatformName slug="google-ads" /> | First-party only; partner or both rejected | Native consent object; EEA needs granted since March 2024 | SHA-256; country and zip sent plain | ~5,000 recommended; membership up to 540 days |
| <PlatformName slug="linkedin-ads" /> | By contract; no API field | Member opt-in on LinkedIn; EEA gated by Zernio | SHA-256 email; names plain | 10,000 rows, min audience 300; list 30d, audience 90d |
| <PlatformName slug="x-ads" /> | By contract; no API field | No API field; EEA gated by Zernio | SHA-256, lowercased | ~100 matched active users to target |
| <PlatformName slug="tiktok-ads" /> | By contract; no API field | No API field; EEA gated by Zernio | SHA-256 | 1,000 file entries; raw file deleted after build |
| <PlatformName slug="pinterest-ads" /> | By contract; no API field | No API field; opted-out lists banned; EEA gated | SHA-256 | ~100 matches to use the audience |
| <PlatformName slug="reddit-ads" /> | By contract; no API field | No API field; EEA gated by Zernio | SHA-256 only | 1,000 users; list expires one year after update |

Only Meta and Google expose consent or data-source fields in their API. For the other five, Zernio enforces consent before upload and the platform's advertising terms govern, which you accept when connecting the account.

## By region

The `region` you send on a contact (an ISO country like `DE`, or `US-CA` for California) decides which rule applies.

- **EEA, UK and Switzerland — consent required.** That is the 27 EEA states plus `GB` and `CH`. A contact here is dropped unless its `consent.adUserData` is `granted`; Zernio enforces this on every platform.
- **United States — opt-out.** Upload is allowed with notice and an honored opt-out. For a California contact (`US-CA`), Zernio attaches Meta LDU; on platforms with no LDU equivalent, suppress opted-out contacts at source before upload.
- **Brazil (LGPD).** Marketing rests on consent or a documented legitimate interest. Treat it like the EEA for a safe baseline.
- **Canada (CASL/PIPEDA).** Commercial messaging defaults to express consent. Gate uploads on opt-in.

<Callout type="info">
Opt-outs are your responsibility to keep current. Remove an opted-out contact from a list, or send a remove request. Pinterest explicitly bans uploading anyone who opted out of targeted advertising.
</Callout>

## Pass data source, consent and region

Declare the data source when you create a `customer_list` audience. It is optional and defaults to the compliant baseline (Meta `USER_PROVIDED_ONLY`, Google `first_party`).

```bash
curl -X POST "https://zernio.com/api/v1/ads/audiences" \
  -H "Authorization: Bearer $ZERNIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "accountId": "664abc123def456ghi789",
    "adAccountId": "act_123456789",
    "name": "High-value customers",
    "type": "customer_list",
    "dataSource": "first_party"
  }'
```

`dataSource` is one of `first_party`, `partner_provided` or `both`.

Consent and region are set when you add members — per contact, or as a batch-level default that each contact may override. Each `consent` field is one of `granted`, `denied` or `unspecified`.

```bash
curl -X POST "https://zernio.com/api/v1/ads/audiences/{audienceId}/users" \
  -H "Authorization: Bearer $ZERNIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "consent": { "adUserData": "granted", "adPersonalization": "unspecified" },
    "region": "US",
    "users": [
      {
        "email": "john@example.com",
        "region": "DE",
        "consent": { "adUserData": "granted", "adPersonalization": "granted" }
      },
      { "email": "jane@example.com", "region": "US-CA" },
      {
        "phone": "+1234567890",
        "region": "GB",
        "consent": { "adUserData": "denied", "adPersonalization": "denied" }
      }
    ]
  }'
```

In this batch: the German contact has granted consent, so it uploads. `jane` is in California, so Meta receives her with LDU. The UK contact denied consent, so Zernio drops it before upload everywhere.

## FAQ

**Do you ever send raw email or phone to a platform?** No. Every identifier is normalized and SHA-256 hashed inside Zernio. Only the hash is uploaded.

**What if I omit `dataSource`, and send no `consent` on upload?** The audience stays on the compliant default: Meta `USER_PROVIDED_ONLY`, Google `first_party`, and no consent gating. Nothing is dropped.

**Why was my Google audience rejected?** Google Customer Match accepts first-party data only. A `dataSource` of `partner_provided` or `both` is refused for Google; use `first_party`, or target Meta.

**Who is the data controller?** You are, for the list you upload. The platform acts as your processor or an independent controller for the match, under the terms you accept when connecting the account.

**How are opt-outs handled?** Keep them current in your own system and remove opted-out contacts, or send a remove request. California opt-outs map to Meta LDU; elsewhere, suppress at source.

## Related

- [Ads API](/products/ads)
- [Create audiences on Meta](/platforms/meta-ads/audiences)
- [Create audiences on Google](/platforms/google-ads/audiences)
- [Ad platform support](/platforms/advertising)
- [Conversions API](/products/conversions-api)