Privacy Policy

What we collect

Nothing, by default. This site is static — plain pages with no server-side application behind them, no cookies, no analytics or tracking scripts, and no account system. Fonts and every other asset are served from this site itself, not a third party. Like any website, the hosting provider that serves these pages keeps standard, short-lived server logs (such as IP address and page requested) for security and operations; we do not use these to identify or profile visitors. If you email us at the addresses below, we hold that email in our mailbox like any other correspondence, and use it only to reply to you.

Synthetic data only

Every screen, name and "resident" you see on this site and in any linked interactive demo is synthetic — invented for illustration. No real person's information appears anywhere in the demonstration.

No third-party sharing

Because we don't collect data from visitors in the first place, there is nothing to share, sell or disclose to advertisers, data brokers or other third parties.

A synthetic showcase, not a data product

When the Well Engaged app first appears on the App Store, it will run entirely against a built-in demonstration facility: every resident, photo, activity record and family moment in it is synthetic. Using the app means signing in and syncing that demonstration activity to our server — that is how the app is built to work. When you sign in, or try to, the app sends those sign-in details to our server, and we keep short-lived security logs of sign-in attempts (the email entered and the network address it came from); those logs are purged on a schedule and used only to protect the service. Beyond that, no accounts are created by the public, no analytics or advertising trackers run, and none of the synthetic demonstration content is used for any purpose other than running the demonstration. Real facilities are enabled individually, under the pilot approach described below, and never through the public download alone.

Consent-based collection

We intend to collect information about a resident only after consent is obtained at onboarding — from the resident where they have capacity, or from their nominated substitute decision-maker (for example, an enduring attorney or guardian) where they do not. Consent will be able to be reviewed and withdrawn, with the practical effect of withdrawal explained up front.

What we intend to collect, and why

• Activity preferences and participation records — which activities a resident engages with and how, so lifestyle staff can personalise sessions and produce participation evidence for their own quality reporting.
• Basic profile details (name, room, interests) — supplied by facility staff, used to personalise sessions and give families appropriate visibility.
• Family-contributed material (photos, stories) — supplied voluntarily by family members who have been granted access by the facility or resident, used to build reminiscence activities.
• Staff account details — for facility coordinators and quality managers using the app, used for authentication and audit logging.
• Family member contact details (name, relationship, email, phone) — supplied by the facility or resident so we can send portal invitations and one-time sign-in links to the family members a resident's household has chosen to include.
• Device and security records — the identity of each enrolled facility iPad, and short-lived security logs of sign-in attempts (email entered, network address); used to keep the service secure and are purged on a schedule.

We may also use information in de-identified, aggregated form — never in a way that could reasonably identify a resident, family member or staff member — to operate and improve the service.

Storage and security

We intend to host all pilot data on servers located in Australia, with encryption in transit and at rest, role-based access controls, and append-only audit logging of access to individual resident records. Data will be retained only as long as needed for the purposes above and the facility's own record-keeping obligations, then deleted or de-identified on an agreed schedule.

Family portal access

Family members will only ever see what the resident (or their substitute decision-maker) has authorised. Access will be granted individually by the facility, with the ability to revoke it, recognising that not every family relationship is a safe one.

Access and correction

Residents, their substitute decision-makers, and facility staff acting on their behalf will be able to request access to, and correction of, information we hold about them, subject to verifying identity and any legal exceptions that apply.

Who is in control of the data

We intend the facility to remain the data controller for resident information, with Well Engaged acting as a processor under a data processing agreement — meaning the facility sets the rules for use of resident data, and we agree to follow them.