Trust and transparency
Last updated: 11 November 2026
Current notices
No incidents to report as at 11 November 2026.
Operator: Customer Experience Insight Pty Ltd (ABN 61 634 039 759) trading as WA AI Hub
Contact: support@memora.help
1. Our safety and security framework
We publish a Privacy Policy, Terms, a Children's Policy, a Refund Policy and this page.
The protections in place include:
- Passwords are stored as a hash. We never see your plain-text password.
- Email addresses are verified, and you can turn on two-factor sign-in for your account.
- Requests are rate limited, and sign-up is protected against automated bots.
- Transport security headers are set on every page.
- Photos and recordings in the Memory Vault are held in private storage and served only to signed-in people who are allowed to see that person's records.
- Text sent to AI features is checked first for abusive content and for attempts to manipulate the AI.
- AI-drafted session notes stay as drafts until a person reviews and approves them.
- AI reminiscence features do not run for a person unless AI-processing consent is recorded for them.
- Significant actions, such as AI requests and changes to stored memories, are recorded in an audit log.
- Records are deleted on a schedule under our retention rules.
This is a description of how the service is built. It is not a certification.
2. AI models and independent evaluation
AI is used for the carer guidance chat, drafting care and behaviour-support plans, reminiscence prompts and session notes, and voice input, where your recording is turned into text and summarised. The models are run by third-party AI model providers.
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. See OpenAI, Google and Anthropic.
Our own checks:
- Automated tests, including tests of content checks, consent rules, retention and payments.
- Type checks, code checks and a full build on every change.
These are run by us and are not independent.
3. Who can access your data
You and your organisation
Records belong to the account that created them. If you belong to a care institution, coordinators, clinicians and administrators in the same institution can also see the records of people in that institution's care. 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 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
See section 4.
4. Our subcontractors and their boundaries
| Function | What it handles | Where |
|---|---|---|
| Hosting | Runs the website and application | Australia (Sydney) |
| Media storage | Photos and recordings in the Memory Vault | Australia (Sydney) |
| Database | Accounts, profiles, notes, plans, conversations and transcripts | United States |
| AI processing | Text you enter into AI features, with related context from your account | United States |
| Speech-to-text | Voice input recordings | United States |
| Account and service emails | United States or other countries | |
| Payments | Card payments | United States or other countries |
| Rate limiting | IP address and request counts | United States or other countries |
| Bot protection | Sign-up checks | United States or other countries |
| Analytics | Anonymous page-view statistics | 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:
- The application is set to run in the hosting provider's Sydney region.
- Photos and Memory Vault audio files are not sent to AI services.
- We do not keep the audio of voice input. We keep the transcript.
- We do not use your information to train AI models and we do not authorise our AI providers to do so. We rely on the providers' published terms for this.
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
- People with an account would get an email at the address on the account.
- We hold no contact details for the people being cared for. We would tell the carer or family member whose account holds their records, and ask them to pass the notice on.
- 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: write to support@memora.help.
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.