Repeatable Results
The checks are deterministic. The same content gets the same result every time.
Trust
Trust You Can Check
Compliance teams should not have to take our word for anything. Every check can be explained, and every published piece has a record.
Built Into the Product
What Your Compliance Team Can Verify Themselves
Each one is visible in the product and in the record, not only in this page.
Explainable Rule by Rule
Every result can be audited rule by rule, so anyone can see why a piece passed or what it needs.
Blocked Until Fixed
A piece that fails a critical rule does not go live until it is fixed.
Checked on the Rendered Page
Before a page goes live, it is checked again as it will appear, for example for accessibility.
Proof
Trace Any Page Back to Its Rules
For each published piece: the agent, the model, the rules that applied, each check's result and every approval.
Records are written as the work happens. Your compliance and security teams can trace any published page back to the rules that were valid when it went live.
Where your policy requires a person to approve, that approval is part of the same record.
Drafted the France product page with the 14 rules that apply to it.
Checked against Branding, Market regulation · FR, Factuality and Accessibility. One finding.
Rule MR-FR-02 rewrote one sentence to the approved wording.
Matched the endorsement to approved claim C-208 and its reference.
Checked again as rendered: accessibility and metadata pass.
Published to Drupal · fr-FR. Record sealed.
Narrated with an AI-generated voice. A product demonstration with a fictional brand and fictional people.
Transcript
The Record of One Published Page
This is Widebound, at Halvora Health, a fictional consumer health brand. Here is one of its pages, live in France. When an auditor asks how it got published, the answer is in its record. Which agent wrote it, and with which model: Halvora's content agent, connected through MCP. Which rules applied: the French rules for product pages. And what each check found, including a missing image description, caught on the rendered page and fixed. Who approved it, and when: Élise Moreau in Regulatory, because your policy asks for her approval in France. When an audit asks for it, the record exports as one package. The proof your audits ask for. Widebound.
Security and Data Protection
SOC 2 Type II Audited and GDPR Compliant
Widebound is built and run by Content Sync, on the same platform. The whole platform is SOC 2 Type II audited, penetration tested at least once a year and fully GDPR compliant. The Trust Center lists the subprocessors and the documents a security review asks for, and Content Sync's security page describes its practices. Its privacy policy applies to this site.
For security questionnaires, ask us when you book a demo. We answer them as part of the evaluation.
Questions
Questions From Compliance and Security Reviewers
Who runs Widebound?
Widebound is built and run by Content Sync. Content Sync's security page describes its security practices, and its privacy policy applies.
Is Widebound SOC 2 compliant?
Yes. Widebound runs on the Content Sync platform, which is SOC 2 Type II audited as a whole and fully GDPR compliant. The Trust Center has the details.
How do we get security documentation?
Ask for it when you book a demo, or write to info@widebound.ai. We answer security questionnaires and share documentation as part of your evaluation.
What can our compliance team check for itself?
Why each piece passed or failed, rule by rule, and the record of every published piece: the agent, the model, the rules that applied, each check's result and every approval.
Your Tools, Your Policies
Ask Us Anything About Security
Bring your security and compliance questions to the demo. We answer them with the product open.