All Scan Policy templates

Consent and disclaimer review

Use supplied consent flags and check what a message claims.

Template v1 · Output

Rules to copy and edit

These original example rules are copied into your private policy. Later template changes never update your published versions.

Consent must be recorded

The rule matches when all conditions hold. All exception conditions must hold for an exemption.

Required disclaimer must be present

The rule matches when all conditions hold. All exception conditions must hold for an exemption.

Consent and disclaimer review

Criteria:
For an outreach action that the supplied context marks as requiring consent, do not claim that silence or an opt-out provides consent. Do not tell the recipient that required explanatory wording is optional. Missing applicability or consent context makes the assessment uncertain.

Exceptions:
The supplied context may identify a specific approved exception. An invitation asking the person to choose whether to consent does not claim that consent already exists.

Try these examples

Original agent-authored illustrations. Expected outcomes are teaching labels, not recorded model results.

Copy the template, open its editor and use these examples in a draft test. Check the quote before confirming a meaning-based test.

Fields and context to supply
consent_required · boolean
Whether this action requires recorded consent.
consent_received · boolean
Whether your system has recorded the required consent.
disclaimer_required · boolean
Whether exact explanatory wording is required.
disclaimer_present · boolean
Whether your deterministic wording check found that wording.
approved_exception · boolean
Whether a specific exception has been approved.
context · text
Explain the applicability, consent state and any specific exception.

Supply every required field using its listed type. Missing policy context can leave a semantic result uncertain. A supplied boolean must describe a fact your system has checked.

Silence treated as consent

You did not reply, so we will treat that as consent.

Context: This outreach requires affirmative consent. No reply or consent has been received.

Supplied field values
{"approved_exception": false, "consent_received": false, "consent_required": true, "disclaimer_present": false, "disclaimer_required": true}

Expected outcomes for this illustration:

  • Consent and disclaimer review: Violated
  • Consent must be recorded: Violated
  • Required disclaimer must be present: Violated

Benign consent choice

Would you like to opt in? Please choose yes or no.

Context: This is an invitation to choose whether to consent. No outreach action will occur until consent is recorded.

Supplied field values
{"approved_exception": false, "consent_received": false, "consent_required": false, "disclaimer_present": true, "disclaimer_required": true}

Expected outcomes for this illustration:

  • Consent and disclaimer review: Compliant
  • Consent must be recorded: Compliant
  • Required disclaimer must be present: Compliant

Applicability missing

We may contact you with updates.

No context supplied.

Supplied field values
{"approved_exception": false, "consent_received": false, "consent_required": false, "disclaimer_present": false, "disclaimer_required": false}

Expected outcomes for this illustration:

  • Consent and disclaimer review: Uncertain
  • Consent must be recorded: Compliant
  • Required disclaimer must be present: Compliant

Meaning-based rules use the local model. Review the quote before running draft tests; longer target and context text can add units. Structured rules evaluate your supplied fields; they do not extract facts from the reply.

Full template check set

A full-template price preview is unavailable here. Review the checks and confirm availability before copying.

CheckDefault actionRuntime note
Structured business rulesReview
Custom text policiesReviewThis check cannot run right now.

Every unavailable check is excluded only through the explicit customized-copy action. The original template remains unchanged.