Skip to main content

Important and Disclaimers

This page covers critical notes that should be understood before production use.

Reporting is required for full cycle completion​

  • analyse_and_report and analyse_and_report_async are not optional for complete production integration.
  • They finalize the ad workflow cycle after the model response is produced.
  • This confirmation step is part of how publisher ad-placement opportunity is accounted for.

Privacy and data-protection model​

  • The raw LLM response text is not sent to backend reporting as-is.
  • Reporting uses derived metrics and tracking metadata needed for acknowledgment.
  • This design helps reduce exposure risk and supports privacy/safety expectations in application integrations.

Operational recommendation​

  • Always call analyse_and_report or analyse_and_report_async after receiving final model output when enhancement succeeded.
  • Treat reporting as a required production path, not a debug-only step.

Compliance and enforcement​

  • Adstract continuously monitors platform behavior and reporting integrity.
  • False reporting is treated as a severe violation.
  • Violations include cases such as reporting ad placement and then programmatically removing ad content from the final response.
  • Severe violations can result in account/platform bans and legal action.

Terms and conditions​

For full policy details, see our Terms and Conditions: