Introduction
The AiCM platform reduces manual conversion effort, avoids operational distraction, and helps organisations make PDF content available to more people and AI systems. This page explains how the platform is governed before and after deployment. It covers secure tag deployment, privacy, security, availability, client responsibility, PDF conversion accuracy, accessibility, AI readability, and the supporting policy pages available for review. The AiCM platform is built by AAAnow, drawing on more than 25 years of automation experience across digital accessibility, quality, and website assurance.
The short version
The AiCM platform converts linked PDF content into inclusive HTML content, served alongside the original PDF. The original PDF remains available.
The organisation remains responsible for the content delivered, while the AiCM platform is responsible for operating, monitoring, and supporting the inclusive page delivery. The platform is designed to reduce cost, avoid operational distraction, and improve access to published information for people and AI systems.
What remains under your control
Your organisation remains in control of its website, documents, deployment decisions, and published content. The AiCM platform does not remove the original PDF, replace the website, or take editorial control. It supports access to the content already published by your organisation.
| Area | Governance position |
|---|---|
| Website control | Your organisation continues to own, manage, and control the website. |
| PDF control | Your original PDFs remain available on your website. |
| Content responsibility | Your organisation remains responsible for the accuracy of re-published content. |
| Secure tag approval | Your team approves the secure tag before it is added. |
| Deployment method | The secure tag can be added using a Tag Manager or direct deployment. |
| Recommended deployment | Direct deployment is supported and recommended using the published deployment instructions. |
| Review process | Digital, IT, procurement, legal, and security teams can review before deployment. |
How the secure tag works
The secure tag is the controlled way the AiCM platform is included in a client website.
Once placed on the website, the secure tag communicates with the AiCM platform. It does not require software to be installed on client devices or servers, and it does not require a connection to internal client networks.
The secure tag supports the visitor experience by enabling inclusive HTML versions of PDF content to be offered. The original PDF remains available for visitors who still want or need the document in that format.
For deployment guidance, use the published secure tag deployment instructions.
Availability, uptime and performance
The AiCM platform is monitored continuously for both uptime and performance.
If the AiCM platform is unavailable, the secure tag does not render, does not return an error, does not break page elements, and does not affect website functionality. This has been tested.
The website continues to operate independently. Visitors are not presented with an AiCM platform error, and the host website functionality remains unaffected.
Live availability and performance monitoring can be seen on the public system availability page.
Security and secure tag protection
Security is built into the way the secure tag is deployed, monitored, and protected. We take security seriously, and take all practical steps to protect you - no one is 100% hacker proof, our systems limit exposure, but we can never say we are completely secure.
The secure tag is protected by anti-hijacking, anti-sabotage, hash verification, domain segregation, and continuous monitoring. These protections are designed to protect the connection between the secure tag and the AiCM platform.
Real-world testing has covered 133,700 websites, including one deployment scale test across 3,560 sites simultaneously.
The secure tag also runs with continuous integrity checks. Hash verification is used to confirm that delivered content has not been altered before it reaches visitors.
The full architecture and hardening detail is available in the Tag Security page.
Incident response
The AiCM platform includes automated protections that activate immediately when a relevant incident is detected.
For clients taking out additional support provision, critical incidents are assigned to a named member of the AiCM platform team, assessed, and communicated within 2 hours of detection.
Security concerns can also be reported through the security contact route.
Privacy and data
The secure tag operation works with publicly available web page content.
It does not collect personal information (for the purposes of tracking retargeting or marketing of any kind), commercially sensitive business data, credentials, or authentication material as part of the secure tag operation. Anonymized information is used to operate the service, for example content consumption and / or supporting device specific service delivery, any such data used is not available outside the system.
The wider AiCM platform relationship may involve personal information where someone uses the website, dashboard, billing, support, analytics, sales, or marketing services. These interactions are handled under the Privacy Policy.
The Privacy Policy explains what personal information may be processed, why it may be processed, how rights can be exercised, and how information is protected.
Accessibility and inclusion
PDFs can create barriers for people.
They can be hard to read on smaller screens, difficult to navigate, awkward to enlarge, poor for search, or unreliable with assistive technology. The problem becomes harder to manage when organisations carry large volumes of PDF content across websites, departments, services, and public information pages.
The AiCM platform helps reduce these barriers by creating inclusive HTML versions of PDF content. This gives more people a better way to read, search, navigate, translate, and understand the information an organisation has already published.
The Accessibility page explains the platform's access commitment and the route for reporting accessibility problems.
AI inclusivity
AI systems increasingly read website content on behalf of people.
That includes search assistants, Agents, AI answer engines, summarisation tools, procurement research tools, workplace assistants, and customer support tools. These systems depend on readable, structured content to interpret what an organisation has published.
When important content is locked inside PDFs, especially across larger organisations, there is greater risk that information may be missed, misunderstood, or represented in a way the organisation does not control.
The AiCM platform helps by turning PDF content into inclusive HTML content that can be read more easily by people and AI systems. This improves access to published information and reduces the risk of avoidable misrepresentation.
For a wider explanation of why this matters, read the related white paper.
PDF conversion accuracy and client review
The AiCM platform works to best endeavours when converting PDF content into HTML.
Some PDFs, especially designer-led documents or poorly constructed files, may limit how closely the HTML can reproduce the original. This can include visual layout, reading order, embedded content, complex tables, scanned content, or design choices that were not created for accessible use.
Clients should review the original PDF, the converted HTML version, and any requested changes before relying on the published output.
Where requested, HTML can be updated or modified. The client remains responsible for approving the published result and confirming that the content is suitable for use.
Where language translation is utilised , translations are typically more than 90% accurate. They are based on generated document translation, rather than conversational interpretation.
Responsibility and accountability
Good governance depends on a clear split of responsibility.
The AiCM platform operates, monitors, and supports the service. The client remains responsible for the website, the original PDF, the accuracy of the content, internal approvals, and legal obligations.
| Area | Client responsibility | AiCM platform responsibility |
|---|---|---|
| Website ownership | Owns, manages, and controls the website. | Provides the platform accessed through the secure tag. |
| Original PDFs | Publishes and maintains the source documents. | Converts supported linked PDFs into inclusive HTML content. |
| Content accuracy | Confirms source content is accurate and approved. | Deserving of the published content made available online. |
| Secure tag approval | Approves secure tag deployment through internal processes. | Provides secure tag guidance and service support. |
| Service operation | Reports issues and manages internal decisions. | Monitors, maintains, and supports the platform. |
| Accessibility obligations | Remains responsible for organisational obligations. | Supports better access through inclusive HTML content. |
| Legal obligations | Takes professional advice where required. | Provides service information and supporting policy pages. |
| High-risk content | Reviews sensitive or complex content where needed. | Provides details as to content usage, priority of review. |
| HTML review | Reviews and approves converted HTML output. | Provides client interface to upload, reformat, securely edit converted content. |
What the AiCM platform does not do
This section explains the boundary clearly before deployment.
| AiCM platform does not | What this means |
|---|---|
| Remove the original PDF | The original PDF remains available on the website. |
| Rewrite the source PDF | The original document is not edited by the platform. |
| Replace the CMS | The existing website platform remains unchanged. |
| Take editorial control | The organisation remains responsible for published content. |
| Guarantee legal outcomes | Legal obligations remain with the organisation publishing the content. |
| Remove review responsibility | Clients should review PDFs, HTML versions, and requested changes. |
| Replace professional advice | Professional advice should be taken where legal obligations are concerned. |
| Remove human judgement | Sensitive, complex, or high-risk documents MUST have a review process |
Before approving deployment
This checklist is designed for teams reviewing the platform before deployment.
| Review question | Where to check |
|---|---|
| How is the secure tag added to the website? | Secure tag deployment instructions and Tag Security. |
| What happens if the platform is unavailable? | Availability section and system availability page. |
| How are uptime and performance monitored? | System availability page and Tag Security. |
| What data does the secure tag operation use? | Privacy section and Tag Security. |
| How are cookies and tracking explained? | Cookie Policy. |
| How is secure tag protection handled? | Security section and Tag Security. |
| How are security issues reported? | Security page and contact route. |
| Who remains responsible for published content? | Responsibility and accountability section. |
| Who checks PDF and HTML conversion accuracy? | PDF conversion accuracy and client review section. |
| Where are legal boundaries explained? | Terms & Conditions and Disclaimer. |
| Where is accessibility explained ? | Accessibility Statement. |
| Where can AI readability context be reviewed? | Who speaks for the organisation? white paper. |
Supporting policy pages
The Governance page provides an overview. The supporting pages provide the detailed legal, privacy, security, accessibility, and service information.
| Page | What it explains |
|---|---|
| Terms & Conditions | Commercial terms, service use, responsibilities, restrictions, payment, and contractual position. |
| Privacy Policy | Personal information, service data, account data, rights, lawful processing, and privacy handling. |
| Cookies | Cookie use, tracking, analytics, consent preferences, and browser control. |
| Acceptable Use Policy | Rules against misuse, abuse, scraping, reverse engineering, and service interference. |
| Disclaimer | Legal boundaries, reliance limits, service scope, and professional advice boundaries. |
| Accessibility | Accessibility commitment, alternative formats, WCAG alignment, and feedback route. |
| Security | Vulnerability reporting, security issue handling, and security contact route. |
| Tag Security | Secure tag architecture, hardening, monitoring, incident response, and isolation. |
Questions before deployment
For governance, deployment, security, privacy, accessibility, or content questions before deployment, contact zzzzzz_xxxxx@AAAnow.ai.
The AiCM platform is designed to help organisations make PDF content available to more people and AI systems, while keeping the original PDF, website control, and content responsibility with the client.
Full link listing
The links below should be included on the website page and used as the reference list for supporting pages.
| Link | What it is for |
|---|---|
| Secure tag deployment instructions https://aicm.aaanow.ai/resources/cms-tag-installation | Explains how the secure tag should be added using the recommended deployment approach. |
| System availability page https://aicm.aaanow.ai/system-status | Shows public monitoring of uptime and performance for the AiCM platform. |
| Who speaks for the organisation? https://aicm.aaanow.ai/whitepaper/who-speaks-for-the-organisation | Explains why AI systems reading public content creates governance and representation issues. |
| Terms & Conditions https://aicm.aaanow.ai/terms | Explains commercial terms, service use, contractual position, and responsibility boundaries. |
| Privacy Policy https://aicm.aaanow.ai/privacy | Explains personal data, service data, privacy rights, lawful processing, and data handling. |
| Cookies https://aicm.aaanow.ai/cookies | Explains cookies, tracking, analytics, consent preferences, and browser controls. |
| Acceptable Use Policy https://aicm.aaanow.ai/acceptable-use | Explains rules against misuse, abuse, scraping, reverse engineering, and service interference. |
| Disclaimer https://aicm.aaanow.ai/disclaimer | Explains reliance limits, legal boundaries, service scope, and professional advice boundaries. |
| Accessibility https://aicm.aaanow.ai/accessibility | Explains accessibility commitment, alternative formats, WCAG alignment, and feedback route. |
| Security https://aicm.aaanow.ai/security | Explains vulnerability reporting, security issue handling, and the security contact route. |
| Tag Security https://aicm.aaanow.ai/tag-security | Explains secure tag architecture, hardening, monitoring, incident response, and isolation. |