The EthosOne Trust Centre, and school trust centre software
Trust Centre: what we stand behind and what you publish
The Trust Portal is where you choose what the public sees; the Trust Centre is what they see.
EthosOne Trust Portal is the school trust centre module in EthosOne Core, governance, risk and compliance software built only for schools.
Families, regulators and partners read current, public-safe content; drafts, private evidence and internal registers stay private.
What we keep hearing
It is 10:15 and the principal is halfway through a tour with a prospective family. At the library door the father asks which AI tools the school uses and where the children's data goes. The principal says she will send the policy, and back in the office the current version is on the drive, or the website, or in the inbox of the person who last updated it. Somewhere in that morning, the answer still has to be a link. This is the room where the approved version is already public.
What we stand behind
Two things live on this page and neither is a footnote to the other. This half is EthosOne's own policy and technology governance, for anyone evaluating us. If you came to evaluate the product instead, skip to what your school can publish: the Trust Portal, and the public Trust Centre it produces.
Every policy below is a current, approved EthosOne document with its own URL and its own dates. They are the same documents a procurement reviewer would be sent, published rather than attached to an email.
Technology governance, in short
EthosOne is hosted on AWS in Sydney and Melbourne. AI runs onshore in Australia and school data is never used to train a model. The longer explanation, including the controls behind that sentence, is on security and hosting rather than repeated here, so there is one version of it to keep current.
We run the product on ourselves
Our own instance is at trust.ethosone.io, published from our own library using the module described below. A prospect can read what we publish about ourselves before deciding whether the thing we sell is worth publishing from.
What is not public
Sensitive reports and proprietary implementation detail are available under a controlled diligence request rather than posted. Ask through contact and say what you need it for. Gating everything would defeat the point of the page; gating nothing would be careless with the same records we tell schools to protect.
What your school can publish
The rest of this page is the module. It is what produced the instance linked above, and it is what a school licenses to produce its own.
Six views, one picture. Each one reads from the same live records.
01Branding
Logo, icon, banner, colours, fonts, public contact and a governance summary make the portal recognisably the school's. Edit, preview and save as a draft configuration.
02Featured
Curate the highest-value public items as featured cards, reorder them and test every call to action, so each opens a real public-safe destination.
03External Policies and Resources
A public resource library. Switch a policy or resource Public or Featured and the stakeholder finds only the intended controlled version.
04Data & Privacy
Answer due-diligence questions about data, security and AI practice with configured statements and source links, without leaking the controls themselves.
05FAQs
Bounded public answers, edited and ordered by the curator, so repeated stakeholder questions get a current, attributable reply.
06Policy
The approved policy list with independent Public and Featured switches. Each opens in a file viewer at its fixed source version.
The Trust Portal is the external expression of the accountability spine. Approved versions come from the policy library, and what the board approved is what families read, while the private registers, actions and evidence behind it stay inside EthosOne. When a parent asks whether the school is across it, the answer is a link.
Even we use it. Our own Trust Centre is published from our own library, using the module described above, so you can read what we say about ourselves before deciding whether the thing we sell is worth publishing from.
The helper knows which content is approved for public display and drafts from that alone: a governance summary from approved facts, plain-language policy summaries, sourced privacy responses, FAQs, a family-facing excursion overview and safe high-level risk narrative.
It can recommend which items to feature for a given audience and run accessibility and copy checks on the preview. The curator applies every draft, verifies redaction and decides what is public.
Sovereign frontier AI, hosted in Sydney and Melbourne.What it does not do
- It does not publish internal records merely because they exist.
- It does not expose drafts, private evidence or inaccessible source links.
- It does not let Preview differ from the published portal without disclosure.
- Stored in AustraliaAWS Sydney and Melbourne, one database per school
- AI stays in the country tooHosted in Sydney and Melbourne; never trained on your content
- Published, not describedOur policies in the Trust Centre · How we handle your data
“It meets all of the real frustrations of business directors in one place.”
Nick MillerDirector of Business, Blackfriars Priory SchoolThe seven we are asked every time.
Still weighing something up? Thirty minutes with us, on your own registers, answers the rest.
Get in contact01What is a school trust centre?
A public page where a school publishes its current approved policies, privacy and data practice, FAQs and selected assurance so families, regulators and partners can see how it meets its obligations. In EthosOne it is published from the governed library, on the school's own domain.
02Will it run on our own domain?
Yes. Configure and verify your domain in the Domain section and the Trust Centre resolves at the school's address.
03What happens when a policy is superseded after we publish it?
The curator decides. Each public policy is switched Public or Featured on its own, so when a policy is replaced, the curator switches the new version on and the old one off.
04Can parents see our risk register?
Only what you choose. The Risks section is off until enabled, and each profile or risk is marked public individually, so families see selected governance without sensitive detail.
05Do viewers need a login?
No. The public Trust Centre is read anonymously, and an external viewer who opens a private or deleted source sees no internal identifiers or metadata.
06Is the Trust Portal an extra module?
No. It is part of Core.
07Trust Centre: what we stand behind and what you publish, in full: what does it cover?
A governance or privacy lead selects approved policies, resources, privacy statements, FAQs, excursion guidance and chosen risks, previews the portal, and publishes to a branded public Trust Centre at the school's own address. It is built for business managers, principals and boards, and it is part of Core, included with every EthosOne licence.
More free templates and tools
When the parent asks at the library door,the approved version is one link away.
EthosOne’s own approved policies and technology governance in one place, and the same capability as a branded public Trust Centre a school can publish from its own approved library.