Trust and transparency
Last updated: 11 November 2026
Operator: Customer Experience Insight Pty Ltd (ABN 61 634 039 759), trading as WA AI Hub
Contact: support@wahub.ai
Current notices
No incidents to report as at 11 November 2026.
1. Our safety and security framework
We publish how SocialCraft™ handles information in our Privacy Centre, Terms of Service and Data deletion pages.
The protections in place include:
- Sign-in is handled by a dedicated identity provider. We do not store your password.
- Requests that change data are rate limited.
- A content security policy and transport security headers are set on every page.
- Access tokens for the social accounts you connect are encrypted before storage.
- Input is validated before it is processed.
- Text sent for caption writing is screened by a content filter.
- Workspace roles limit what each member of a workspace can do.
This is a description of how the service is built. It is not a certification.
2. AI models and independent evaluation
SocialCraft™ uses a third-party AI model provider to write and improve post ideas, captions and campaigns, to research a business from public web pages, and to describe images you upload. AI-generated drafts may contain mistakes. You are responsible for checking them before they are published.
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:
- Automated tests, type checks and lint on every change.
- Database migration tests and a build with end-to-end checks on every change.
These are run by us and are not independent.
3. Who can access your data
You and your organisation
Your content belongs to your account and its workspace. You can add people to your workspace, and each person's role (owner, admin, editor, approver or viewer) sets what they can do. This is enforced by the application. You can also draft posts without an account. Those drafts are not linked to a name or email address.
Us
One person, the owner of the business, can access production systems and data. There are no other staff or contractors with access.
There is no feature that lets us sign in as you.
Our tools
The owner uses AI-assisted operations tools to check that the service is running correctly. Those tools have read-only access to the database. Any change they suggest must be approved by the owner before it runs. Queries that could return personal information are restricted to AI models running on the owner's own computer.
Our subcontractors
Some of our subcontractors process your information to provide the service. Section 4 lists them by function.
4. Our subcontractors and their boundaries
| Function | What it handles | Where |
|---|---|---|
| Website hosting | All requests to the service while they are processed | Not stated |
| Database | Accounts, workspaces, drafts, personas, campaigns, scheduled posts, encrypted social account tokens | Not stated |
| Sign-in and account management | Name, email address and sign-in details | Not stated |
| AI processing | The business details, ideas, captions and images you ask it to work on | United States |
| Web search | Search queries about the business or topic you enter | Not stated |
| Media storage | Images you upload to the media library | Not stated |
| Payments | Billing details, entered on the processor's own checkout page | Not stated |
| Email delivery | Email address and the message sent | Not stated |
| Rate limiting and caching | Request counts and short-lived cached results | Not stated |
| Social networks you connect | The posts you publish and the account data you ask us to read | 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:
- Access tokens for connected social accounts are encrypted before storage.
- We publish to and read from a social network only for the features you use.
We do not currently pin AI processing to Australia, and we do not remove personal details from text before it is sent to the AI provider.
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: we will email the address on the account.
- People who draft posts without an account: we hold no contact details for them, so we cannot reach them 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 support@wahub.ai.
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.