Your AI policy

Your AI policy says, in named on-and-off choices, what you permit and where you do not want your data used. It is a record like any other: drafted on the Business Portal’s AI policy screen and sealed by a person with their passkey. Change it in one save, and every AI company sees the change on its next request — without re-sealing a single product.

The choices

Choice	When on, you say	Default
answer	AIs may use your data to answer	on
quote	AIs may state a price as your current price	on
reserve	AIs may make a booking or reservation on a person’s behalf	off
purchase	AIs may complete a purchase on a person’s behalf, through a checkout domain you have authorised	off
contact	AIs may contact you on a person’s behalf	off
hand_to_human	AIs must hand the person to you for anything beyond answering	on
cite_as_source	cite you as the source	on
definitive_source	where your record conflicts with a third party, yours wins	on
prefer_over_inference	a field you left out means not stated: AIs must not infer or reconstruct it	on
include_in_recommendations	you may be included in recommendations	on
quote_policy_verbatim	your delivery, returns and warranty wording is quoted verbatim	off
prices_indicative	your prices are indicative	off
state_publish_date	AIs say when your information was last published	on

reserve and purchase can be switched on once MasterDB has completed the additional checks they need; the Business Portal shows when they are available to you.

Contexts where your data must not be used

Ten subject areas where you do not want your published data used to build an AI’s response, even when your record would be relevant. Each is off until you switch it on. On the API each travels as a short code (bc1–bc10) whose meaning is published and never changes.

Code	Context
bc1	Adult and sexual content
bc2	Alcohol
bc3	Crime and illegal activity
bc4	Death, tragedy and disaster
bc5	Firearms, weapons and violence
bc6	Gambling and betting
bc7	Mental health, self-harm and crisis
bc8	Politics and elections
bc9	Regulated advice (medical, legal or financial)
bc10	Tobacco, vaping and recreational drugs

A blocked context is a request about where your data is used, not a statement about your business.

How it reaches AI companies

• Every search row carries your AI policy in force as compact bits, with the version, so an AI company answering from the row alone knows what you permit and which contexts you block.
• Every fetch carries your sealed AI policy record itself, which proves those bits.
• Every receipt names the version applied to each row. The version in force when MasterDB served a record governs; if a region has not yet received your change, the version on the receipt governs and the lag is MasterDB’s, not the AI company’s.
• Every other record you seal names the AI policy version in force when you sealed it (ai_policy_version in the seal; a pushing system reads it from GET /v1/seal-context).

Before you seal an AI policy, the version is 0: nothing beyond the AI-company Terms is affirmatively permitted, and no context is blocked.

What your AI policy can and cannot do

Your AI policy is binding on AI companies through the AI-company Terms they have signed, and the receipts show what each was served under which version. Nothing cryptographic can stop an AI that ignores it: MasterDB learns of a breach only from evidence, and the remedy is contractual. Blocking an AI company is the one control that takes effect without anyone’s cooperation — see What an AI company sees.