glossary Data + launch boundaries Request Scan form · Production Launch Gate

Consent Boundary

A consent boundary defines what the user is consenting to when they submit the public intake, and what the surface must display before that submission. The current OmniLabs prototype is mock-mode by default and ships a draft consent surface; production consent language and the conditions under which it applies are defined separately and reviewed before any endpoint is enabled.

group · Data + launch boundaries scope · entity layer type · DefinedTerm

Definition

A consent boundary describes the specific consent text the user sees, the specific actions that consent covers (intake delivery, follow-up contact, processor disclosure), and the operator-side handling that the consent enables. It is one of four operating boundaries — intake, consent, anti-spam, retention — that together define the public intake posture.

Why it matters

Consent surfaces are easy to ship and hard to retrofit. Defining the consent boundary before the endpoint is shipped means the consent text and the endpoint behaviour are coherent from day one, instead of diverging the first time a stakeholder asks for a small copy change.

Explore related entities

  • Intake Boundary The operating boundary that defines which prospect data the public intake collects, which fields it does not, and how the surface enforces both.
  • Anti-Spam Boundary The operating boundary that defines the minimum spam and abuse controls a production intake surface must hold before being enabled.
  • Data Retention Boundary The operating boundary that defines how long prospect data is retained after intake, when it must be deleted, and who is responsible for both.
  • Production Launch Gate The operating gate that production launch must clear: reviewed Privacy Policy and Terms, intake/consent/anti-spam/retention boundaries, endpoint scope, analytics disclosure, and the production-domain plan.
  • Public-Signal Diagnostic A diagnostic review that uses only publicly observable surfaces of a business — no credentials, no shared accounts, no internal data movement.
[CLAIM BOUNDARY] The consent boundary is an operating-process boundary documented for this project. It is not legal advice and does not substitute for qualified-counsel review of the consent surface and processor disclosures that production launch requires.
See the Revenue Scan request Back to Data + launch boundaries