Information we process
- Placement identifiers, short interaction context, intent keywords, categories, agent metadata, locale, country, device, and app metadata.
- Publisher-hashed user or session identifiers and optional privacy-safe signals.
- Advertiser account, campaign, Offer Unit, creative, destination, budget, bid, billing, and conversion data.
- Request IDs, event IDs, timestamps, logs, error records, audit records, and security events.
Information we prohibit
Genesis is not designed to ingest raw personal information in ad request context. Publishers must not send raw email addresses, phone numbers, addresses, government identifiers, credentials, secrets, payment card numbers, or other sensitive personal data.
How we use information
- Authenticate API calls and enforce publisher controls.
- Match requests to eligible sponsored offers and run auctions.
- Record impressions, clicks, conversions, signals, and exports.
- Provide analytics, reporting, billing, payouts, campaign review, policy enforcement, abuse detection, security, support, and compliance responses.
Tracking position
Genesis does not rely on third-party cookies or cross-site behavioral profiling. Attribution uses placement tokens, click redirects, server callbacks, and short-lived event identifiers.
Retention and rights
Raw request context is kept for a short operational window, event-level logs support reporting and reconciliation, and billing, payout, audit, and campaign review records are retained for required legal or financial periods. End-user requests may need to route through the publisher that controls the original relationship.
Requests and contact
Publishers with API access can submit verified deletion and opt-out workflows through /v1/privacy/requests. Privacy and data-rights intake is available at privacy@thegenesis.com.
Related privacy resources
- Formal privacy policy: /privacy.
- Data processing agreement: /dpa.
- Subprocessor list: /subprocessors.
- Publisher disclosure guide: /disclosure.
Privacy FAQ
- Does Genesis use third-party cookies? No.
- Can publishers send raw PII? No; request validation and policy prohibit raw PII in offer context.
- How do opt-outs work? Subject requests use hashed identifiers or session IDs where technically feasible.