Data firewall

Only the delivery signal leaves your app.

The firewall turns prompt-adjacent context into coarse topic category and language before anything reaches a configured ad path.

Allowed signal

Topic category + language

The delivery path can use broad categories such as travel, education, coding, or finance, plus locale for policy and language fit.

Blocked by default

Raw prompt text, conversation history, account details, identifiers, and model output are not forwarded in the recommended path.

Failure mode

If consent, config, or routing readiness is missing, the sponsoring path blocks or falls back to a non-semantic mode.

Receives the user request and keeps sensitive context local.

Reduces the request to minimal delivery metadata.

Checks consent, categories, blocked industries, and route readiness.

Receives only the scoped signal needed for a placement decision.

Prompt sharing is off by default in the final server API snippets.

Semantic targeting requires explicit consent state in the request.

Publisher metadata is limited to app-level details and categories.

Missing or invalid setup does not create an implicit live ad path.