Integrate at the edge without surrendering first-party control.
A partner integration is a contract with three obligations: a documented consent receipt, a minimum cohort threshold, and a quality control obligation. BingBong does not become a substitute for first-party responsibility.
Edge integration shape.
Token request
Edge requests a token via a documented endpoint. A randomized opaque token is returned with key identifier and rotation policy.
First-party filter
Partner filters identity-bound fields at the edge before transmission. Direct identifiers do not enter the event domain.
Provenance receipt
Partner receives a provenance receipt for the integration: policy version, suppression policy, and ingestion window.
Consent is a partner obligation.
BingBong does not assume consent. Consent is documented per surface, per region, and per data category, and is revocable from the partner's side as well as the consumer's side.
- A documented consent receipt must exist for every token issuance and every event ingestion.
- Consent receipts must be replayable in case of governance review or audit.
- Revocation must propagate to ingestion and cohort construction within the documented window.
- Consent categories must align with the surface's privacy notice and applicable law.
Why cohorts have a minimum count.
The minimum count is not a marketing figure. It is a control against singling-out and near-singling-out by side-channel. Cohorts below the threshold are suppressed at the boundary, not at the buyer.
| Tier | Minimum count (DESIGN TARGET) | Use |
|---|---|---|
| T0 · exploration | ≥ 5,000 | Internal model evaluation only; never delivered to a buyer. |
| T1 · standard | ≥ 1,000 | Standard buyer delivery. Default for most contracts. |
| T2 · sensitive | ≥ 25,000 | Required for any cohort that intersects sensitive-class signals or restricted categories. |
| T3 · governance | per-cohort override | Set by the governance function; never reduced below T1. |
The controls a partner is accountable for.
- Edge filter integrity — identity-bound fields must be filtered before transmission.
- Consent replay — consent receipts must be replayable on demand.
- Revocation propagation — partner systems must honor revocation within the documented window.
- Incident reporting — partner incidents that touch a token must be reported within a documented time bound.
- Audit cooperation — partner must cooperate with BingBong's governance review on a defined cadence.
Become a partner.
Partner onboarding is gated behind the policy, threshold, and quality controls above. The form below is a design demo and does not transmit data.