We operate it, you govern the content.
A managed deployment with agreed operations and support. Your team stays in charge of the official content and what investors see.
How it works
Your existing sources. Your approvals. A controlled AI experience.
AmayzTrust is designed to work alongside your website and approved publishing channels—not replace them. Your team decides which content can be discovered, published to learning, and used to support AI answers.
Existing official materialWebsite, guides, notices, media
Approved AmayzTrust knowledgeDated, sourced, separately approved
Cited answers and related learningWith a next step where it applies
Use what you already publish
Connect existing knowledge. Create new guidance when needed.
Bring together approved investor education articles, notices, warnings, guides and permitted media. Keep linking to the original publisher. When new information is needed, an authorized editor can prepare content for review within the agreed workflow.
Official website and noticesApproved pages, publications and warnings, linked to the originalLearn + AI-eligible once approved
PDF guidanceReadable guides and registers with their publication datesLearn + AI-eligible once approved
YouTube video details and authorized transcriptsPublic metadata can be listed; speech counts only with an approved transcriptLearn · transcript needs approval
Podcast feeds with approved summariesEpisode details from the feed; show notes or transcripts when approvedLearn · text needs approval
Fits the way your authority operates
Your Investor Centre, deployed to fit your governance requirements.
AmayzTrust is designed to be deployed as a branded experience alongside your existing website. Hosting, data location, identity, security review and support responsibilities are agreed with your authority.
One AmayzTrust application
Ask AILearnVerifyReportAlerts & Notices
Your branding · your approved sourcesYour environment, your controls.
Deployment in infrastructure and an account approved by your authority, subject to integration, provider and operational feasibility.
The deployment model is configurable subject to technical and security review. Jurisdiction-dependent data processing and approvals are agreed before any production use.
From approved sources to evidenced answers
The intelligence behind every useful answer.
Authorized public content is collected and organized with its source, date and status. Only material approved for AI answers is eligible for retrieval. When someone asks a question, AmayzTrust finds relevant passages, produces a clear explanation within the approved scope, and shows the evidence—then recommends related official learning.
Official public sourcesWebsite, guides and PDFs; warnings and notices; approved video and podcast text.
AMAYZTRUST
1Connect & prepareAuthorized public content with source, title and date, organized for review.
2Review & approvePublic listing and AI eligibility are separate decisions by your team.
3Knowledge indexRelevant passages with source and version IDs. Only approved text.
4Ask Our AIFor each question: retrieve approved passages, explain within that scope, validate citations.
An investor question enters at stage 4. It retrieves from the index; the AI never reads every record.
Cited answer, recommended learning, next stepEvidence with source and date, a separate recommended guide or video, and Verify or Report where relevant.
Public register → deterministic Verify. Licence status never passes through the generative model.
Confidential complaints → restricted officer workflow, outside the AI’s reach.
The experience is designed around approved public knowledge. The exact sources, integrations, governance and operating model are agreed for each authority.
Illustrative architecture; specific integrations and AI controls are validated in a scoped deployment.
Official media details can be recommended; only an approved transcript or show notes can support claims about what a video or episode says. The public demo shows this flow with prepared answers; live retrieval is validated per deployment.
Your official publishing channels
Connect the sources you can approve and maintain.
Begin with accessible official websites, readable guidance and publication feeds. Add media and social channels when permissions, usable text and platform interfaces allow.
| Group | Source | Prerequisites | Discoverable | AI evidence |
|---|---|---|---|---|
| Website, PDF and notices | Official pages, sitemap or feed, readable PDFs, notices | Accessible public content you have the right to index | Yes, linked to the original | After your team approves the text |
| YouTube and podcast | Channel or feed details; transcripts and show notes where authorized | Channel or feed access, and a permitted transcript or approved notes | Yes, by metadata | Only with an approved transcript or show notes |
| Social and other | LinkedIn, Instagram, Facebook and similar channels | Platform permissions and your authorization; availability varies by platform | Case by case | Only text you approve; not a guaranteed connector |
View detailed source requirements
| Source | Prerequisites | Discoverable | AI evidence |
|---|---|---|---|
| Official website pages | Public pages you may index; a sitemap or feed helps | Linked in Learn | Approved text only |
| PDF guidance and notices | Readable text PDFs; scanned documents need separately scoped OCR | Linked in Learn | Approved text only |
| YouTube | Public channel access through the official interface; transcript rights from you | Metadata and links | Approved transcript only |
| Podcast feed | Public feed; show notes or transcripts you approve | Episode details | Approved notes only |
| Depends on platform permissions and your authorization | Not assumed | Not assumed | |
| Instagram and Facebook | Depends on platform permissions and your authorization | Not assumed | Not assumed |
| Other official channels | Assessed individually | Case by case | Case by case |
Platform names are examples of channels an authority may publish on. They imply no partnership, endorsement or live connection.
How your team keeps control
From new publication to approved investor knowledge.
- 01
Discover / add
A source is connected or an editor adds an item.
Gate: Connect · Discover - 02
Review & organize
Metadata, topic and dates are checked.
Gate: Organize · Review - 03
Publish to Learn
Investors can browse it. This is not AI approval.
Gate: Publish to Learn - 04
Approve text for AI
A separate decision on the exact text.
Gate: Use in answers - 05
Monitor, update or withdraw
By design, changed items return to review and withdrawn items stop being offered; propagation is validated per deployment.
Gate: Change · Withdraw
Example recordAn official video, listed in Learn, with its transcript not yet approved for AI
RecordHow investor complaints are handledVideo · 1 Sep 2026
LearnListed in LearnInvestors can find it
AI answersNot approved for AICannot be cited for what it says
ReviewAwaiting transcript reviewReviewer and date recorded on approval
Withdrawal: the intended control removes material from public discovery and from AI eligibility. The full path through the index, caches and earlier answers is validated before production reliance, and audit trails are scoped per deployment.
Confidential complaints and the public register sit outside this lifecycle: complaints stay with officers, and licence status comes from approved register data.
From discovery to your Investor Centre
Begin with your existing website. Prove the value before expanding.
There is no need to replace your website or commit to every integration at once. We’ll review the content you already publish, agree a controlled starting point, and demonstrate the investor experience that fits your jurisdiction.
- STEP 1
Choose the most useful public content and questions.
- STEP 2
Review a tailored AI knowledge walkthrough or pilot.
- STEP 3
Agree approvals, deployment and next-stage scope.
Technical questions
Short answers for IT and procurement.
Does our CMS or website have to change?
No. Your CMS and publishing process stay in place. The usual starting point is a regulator-branded subdomain with a link in your existing navigation. Deployment choices
What can the AI access?
Only material your team has approved for AI answers. Public listing and AI eligibility are separate decisions, and operational or confidential records are outside the public assistant. Content approval
How are sources updated or withdrawn?
The intended behaviour is that changed items are flagged for review and withdrawn items stop being offered and stop being eligible for answers. How a withdrawal reaches the index, caches and earlier answers is verified per deployment before it is relied on. Content approval
Do video and podcast transcripts need rights?
Yes. A video can be recommended from its public details, but only an authorized transcript or approved show notes can support a factual answer about what it says. Channel support
Who is responsible for hosting and data?
Hosting, data location, identity, security review and support responsibilities are agreed with your authority for either deployment model. Deployment choices
Do AI model providers train on our content?
That depends on the provider and the contract. We confirm it in writing for each deployment rather than make a blanket promise.
How are the register and confidential cases handled?
Licence status comes from approved register data through a deterministic check, never from the model. Confidential complaints stay in a separate officer workflow. AI knowledge architecture
What do we need to start a pilot?
A focused topic, an agreed set of authorized public materials, a few investor questions and a reviewer for accuracy and citations. How to get started
Tailored to your publications
Walk through it with your own content.
We’ll map your sources, approvals and deployment model in one tailored session.