- Last updated
- 11 November 2026
- Operator
- Customer Experience Insight Pty Ltd ABN 61 634 039 759, trading as WA AI Hub
- Contact
- privacy@wahub.ai
Current notices
No incidents to report as at 11 November 2026.
1. Our safety and security framework
We publish how we handle personal information in our Privacy Statement, the rules for using the service in our Terms and Conditions, our Children's Policy, and every change made to a published AI Governance Hub update in our Corrections Log.
The protections in place include:
Sign-in is handled by a dedicated identity provider. We never see your password.
Card details are entered on the payment provider's own page. They do not reach our systems.
Administrative tools are limited to administrators who sign in through the identity provider.
Transport security and other browser security headers.
An automated content check on forms. A person reads every application.
Scheduled deletion under a retention schedule.
Automated checks on our code before it is released.
AI-drafted Hub updates are checked against their sources before they are published.
This is a description of how the service is built. It is not a certification.
2. AI models and independent evaluation
AI language models help find, draft and check public information for the AI Governance Hub, such as laws, policies and deadlines. They also help draft learning articles from our own project documents and code. They are not given members' personal information, and they do not decide admission, pricing, refunds or access to a service.
No independent third party has evaluated this product or the way it uses AI. There has been no outside audit, certification or penetration test. We will update this page if that changes.
The companies that build the models we use publish their own safety evaluations. Those are their evaluations of their models, not an evaluation of this product.
Our own checks:
A type check, a code-style check, automated tests and a production build run on every proposed change.
The automated tests cover the rules that decide whether an AI-drafted update may be published, and the content check on forms.
An AI-drafted update that fails its source checks is held for a person and is not published.
These are run by us and are not independent.
3. Who can access your data
You and your organisation
Each account holder sees their own account, preferences and subscription. This is enforced by the application.
Us
One person, the owner of the business, can access production systems and data. There are no other staff or contractors with access.
Our subcontractors
The companies that process information for us are listed by function in section 4.
4. Our subcontractors and their boundaries
| Function | What it handles | Where |
|---|---|---|
| Website hosting | Requests and logs, including IP address | Our code runs in Australia (Sydney). Content delivery and logs may be handled in other countries, including the United States |
| Database | Subscription records, preferences, team seat email addresses and form answers | Australia (Sydney) |
| Sign-in | Name, email address, password in protected form, sign-in details, application and payment status | United States and other countries |
| Payments | Billing and card details, email address, IP address | Australia and other countries, including the United States |
| Form notification | A reference number and the kind of form. No personal information | United States |
| AI processing | Public source material, and our own project documents and code. No members' personal information | Not stated |
| Website analytics | Page views, only with your consent | Not stated |
Every subcontractor is engaged on its standard published terms. We have not negotiated separate agreements with them and we do not audit them; we rely on the commitments they publish. A named list is available on request.
The limits we apply ourselves:
Our code and our database are pinned to an Australian region (Sydney).
No members' personal information is sent to AI providers, by design.
Card details never reach our systems.
Form answers are kept in our own database, not by the form notification provider.
Analytics is not loaded unless you agree to it.
5. How quickly we would tell you about an incident
If personal information we hold is lost, or accessed or disclosed without authorisation, we will begin assessing it within 72 hours of becoming aware of it. If the incident is likely to cause serious harm, we will notify the people affected and the Office of the Australian Information Commissioner as soon as practicable, and no later than 30 days after becoming aware. Where the GDPR applies, we will notify the relevant supervisory authority within 72 hours where that law requires it.
This service is run by one person. There is no round-the-clock on-call team, so an incident that happens overnight or while the owner is travelling may not be seen immediately.
6. How an incident would reach you
Account holders, subscribers, Sprint applicants and people who have contacted us gave us an email address. We would email them directly. These emails are sent by a person, not by an automated system.
Visitors without an account cannot be reached directly.
If we hold no contact details for you, look at the Current notices section at the top of this page. We will post a dated notice there.
To report a problem to us: email privacy@wahub.ai or use the contact form.
7. What we don't publish, and why
We do not publish the prompts, scoring and ranking methods, pricing logic, abuse-detection rules or model files behind this product, or the findings of our internal reviews. Publishing them would make the service easier to copy or to attack. Where we describe a method publicly, the description is linked above.