Publisher requirements

Call Genesis only for explicit placements.
Preserve sponsored labels.
Keep main product functionality available during Genesis failures.
Avoid sending raw PII, secrets, credentials, or private files.
Use hashed user and session identifiers where identifiers are needed.
Configure category blocks for sensitive or inappropriate contexts.
Record impressions only when offers are actually rendered.

Prohibited behavior

Hide, remove, or obscure sponsorship disclosure.
Inject offers into sensitive user contexts prohibited by policy.
Auto-click or encourage invalid clicks.
Represent sponsored offers as organic model recommendations.
Send private user data to improve monetization.
Manipulate placement context to attract higher bids.

Placement review

Genesis may request placement screenshots, disclosure examples, category control settings, traffic source details, production-readiness evidence, and test-mode event logs before production access.

Enforcement

Genesis may revoke keys, pause placements, hold payouts, require disclosure fixes, or terminate access for violations. Disclosure rules match SDK defaults and prompt-weaving helpers, and privacy-safe signal rules match API validation.

Onboarding links

The policy is linked from publisher onboarding, production-readiness guidance, documentation, and the global footer.