About this block

Data Governance Table puts the security review on the page before the buyer opens a questionnaire. A ruled table lists six data policies, each row pairing the policy name with its exact commitment in mono and a plain line on what it means in practice. Answering in contract language rather than pitch language is the move, it lets a reviewer lift a row straight into the risk memo.

The headline, where your data goes in writing, frames the table as a document rather than a claim. Policies are one array of label, value, and detail, and a footnote closes with a link to the full DPA that ties every row to a clause.

When to use

Reach for this block on AI pages selling into security and legal reviewers, and on trust pages where the data policy needs a plain visual. It is the section a procurement reviewer screenshots for the vendor file.

A natural flow around it on a Marketing Pro page:

Before

• Human review explainer covering the workflow these policies govern

After

• Trust for the formal documents each row is drawn from
• FAQ catching the follow up questions a policy table raises

What you can display

One strong use is your actual data policies in the exact words of your DPA. Other tables:

• Retention policies. What is kept, for how long, and when it purges.
• Access policies. Who can read prompts and under what grant.
• Residency policies. Where inference runs and what never crosses the boundary.

Tip: keep the values in contract language, like the mono column does. A commitment a reviewer can quote beats a promise they have to paraphrase.