Privacy Policy

When you create an account, we collect:

• Email address — used for login, verification, and account-related communications
• Full name (optional display name) — used to personalise your experience
• Account role — your self-identified cohort (e.g., family carer, student, care worker, professional)
• Password — stored as a securely hashed value; we never see or store your password in plain text
• Account creation date and last login timestamp

If you register using a third-party provider (Google or Apple), we receive the email address and name associated with that account. We do not receive your password or access to your third-party account beyond these basic profile details.

You may choose to enter personal and health-related information into various tools within the App. This data is classified as sensitive information under the Privacy Act. Examples include:

• Care logs: mood, sleep quality, medication adherence, meals, water intake, activities, observed behaviours, free-text notes
• Medication records: medication names, dosages, schedules, notes
• Medical notes: clinical observations, appointment summaries, treatment notes
• BPSD (Behavioural and Psychological Symptoms of Dementia) logs: behaviour types, severity, triggers, interventions, outcomes, person identifiers (initials/ID — not full names)
• Daily summaries: mood summaries, medication status, meals, activities, appointments, notable behaviours, health notes
• Activity logs: activity type, duration, mood before/after, enjoyment ratings
• Journal entries: personal reflections, mood, titles, content
• Emergency transfer sheets: patient transfer information (we recommend using initials/IDs, not full names)
• Caregiver alerts: alert type, severity, related entity, action taken
• Shift records: facility name, company, shift times, role, clinical notes, hours worked
• Medical care team contacts: names, phone numbers, email addresses, relationships, types of healthcare providers
• Emergency contacts: names, relationships, phone numbers, email addresses
• Medical appointments: appointment details, dates, times, attending status
• Completed clinical template records (CareTemplate): resident/person name, completed-by, completed date, and filled form values — saved via the Clinical Templates Library and care-template tools
• Resource bookmarks: saved resource titles, URLs, and categories you bookmark for personal reference
• Daily reminders: medication and appointment reminders you create (date, time, label)

Important: Entering this data is entirely voluntary. The App functions without any health data input — these tools are optional features for your own care-planning use.

When you subscribe to a paid plan or make a donation:

• Subscription plan and status (e.g., Free, Student, Family Carer, Aged Care Staff, Clinical Professional, Organisation)
• Subscription start date, next billing date, and amount paid
• Stripe customer ID and subscription ID — used for subscription lifecycle management
• Budget and expense records you enter into the Budget Tracker and Expense Log tools
• Newsletter subscriber data — our weekly newsletter goes to two groups of people: those who subscribed to it, and those who have a Cassandra's Compass account. If you subscribed, we hold your email address, the name you choose to give (optional), the date and time you opted in, the wording you agreed to when you signed up, and where on the App you signed up (for example the home page). The date, the wording and the source are recorded by our server as our record of your consent, which is what the Spam Act 2003 (Cth) requires us to be able to show. Only our platform administrator can see this list — it is never shown to another subscriber or to any other user, and your email address is never written into our usage statistics. If you have an account, you are on the newsletter list unless you switch it off: the Weekly newsletter switch in Settings turns it off at once, for every future send, and you do not need to email us to use it. If you subscribed, the tick box on the sign-up screen is how you asked for it, and it is never ticked for you. Every newsletter carries a one-click unsubscribe link containing your own signed token: pressing it takes effect straight away and needs no account and no login. When you unsubscribe we also keep a suppression record — your email address and the date — so that you are not emailed again even if your subscriber record is later removed; it holds the email address only, and we keep it for as long as we need it to honour your request. To be removed, email support@cassandras-compass-dementia-care.org with the subject line "Unsubscribe" and the email address you subscribed with; if you have an account, deleting your account also removes your newsletter subscription. Please include the email address you subscribed with, and tell us if you would prefer a reply — we action removal requests within 30 days and send no further newsletters to that address once you are removed.

We never see or store your credit card number, CVV, or full card details. Payment processing is handled entirely by Stripe, our PCI-DSS compliant payment processor. Stripe tokenises your card information on their own secure infrastructure — we only receive a transaction confirmation and customer/subscription identifiers.

Complimentary access: the founder can grant free, complimentary access to an account, with no end date. To apply it, we keep one admin-only access record for that account: the email address the access was granted for, the access level, the date it was granted, and a short internal note. No payment is taken and nothing is charged. Platform administrators can read the record, and the account holder can see their own.

If you participate in community features, we store content you post:

• Community posts and replies — content, author display name, likes, board category
• Student discussion posts and replies — title, content, author name, category, likes
• Cass's Café posts — social/community content
• Content reports — if you report content, we store the reason, detail, content snippet, and your user ID
• User blocks — user IDs and display names of users you have blocked

Community content is visible to other logged-in users. Do not post personal health information, full names of care recipients, or other identifying details in public community areas.

• Subscription feedback — reasons for subscribing/unsubscribing, satisfaction ratings, feature usage, improvement suggestions, recommendation willingness
• General feedback — free-text comments you submit via the Feedback page
• Quiz responses — cohort, tier, quiz title, question text, selected/correct answers, scores (used to improve quiz quality; visible to platform administrators both individually and in aggregate)

If you submit an inter-service partnership request, we collect:

• Requesting service name, type, contact name, email, phone
• Target service type
• Partnership type, description, proposed frequency, start date, participant estimates
• Benefits for your service and expected benefits for the partner service — the two lists of benefits you add
• Risk assessment, duty of care plan, insurance considerations, regulatory compliance notes
• Status — every request is saved as a draft

Who can read it: a request can be read only by the account that created it and by the app’s administrator. It is never shown to another user, and the app enforces this in its data access rules rather than by policy alone.

The alert we send: when a request is created, the app’s administrator is emailed one short alert. That email carries the service type and the partnership type only, and a line asking the administrator to open the Founder Dashboard to read it. It never carries the request text, your contact name, your email address or your phone number.

How long we keep it: a request is kept until you delete it or you delete your account. You can delete a request yourself at any time from the page, and deleting your account removes your partnership requests (see Section 13).

Please do not enter the name or health details of any person receiving care.

When you use the App, we automatically collect certain technical information:

• Device type (e.g., iPhone, Android phone, desktop computer)
• Operating system and version
• App version and build number
• Browser type and version (for web users)
• Usage analytics — pages visited, features used, session duration (anonymised and aggregated via Google Analytics)
• Error and crash logs — technical diagnostic data used to fix bugs and improve stability
• IP address — used for security, fraud prevention, and server routing (not linked to your health data)
• Approximate location — derived from IP address at country/region level only; we do not collect GPS location
• Internal page-view analytics — the page path and title visited, the date and time, anonymous visitor and session identifiers, and your user ID where authenticated (stored in our own analytics records to understand how the App is used and improve content; not shared with third parties). These records contain no content you have entered. Administrator visits are not recorded at all — the check is made on our server from the signed-in role, so it cannot be bypassed from the page, and no record is written when an administrator browses the App

When you contact us (via email, feedback forms, or support requests), we collect:

• Your email address and name (as provided in your message)
• The content of your message or support request
• Correspondence history related to your enquiry

If you are issued a promotional access code or granted special access:

• Code, access level, recipient name, recipient email, reason, status, redemption date
• Special friend status (if granted by the founder)

If you join or administer an organisation (for example an aged-care provider, nursing service, or student cohort), we collect and store:

• Organisation details — name, contact name, contact email, organisation type, number of sites, status, and partner status
• Membership records — your name, email, role (Staff or Organisation Admin), join date, and status, linked to your organisation
• Invite codes — unique codes that link a staff member to their organisation’s licensed seats and content
• Aggregate team activity — counts only: whether a member has logged in, number of quiz/CPD attempts and correct answers, number of templates/forms created, feedback submitted, seats used, and days remaining. No personal care data, individual quiz answers, or template content is shared with organisation admins or the founder — only the counts.
• Staff knowledge assessment responses — if you complete the optional Knowledge Assessment invited by your organisation, we store your per-domain confidence ratings and quiz-style answers against your user ID for deduplication and data integrity. Your organisation admins can never see your individual answers — reports are generated server-side in aggregate form only, and no report is produced at all until at least three staff members have responded (anonymity floor). The platform administrator can access individual response records for administration and data-integrity purposes only.

Who can see what: Your organisation admin can see their own organisation’s member list and aggregate activity counts. The platform founder can see aggregate, organisation-level analytics across all organisations (counts only). Organisation admins and the founder cannot see your personal care data, journal, medications, or any user-scoped health information — that remains protected by Row-Level Security (see Section 3). Each organisation can only ever see and manage its own data, staff, codes, and analytics; one organisation can never view or access another organisation’s information.

Our Crisis Support page ("Not 000, But Need Help Now") helps you find the right 24/7 helpline in an urgent moment. Because of the sensitive nature of this page, we want to be unambiguous:

• We do not record which situation you select on the guided pathway. Your selection exists only on your device, on screen, and is never transmitted to us.
• We do not record which helpline you tap or call. Tapping a phone number hands off to your device's own dialer at the operating-system level, outside the App.
• Visiting the Crisis Support page is counted by the same anonymous page-view analytics as every other page (Section 2.7) — the page path only. We cannot and do not infer anything about your circumstances, and this data is never used for marketing or profiling.

If you participate in our referral program, we collect and store:

• Your referral code — a unique code linked to your account, plus your display name and email (kept on the code record for administering the program)
• Referral attributions — when someone signs up via your referral link, we record that the two accounts are linked, the signup date, and the referred person's display name
• Reward status — whether the referral converted, and whether your free-month reward or the new member's first-billing discount has been applied

Referral records are visible only to you (in aggregate form — referrers see "A new member", not names) and to the platform administrator for reward administration. Referral data is never shared with other users.

• Community contribution suggestions — if you suggest content (clinical trials, research opportunities, books, events, news) for review, we store the content type, title, description, link, optional date/location, and your display name (or email as a fallback), linked to your account. Suggestions are reviewed privately by the founder before publication; approved items are published with an anonymous "Suggested by our community" tag — your name is not shown publicly.
• Free job postings — if you submit a job listing via the "Post a Job — Free" form, we store the title, organisation, location, description, salary range (optional), and the application link or contact email you provide. Submissions remain hidden and pending until approved by the founder, then publish to the public Jobs Board. An application link is published in the open. A contact email is not: it is never shown on the board and never included in the listing information a visitor receives. The listing instead shows a Show how to apply button, and the address is returned to that one person only when they tap it. In our records the address can be read only by our administrator and by you as the person who submitted the listing — no other visitor and no other member can read it from the App. Each time the button is used we record a count only: no email address, no listing text and no IP address.

If you apply to list your service as a Sponsored Provider, we collect:

• Business name, service category, description, website, phone, location, chosen advertising package, and professional badge/credentials (if applicable)
• Application contact details — your contact name and email, so we can follow up about payment and your listing
• Billing tracking — for approved listings, the contact details and manual payment-tracking records (package tier, payment status, payment dates) are moved to a separate administrator-only billing record

Your contact and billing details are never shown publicly. When a listing is approved, its contact fields are blanked on the publicly visible listing and stored only in the admin-only billing record. Advertising package payments are arranged manually between us and the business (no card details pass through the App).

The Staff Debrief Toolkit (/staff-debrief) is a private space for aged care workers after a resident’s death, a hard shift or an incident. It is not a counselling service and it makes no clinical claims.

If you choose to save something in it, we store:

• Your reflection or check-in — the answers you chose to write (such as what happened, how you were feeling, what you needed, who you could talk to, or one small thing for yourself), any optional private note, and any options you tapped (such as how heavy the day felt, what made it hard, or what would help)
• The date you saved it

Who can see it:

• Only you. These entries are protected by Row-Level Security, exactly like your journal: they can be read, edited and deleted only by the account that created them
• Your employer cannot see them. If you belong to an organisation, that organisation’s administrators have no access to these entries, and no count of them appears in any organisation report or activity snapshot. This is enforced by the App’s data access rules, not by policy alone
• The platform founder has no way to read them through the App. There is no administrator read path to this data

Like all data in the App, entries are stored on our hosting provider’s systems.

How it is used: it is not used for anything. Your entries are never sent to an AI model, never included in analytics, never used for marketing, and never shared with anyone. The only thing recorded about this toolkit is a simple usage count of how often a tool is opened or an entry is created. It carries no note, no answer and nothing you wrote. It is linked to a random identifier for your device and, if you are signed in, to your account so that we can count how many people use the tool. If you delete your account, it is disconnected from you.

Deleting it: you can delete a single entry, or all of your entries, at any time from the history at the foot of the toolkit page, and the deletion is immediate. Deleting your account also removes all of your debrief entries (see Section 13).

Entering anything here is entirely voluntary. The toolkit’s guide and its support numbers are free to read without an account, and the tools work fully without any note being saved.

The CPD Record (/cpd-record) is a private place to keep your own record of continuing professional development: the learning activities you complete, how long they took, what you learned and what they mean for your practice. It is a recordkeeping tool. It is not a registration service, it does not assess whether an activity counts towards your registration, and it makes no claim about the status of any activity, course or provider.

If you choose to save an entry, we store:

• The entry itself — the date you completed the activity, its title, the source or provider, the type of activity, and your own estimate of the learning time in minutes
• What you wrote — your learning goal, what you learned or the outcome achieved, and your reflection on what it means for your practice

Who can see it:

• Only you. These entries are protected by Row-Level Security, exactly like your journal: they can be read, edited and deleted only by the account that created them
• Your employer cannot see them. If you belong to an organisation, that organisation’s administrators have no access to these entries, and no count of them appears in any organisation report or activity snapshot. This is enforced by the App’s data access rules, not by policy alone
• The platform founder has no way to read them through the App. There is no administrator read path to this data

Like all data in the App, entries are stored on our hosting provider’s systems.

How it is used: it is not used for anything. Your entries are never sent to an AI model, never included in analytics, never used for marketing, and never shared with anyone. The only thing recorded about this tool is a simple usage count of how often a tool is opened or an entry is created. It carries no title, no provider, no learning goal, no outcome, no reflection, no date and no duration. It is linked to a random identifier for your device and, if you are signed in, to your account so that we can count how many people use the tool. If you delete your account, it is disconnected from you.

Your exports: when you export your record to PDF or CSV, the file is built in your own browser and saved to your own device. It is not sent to us, and we keep no copy of it.

Deleting it: you can delete a single entry, or all of your entries, at any time from the record page, and the deletion is immediate. Deleting your account also removes all of your CPD entries (see Section 13).

Entering anything here is entirely voluntary. The record works fully without any reflection being written, and nothing you enter is ever assessed by us.

The Professional Quizzes (/professional-quizzes) are self-assessment modules for professional development. Completing one does not confer a qualification, a credit or any status, and a certificate issued by the App records participation only.

If you complete every question of a quiz, we store a record of that attempt:

• The attempt itself — the quiz name, when you started and finished it, how many questions there were, how many you answered correctly, and the estimated learning time shown for that quiz
• A certificate ID — a random 12-character code, printed on any certificate you download so it can be matched back to the stored attempt

What a Professional Quiz attempt does not store: which answers you chose. A Professional Quiz attempt records a score, never your responses, so nothing is saved in it that could reconstruct what you answered.

The Student Quiz and the Carer Quiz work differently. For each question you answer, we store a record that includes the question text (the first 200 characters), the option you chose, the correct option and whether you were right, together with the quiz name, your cohort and the quiz’s difficulty level (easy, medium or hard). These records are used to count quiz activity — how many people are using the quizzes and how they are going. The platform founder can read them. Your organisation cannot see your individual answers: an organisation report shows only a count of quiz activity by its members. You can delete these records by deleting your account.

Who can see it:

• Your Professional Quiz attempts: only you. These records are protected by Row-Level Security, exactly like your journal: they can be read and deleted only by the account that created them. Your employer cannot see them, and no count of them appears in any organisation report or activity snapshot. This is enforced by the App’s data access rules, not by policy alone. The platform founder has no way to read them through the App
• Your Student Quiz and Carer Quiz responses: you, and the platform founder. You can read and delete your own rows. The platform founder can read them, for administration and to count quiz activity, and they are counted in aggregate organisation and platform figures. Your organisation cannot see your individual answers — it sees only a count of quiz activity by its members

Like all data in the App, these records are stored on our hosting provider’s systems.

How it is used: it is not used for anything beyond the quiz activity counts described above. Your records are never sent to an AI model, never used for marketing, and never shared with anyone outside those counts.

Your certificates: when you download a certificate, the PDF is built in your own browser and saved to your own device. It is not sent to us, and we keep no copy of it. The name you type on the certificate is used only to print it and is not saved — only the attempt and its certificate ID are stored.

Deleting it: you can delete a Professional Quiz attempt at any time from the certificates list on the CPD Record page, and the deletion is immediate. Deleting an attempt removes the attempt record and the certificate ID printed on that attempt’s certificate. We keep no certificate file: the certificate is generated in your own browser and saved to your own device, so there is nothing left on our side once the attempt is deleted. Student Quiz and Carer Quiz responses have no delete control in the App yet; they are removed when you delete your account. Deleting your account also removes all of your quiz records and certificate IDs (see Section 13).

The Carer Wellbeing Check-In (/carer-check-in) is a weekly reflection for people caring for someone. It asks five short questions about how the week felt, and lets you add a private note. It is not a counselling service, it is not a diagnosis, and your answers are not monitored by anyone. The free guide and the support phone numbers on that page are available to everyone, including visitors who are not signed in.

If you save a check-in, we store the following:

• Your five answers — how heavy the week felt, whether you got time for yourself, how you slept, whether there is someone you can call on, and whether something about your own health is waiting
• The date — so the entry appears in your own history and in the eight-week strip
• Any note you choose to write — including the optional note about your own health

Who can see it:

• Only you. These entries are protected by Row-Level Security, exactly like your journal: they can be read and deleted only by the account that created them
• Your employer cannot see them. If you belong to an organisation, that organisation’s administrators have no access to these entries, and no count of them appears in any organisation report or activity snapshot. This is enforced by the App’s data access rules, not by policy alone
• The platform founder has no way to read them through the App. There is no administrator read path to this data

Like all data in the App, these entries are stored on our hosting provider’s systems.

How it is used: it is not used for anything. Your answers and your notes are never sent to an AI model, never included in analytics, never used for marketing, and never shared with anyone. The only thing recorded outside your own entry is that the tool was opened and that a check-in was saved — the count carries no answer and no note, and the endpoint that receives it rejects any field that would carry one.

Deleting it: you can delete a single check-in, or all of your check-ins, at any time from the history on the check-in page, and the deletion is immediate. Deleting your account also removes all of your check-in entries (see Section 13).

Saving a check-in is entirely voluntary. The guide and the support numbers work fully without a saved check-in, and nothing you enter is ever assessed by us.

The Respite Plan (/respite-plan) is a private planning tool for family carers. It helps you write down how the day usually runs, what helps, who to ring, and what should happen if you cannot care for a few days — and then print a handover sheet to give a stand-in carer. The free guide, its references and a blank printable handover template on that page are available to everyone, including visitors who are not signed in. Filling in a plan, having it saved to your account and printing a handover sheet from it are free for every signed-in account — no paid plan is needed for any part of this tool.

If you save a plan, we store the following:

• The plan itself — the first name or nickname you choose to enter, what a good day looks like, the daily routine, when medicines are given and where the official medication list is kept, changed behaviours and what helps, communication tips, safety and mobility, food and fluids, where emergency information is kept, and what should happen if you cannot care
• Any contacts you add — the names, numbers and optional notes you type yourself
• The date and time the plan was last saved

As you type, your plan is saved to your account automatically and the page shows the time it was last saved. You can also save at any moment with the Save now button. If a save fails, the page tells you. Start a new plan clears your plan after you confirm, and then you begin again with a blank form.

What we ask you not to enter: the page carries a standing notice asking you not to enter dates of birth, Medicare numbers, addresses or other ID numbers, and to use a first name or nickname rather than a full name. The medicines section deliberately asks for when medicines are given and where the official list is kept — not a list of medicines — so a printed sheet points at the current, authoritative list instead of repeating a copy that may be out of date.

Who can see it:

• Only you. Your plan is protected by Row-Level Security, exactly like your journal: it can be read, edited and deleted only by the account that created it
• Your employer cannot see it. If you belong to an organisation, that organisation’s administrators have no access to your plan, and no count of it appears in any organisation report or activity snapshot. This is enforced by the App’s data access rules, not by policy alone
• The platform founder has no way to read it through the App. There is no administrator read path to this data

Like all data in the App, your plan is stored on our hosting provider’s systems.

How it is used: it is not used for anything. Your plan is never sent to an AI model, never included in analytics, never used for marketing, and never shared with anyone. The only things recorded about this page are that it was opened and that a handover sheet was generated — neither carries your name, any section of your plan, a contact, or which sections you chose to print, and the endpoint that receives them rejects any field that would carry one.

Your handover sheet: the printable handover sheet is built in your own browser and saved to your own device. It is not sent to us, and we keep no copy of it. You choose which sections print — none are selected to begin with — and every sheet carries the line “This sheet was written by the person’s carer. It is not medical advice and must be checked with the person’s doctor and care team.”

Deleting it: you can delete your plan at any time from the plan page, and the deletion is immediate. Deleting your account also removes your respite plan (see Section 13).

Saving a plan is entirely voluntary. The guide, its references and the blank handover template work fully without one.

So we can understand which parts of the App help people, we keep two kinds of usage record. Neither ever contains anything you have written.

• Upgrade usage records — the event (for example that an upgrade prompt was shown or tapped, that a plan was chosen, or that a purchase completed), the plan the event relates to, the channel (web, Apple or Google) and billing period where one applies, and the date and time
• Sign-up usage records — the event (that an account was started or completed), the method used (email, Google or Apple), and the date and time
• A short machine label for where the event happened — a fixed identifier such as a feature name, never anything you typed
• Your account ID where you were signed in at the time. It is taken from your session on our server, never from the page, so a record can never be attributed to somebody else
• Anonymous visitor and session identifiers — the same ones described in Sub-section 2.7, so sign-ups and upgrades can be read against overall traffic without identifying anyone

Why: only to see how people find and move through the App, and where we can make it clearer. These records are never used to read, review or reconstruct anything you have entered.

Who can see it: platform administrators only, as aggregate reporting.

No health content is ever included. No care record, journal entry, medication, note, quiz answer or any other content you have written can appear in these records: the fields are a closed list, and the endpoint that receives them rejects any field outside it.

Cassandra’s Compass offers free access to verified University of Tasmania students and staff. To administer that offer we store a grant record:

• Your account ID — set on our server from your signed-in session. This is the only thing the access check matches on
• The verified UTAS email address the grant was issued for, kept for reference and audit
• Domain category — whether the address was a student, staff or other university address
• Granted date, and how the grant came to exist — an automatic grant at sign-in, the one-off migration, or issued by hand
• Status, and where revoked, the revoking administrator, their name and the revocation date

Why: to give University of Tasmania students and staff the access they are entitled to, and to keep an audit trail of who granted or revoked it.

Who can see it: platform administrators only, on an admin-only access panel.

If your UTAS email stops working: access is decided by your account ID and the grant’s status, never by the email address — so your access continues after the address stops working, unless the grant has been revoked. A revoked grant stays revoked and is never re-issued automatically.

The free plan includes three template fills or prints a calendar month. To apply that allowance we keep one counter per account per month:

• Your account ID — set on our server from your signed-in session
• The calendar month the count covers, in Australian care time
• The number of templates used that month, and the date and time of the most recent use

Never stored: which template you used, and anything you typed into it. The counter holds a number and nothing else. Student plans and above are not counted at all.

Why: only to apply the free monthly allowance, and to reset it on the first day of each month.

Who can see it: platform administrators only. It is never shown to your organisation or to any other user.

If you belong to an organisation and a learning pathway is assigned to you, we keep a record of your completion of it. This sub-section sets out exactly what that record holds, who can see it, and what it never contains.

What we record. For each step you complete on a pathway:

• Your account ID — set on our server from your signed-in session, never from your device
• The pathway and the step you completed
• The date and time you completed it
• The organisation you belonged to at that moment, recorded as a snapshot so your organisation’s past figures are not rewritten if you later change organisations
• The authored estimated learning time for that step, in minutes — an estimate written by Cassandra’s Compass, not a measured time and not a formal credit

Where an organisation assigns a pathway to you, we also record the pathway, your account ID, the assigning organisation, who assigned it, the assigned date, any due date, the status, and any short note the assigning admin wrote. We also record your name and your email address as the organisation entered them, so the organisation can tell who an assignment is for. If you delete your account, your name, your email and the note are cleared, your account ID is replaced, and the record is no longer linked to you — the pathway, the status, the dates and the organisation are kept so the organisation’s record of what it assigned stays correct. A due date is optional, and an assignment with no due date is never reported as overdue.

What your organisation admin can see. For people in their own organisation only, an organisation admin can see:

• Your name and your role label within the organisation
• The pathway assigned to you
• How many steps you have completed out of the total for that pathway
• The status — completed, in progress, not started, or overdue
• The assigned date and the due date
• Your completion date and your last activity date

They can also export exactly those columns as a spreadsheet, and the export carries a written notice of the same limits described here.

What your organisation admin cannot see. They cannot see, and the App does not show them:

• Any quiz score or quiz answer
• Any note you have written
• Any debrief entry from the Staff Debrief Toolkit
• Any Carer Check-In answer or note
• Any CPD record or reflection
• Any Respite Plan, or anything else private to you
• Anything from a care record

None of that is recorded against a pathway, so there is nothing of that kind to show. Your organisation admin has no direct access to your learning records in the database either: their view is produced by our server, after checking who they are, and only ever as the columns listed above.

You are told on screen. When a pathway is assigned to you, the App shows you a notice on the pathway itself, naming who assigned it, the due date if one was set, and stating plainly what your organisation can and cannot see. You are never assigned a pathway without being told.

The weekly digest. An organisation can opt in to a short weekly email summarising its own training activity. That email contains counts and dates only — how many members have started, how many pathways are still to be finished, what is past its due date, and how many minutes of estimated learning have been recorded. It contains no name, no individual row, and none of the private material listed above. It is off by default, and stops the moment the organisation turns it off.

What the platform founder sees. The founder sees aggregate counts only, per organisation: how many staff were invited, how many were active in the last 30 days, how many pathways were assigned, a completion rate, and the last activity date. The founder never sees an individual name, an email address, or a per-person row. Any breakdown for a group of fewer than five people is withheld entirely and shown as “fewer than 5”, because a rate over four people can identify someone by elimination.

Retention and deletion. Learning records are kept for as long as your account exists, so your organisation can see which pathways its staff have completed. Deleting your account removes your pathway progress and your assignments with it. If your account is deleted, your organisation’s past figures are not rewritten — the completion counts already reported for the period you were a member remain, but they are no longer linked to you as an individual. You can ask us to delete a specific learning record at any time (see Section 12.3).

See also: Section 3 sets out what we cannot see, and Section 4 lists the pages where you may input sensitive data.

On our Sponsored Providers directory a signed-in account may rate a provider and leave a short comment. That rating and comment are a review.

What a review holds. The rating you choose (Good, Meh or Bad), an optional comment of up to 500 characters, and the name shown with it. One review per account per provider is kept: rating the same provider again updates your existing review rather than adding a second one. You cannot review a listing you created yourself.

The name shown is your first name and last initial only — for example “Anna K.”. We record it that way when the review is saved. A review written before this rule was introduced may still hold the full name in storage; those older reviews display only the first name and last initial as well, so the full name is never shown publicly.

Who can see a review. Anyone. The comment and the name shown with it appear publicly on the provider’s listing, and the rating is counted in the summary shown beside it. Your account is not linked to the review publicly, and we do not publish your email address.

Hiding a review. We can hide a review from public display — for example a review that is abusive, off-topic or otherwise not fit to show. A hidden review disappears from the listing and from every statistic we show, but the record is kept so that it can be restored. A hidden review can be read only by us and by the person who wrote it; it is never sent to any other reader. You can edit or delete your own review at any time.

Reporting a listing. A signed-in account can report a listing to us. A report tells us the listing’s business name and that a reader reported it, together with the short reason chosen. We do not ask for, and do not collect, the reporter’s name, email address or account — a report carries no details about the person who sent it. We apply a short cooldown between reports from the same person, and the report is held only as a small count that cannot be turned back into a person.

Deleting your account deletes your reviews. Your reviews are removed with your account, as described in Section 13.

A sponsored listing may show a professional badge and a credentials line — for example “Registered Nurse” or “GP, FRACGP”. The provider supplies that wording, so until we have checked it ourselves the listing shows it prefixed “Self-reported:”.

What we store when we check. When we check a claimed professional title against the relevant public register — the Australian Health Practitioner Regulation Agency (Ahpra) or the Nursing and Midwifery Board of Australia — we record that the check was made and the date it was made. Once that is recorded the listing shows the badge and the credentials line normally, with the date of the check. The check can be recorded only by our administrator.

Who approved the listing. When we approve a listing we also record the name of the person who completed the approval checklist and the date they completed it. That record is internal: it is what lets us show that a check was actually made, and it cannot be written by anyone other than our administrator.

Nothing about a reader is involved. This sub-section concerns advertisers and our own internal records. It does not describe any information about a reader, a carer, or a person receiving care.

Cassandra’s Compass publishes a public Hall of Fame at /hall-of-fame. It is a page anyone can read, signed in or not, and it sits behind no account gate and no subscription gate.

What it publishes. For each honouree it publishes their name, their photograph where we hold one, a biography and a subtitle, the role and award they are recognised under, and any external links to their own work or an official profile.

Where it comes from. Each entry is written from public sources and, where a person’s approval has been recorded, it is published with that approval. Photos are shown with a credit naming their source. Where we hold the person’s permission we record it. Where we use a photo from an official public page on our own decision, we record that too, and we remove it on request. Where a credit line is missing, the person’s initials are shown instead of the photograph. The credit names the source of the photograph or the biography.

How to ask for a correction or removal. A person named in the Hall of Fame, or their family, can ask us to correct or remove an entry at any time. Email admin@cassandras-compass-dementia-care.org with the subject line “Hall of Fame correction or removal request”, or use the “Request a correction or removal” link on the page itself. We will respond within 30 days.

Anyone can nominate someone for a Cassandra’s Compass Award using the form on the Awards page. The awards are open to people 18 and over, and the form cannot be sent without that confirmation.

What we collect about the nominee. The nominee’s name, their email address if the nominator has it, the nominator’s relationship to them, their organisation and role if the nominator knows where they work, and the reason the nominator gives for the nomination. About the nominator we collect their name and email address only if they choose to give them — a nomination can be made anonymously. The form asks the nominator not to include health or diagnosis details about the nominee.

Why we collect it. Only to ask the nominee for their consent and to run the awards. Nothing about a nominee is published without their consent, and where we cannot reach them we publish a fully de-identified tribute — no name, no location and no photograph — or nothing at all.

The five choices. A nominee chooses one of: full recognition (full name, suburb, photo and story); first name and suburb; first name only, with no location and no photo; fully anonymised (for example “a dedicated carer from regional NSW”); or not featured publicly. Every choice is honoured exactly as it was made.

The consent link. The nominee is sent a private link containing a unique token. The link lasts 30 days from the day it was issued; after that it stops working and we can issue a new one on request, which replaces the old link immediately. The form records who completed it — the nominee themselves, the nominee with support from someone they trust, or a guardian or other person with legal authority who must name themselves and the authority they hold.

Who can read a nomination. Our platform administrator only, and — where a nominator holds an account — that same account can read the nomination it submitted. A nomination is never shown to any other user and never appears on any public page in its submitted form.

How long we keep it. A nomination that goes nowhere is kept for no longer than 12 months, and one the nominee declined is kept for no longer than 90 days. Pending: this cleanup is built but has not been switched on yet; until it is, the retention described here does not yet take effect and no nomination is removed automatically.

How to withdraw or correct a choice. A nominee can withdraw their consent or change their choice at any time. Email admin@cassandras-compass-dementia-care.org with the subject line “Withdraw my consent” and the name you were nominated under, and we will act within 14 days. Withdrawing consent also takes the tribute down; nothing is deleted, so the record of what was given and then withdrawn stays intact.

Cass’s Café is the social space on the App where people touched by dementia and aged care can find each other. It is reached from the Cass’s Café page. The café is for people 18 and over.

What a café post holds. The text you write, your display name, your account ID (so the post can be attributed to you and so you can delete it yourself), the category you chose (Connect, Volunteer Offer, Help Needed, or Event), the date, and the number of likes. An event also holds the event title, type, date, time, location or link, and a description. The café asks you not to post your home address, financial details, identifying information, or health details about yourself or anyone you care for.

Who can read a café post. A café post can be read by anyone who can reach the data, including someone who is not signed in. Community posts and café posts are not restricted to signed-in readers at the data layer, so please treat anything you post there as public. This is why the café asks you to keep posts general and to suburb level. Only an administrator can delete someone else’s post.

Reporting a post or an event. Any reader can report a café post or event. A report records the content type, the content ID, up to 200 characters of the post for context, the display name and account ID of the author, the reason you chose, and anything you type in the details box. Reports are readable by our platform administrator only.

A safety concern. If you choose the reason “Safety concern: someone may be at risk”, the administrator is alerted without the post text and without any name — the alert says only that a reader raised a safety concern. What you typed in the details box stays in the report record, where only the administrator reads it.

Blocking a member. You can block another member from the café board. A block stores that member’s account ID and display name against your own account, and their posts are then hidden from you. You can undo it from your profile.

Deleting your own post. You can delete a post you wrote at any time, straight from the board, after confirming. Deleting it removes it for everyone. Your café posts are also deleted with your account.

The café opt-in is a setting on your device. Choosing to join the café, and the member type and suburb you give, are saved in your own browser on that device only. It is not an account setting, it is not sent to us, and it does not make your posts private.

Volunteer visits are not checked by us. People arranging help through the café are not screened, vetted, or checked by Cassandra’s Compass. Anyone visiting an older person at home should hold the checks the Australian Government expects of aged care volunteers, and we encourage you to meet the person’s family or support person first, and never to take payment, keys or bank details.

The Rewards page stores nothing on our systems. Badges and points are worked out on your own device, in your browser, from your own records — your care logs, medical notes and journal entries. They are not sent to us and are not saved anywhere by us.

Your choice to turn rewards on or off is saved only in your browser on that device. It is not an account setting and it does not change what we hold about you. Turning rewards on or off changes nothing about your logs, notes or journal — those stay private to you. The only figures we see are anonymous platform-wide totals that cannot be traced back to you.

• Care Tracker (/care-tracker) — mood, sleep, medications, meals, water intake, activities, behaviours, notes
• Medications (/medications) — medication names, dosages, schedules, notes
• Medical Notes (/medical-notes) — clinical observations, treatment notes
• Medical Appointments (/medical-appointments) — appointment details, dates, attending status
• BPSD Behaviour Tracker (/bpsd-tracker) — behaviour types, severity, triggers, interventions, outcomes
• Daily Summaries (/daily-summaries) — mood, medication status, meals, behaviours, health notes
• Activity Tracker (/activity-tracker) — activity types, duration, mood, enjoyment
• Caregiver Alerts (/caregiver-alerts) — alert types, severity, health metrics, actions taken
• Emergency Transfer Sheet (/emergency-transfer) — patient transfer information
• Care Data & Reporting (/care-data) — aggregated care data visualisations
• Care Progress (/care-progress) — care and activity progress tracking

• My Journal (/my-journal) — personal journal entries, mood, reflections
• Memory & Visit Companion (/memory-companion) — visit planning data, memory prompts
• Resource Bookmarks (/resource-bookmarks) — saved resource titles, URLs, categories
• My Template Hub (/my-template-hub) — personal template entries
• Staff Debrief Toolkit (/staff-debrief) — private reflections after a resident’s death, and a private note and check-in after a hard shift
• CPD Record (/cpd-record) — the learning activities you log, your learning goal, what you learned and your reflections on your practice
• Carer Wellbeing Check-In (/carer-check-in) — your five weekly answers and any private note you write about your week or your own health
• Respite Plan & Handover Sheet (/respite-plan) — the person’s first name or nickname, what a good day looks like, the daily routine, when medicines are given and where the official list is kept, changed behaviours, communication tips, safety and mobility, food and fluids, your contacts, where emergency information is kept, and what should happen if you cannot care

• Contacts (/contacts) — emergency contact names, relationships, phone, email
• Medical Care Team (/medical-care-team) — healthcare provider names, contacts, specialities

• Budget Tracker (/budget-tracker) — financial budget records
• Expense & Travel Log (/expense-log) — expense entries, travel costs
• Shift Calendar (/shift-calendar) — facility, company, shift times, role, notes
• Agency Shift Tracker (/agency-shift-tracker) — agency shift records
• Shift Report & Handover (/shift-report) — clinical handover notes

• Community (/community) — public posts and replies (visible to other users)
• Student Hub (/student-hub) — student discussion posts and replies (visible to other students)
• Cass's Café (/cass-cafe) — social community posts and events (readable by anyone who can reach the data — see Sub-section 2.28)

⚠ Content posted on these pages can be read by other people — and for community and café posts that includes someone who is not signed in. Do not post personal health information or identifying details about care recipients.

• Feedback (/feedback) — free-text feedback and comments
• Need Support / Rate Us (/need-support) — support requests and ratings
• Inter-Service Partnerships (/inter-service-partnerships) — organisation details, contact information, partnership proposals
• Professional Quizzes (/professional-quizzes) — quiz responses and scores
• Quizzes Hub (/quizzes) — quiz responses by cohort and tier

• Base44 — our primary cloud infrastructure and database hosting provider. Base44 processes personal data securely on our behalf, in accordance with our instructions and applicable data protection laws. Base44 is contractually prohibited from using your personal data for any purpose other than providing the hosting and processing services required for this App. Row-Level Security ensures even Base44 infrastructure administrators cannot read your user-scoped care data.

• Stripe — processes all subscription payments, donations, and Featured Job Listing purchases. Stripe is PCI-DSS Level 1 certified. We never receive or store your full card number, CVV, or card verification data. Stripe provides us with a transaction confirmation and customer/subscription identifiers only. See Stripe's Privacy Policy.
• Sponsored Provider advertising packages — invoiced and paid manually (for example by bank transfer). No card or payment details pass through the App for these packages.

• Google — if you sign in with Google, we receive your email address and name. See Google's Privacy Policy.
• Apple — if you sign in with Apple, we receive your email address (or relay email) and name. See Apple's Privacy Policy.

• Google Analytics (GA4) — collects anonymised, aggregated usage data (pages visited, session duration, device type). IP addresses are anonymised. We use this data to understand how the App is used and to improve features. No personally identifiable health data is sent to Google Analytics. See Google's Privacy Policy.

• Apple App Store (StoreKit 2) — processes iOS subscription purchases. Apple handles all payment details. We receive a transaction receipt for verification only.
• Google Play Billing — processes Android subscription purchases. Google handles all payment details. We receive a purchase token for verification only.

• Google Calendar — if you use the Calendar Sync feature, we connect to your Google Calendar via an authorised Google Calendar connector to display and sync your events. Google processes your calendar data according to its own privacy policy. See Google's Privacy Policy.
• Adzuna (job-board data source) — our Jobs Board is populated in part by job listings sourced from Adzuna's API. Adzuna provides public job-posting data (title, employer, location, application URL); no personal data is sent to Adzuna. See Adzuna's Privacy Policy.

• Clinical Assistant (AI/LLM feature): The in-app Clinical Assistant uses an artificial-intelligence large language model (LLM) to respond to the clinical or care questions you type. When you send a question, your entered text is transmitted to the platform's LLM provider to generate a response, along with relevant context from your saved Resource Bookmarks. The LLM provider processes this input according to its own privacy and data-handling terms as a sub-processor acting on our instructions.
• AI-generated content is not professional advice: Responses from the Clinical Assistant are generated by AI and are provided for educational and care-planning purposes only. They do not constitute professional medical, clinical, nursing, or legal advice, and they are not a substitute for the clinical judgement of a qualified health professional. Always verify AI-generated information and consult a registered health professional before making decisions about care, medication, or treatment. In an emergency, call 000 (Australia) immediately.
• No health-data training: We do not use your clinical questions or any personal health data you enter to train external AI models. See also Section 16 — Medical Disclaimer.

We may disclose personal information where required by law, court order, or lawful request from a government or law enforcement agency, or where we believe it is necessary to protect the rights, property, or safety of our users or others. Any such disclosure will be limited to what is legally required.

We do not share your personal or health data with data brokers, advertising networks, or third-party marketers. No advertiser receives access to your care data, journal entries, or health information.

• Encryption in transit: All data transmitted between your device and our servers is protected using TLS (Transport Layer Security) 1.2 or higher with strong cipher suites. This means your data is encrypted end-to-end as it travels across the internet.
• Encryption at rest: All data stored in our databases is encrypted at rest using industry-standard AES-256 encryption. This protects your data even if physical storage media were compromised.
• Password hashing: User passwords are never stored in plain text. They are hashed using strong, salted one-way hashing algorithms that cannot be reversed.

This is our most important privacy protection for your health and care data. Every record you create in the App's personal tools (care logs, journals, medications, BPSD logs, shift records, etc.) is protected by database-enforced Row-Level Security. This means:

• Each data record is tagged with the ID of the user who created it
• The database itself enforces that only the creator can read, modify, or delete their records
• Even our own administrators and infrastructure providers cannot bypass this to read your personal care data
• This is a technical guarantee, not just a policy promise — the database refuses to serve your data to anyone but you

• Authentication: All access to the App requires valid authentication credentials (email/password or OAuth provider)
• Session management: Login sessions use secure, time-limited tokens that expire automatically
• Role-based access: Administrative functions (user management, subscription management, content moderation) are restricted to authorised admin accounts
• Principle of least privilege: Our team members have access only to the systems and data necessary for their specific role

• Secure cloud infrastructure: Our hosting provider (Base44) maintains ISO 27001-aligned security controls, regular penetration testing, and 24/7 infrastructure monitoring
• Firewalls and network security: All servers are protected by enterprise-grade firewalls and network access controls
• Regular security updates: Our infrastructure, dependencies, and application code are regularly updated to address known vulnerabilities
• Backup and disaster recovery: Data is backed up regularly with encrypted backups stored in secure, geographically distributed locations

• Security incident response plan: We maintain a documented incident response plan that is reviewed annually
• Staff training: Our team is trained on privacy obligations, security best practices, and breach response procedures
• Audit logging: Critical system actions are logged for security monitoring and forensic investigation
• Regular security reviews: We conduct periodic reviews of our security posture, including code reviews, dependency audits, and access control audits

While no system can guarantee 100% security, we have implemented multiple, layered protections designed to keep your data safe. The combination of encryption, Row-Level Security, access controls, and secure infrastructure means that your personal care data is among the best-protected data in the industry. If you have any questions or concerns about our security practices, please contact us at admin@cassandras-compass-dementia-care.org.

You have the right to request access to the personal information we hold about you. To access your data, you can:

• View your care data directly in the App at any time — it is always available to you
• Export your data by contacting us at admin@cassandras-compass-dementia-care.org
• Request a written summary of the personal information we hold

We will respond to access requests within 30 days. We may ask you to verify your identity before providing access.

You have the right to request correction of any inaccurate, incomplete, or outdated personal information. You can:

• Edit your data directly within the App's tools at any time
• Update your profile information (name, email) via the User Profile screen
• Request correction by contacting us at admin@cassandras-compass-dementia-care.org

We will take reasonable steps to correct information within 30 days of receiving your request.

If we decide not to correct the information, we will tell you why in writing and how to complain about that decision — first to us, and then to the Office of the Australian Information Commissioner (OAIC). You may also ask us to attach a statement to the record setting out the correction you sought, and we will take reasonable steps to associate it with the information. There is no charge for making a correction request or for asking us to attach a statement.

You have the right to request deletion of your personal information. See Section 13 for full details on account closure and data deletion.

Where we process your data based on your consent (particularly for sensitive health information), you have the right to withdraw that consent at any time. Withdrawing consent will not affect the lawfulness of processing before withdrawal. To withdraw consent, you can:

• Delete the specific data entries you no longer wish to share
• Delete your account entirely (Section 13)
• Contact us at admin@cassandras-compass-dementia-care.org to request withdrawal of consent

If you believe we have breached the Australian Privacy Principles or mishandled your personal information, you have the right to:

• Complain to us first: Contact our Privacy Officer at admin@cassandras-compass-dementia-care.org. We will acknowledge your complaint within 5 business days and respond within 30 days.
• Complain to the OAIC: If you are not satisfied with our response, you may lodge a complaint with the Office of the Australian Information Commissioner (OAIC):

If you are located in the European Union or United Kingdom, you additionally have the right to:

• Data portability — receive your data in a structured, machine-readable format
• Object to processing — object to processing based on legitimate interests
• Restriction of processing — request that we limit processing of your data
• Lodge a complaint with your local data protection authority

You can delete your account directly within the App via the Profile screen, under Danger zone and then Delete My Account & All Data. Signing in is needed to do this. When you confirm deletion:

• Your records are deleted straight away — not scheduled for later
• Your user-scoped data (care logs, journals, medications, BPSD logs, shift records, budget records, medical notes, activity logs, emergency contacts, and the private reflective and quiz records described in Sub-sections 2.15 to 2.19) is removed
• A small number of records that organisations or we rely on for totals are anonymised instead, so they are no longer linked to you: a learning completion record keeps the pathway, the step and the date but loses your account, name and email, and a simple usage count keeps the number but loses your account
• Community posts you have created are deleted with your account, or you can delete them yourself beforehand
• A review you left on a Sponsored Provider is deleted with your account (Sub-section 2.24). If you nominated someone for an award, the nomination is kept for the nominee’s consent trail, but your name and email are cleared from it, so it is no longer linked to you (Sub-section 2.27)
• Your account is then removed, and you are signed out

You may also request account deletion by emailing us at admin@cassandras-compass-dementia-care.org with the subject line "Account Deletion Request". We will verify your identity and action the request within 30 days.

Everything about deleting your account — both ways to do it, and exactly what is deleted, what is anonymised and what we must keep — is set out on our account deletion page. That page needs no sign-in, so it is there if you cannot get into your account.

Certain limited data may be retained after account deletion as required by law:

• Financial records: Transaction records (amounts, dates, plan type) may be retained for 5–7 years as required by Australian taxation law. These records do not include your care or health data.
• Legal hold data: If your data is subject to a legal hold or ongoing investigation, we may retain it until the matter is resolved.
• Anonymised aggregate data: Statistical data that has been irreversibly anonymised may be retained indefinitely for analytics and product improvement.

Deleting your account does not cancel a subscription. A subscription is held by the company that bills you for it, so it continues until you cancel it, and deleting your account does not stop it. Cancel it first so you are not billed again.

If you subscribed through the Apple App Store, cancel it in Settings, then your name, then Subscriptions. If you subscribed through Google Play, cancel it in the Play Store under Payments & subscriptions, then Subscriptions. If you paid by card on our website, email us and we will cancel it for you. The full steps, with links to Apple’s and Google’s own instructions, are on our account deletion page, and we will help if you ask us to.

We encourage users to enter only the minimum information necessary for their care-planning needs. The App functions fully without any health data input. We recommend using initials or non-identifying codes rather than full names of care recipients in care logs, BPSD trackers, and transfer sheets.

Your care data is protected by Row-Level Security, meaning even our team cannot access it. This is particularly important for people living with dementia and their families, who may be sharing deeply personal health information, behavioural observations, and emotional reflections.

If you are a caregiver using the App on behalf of someone living with dementia, you are responsible for ensuring that the person you care for (where they have capacity) has consented to the information being recorded. We recommend:

• Discussing what information you plan to record and why
• Using initials or non-identifying codes rather than full names where possible
• Respecting the dignity and privacy preferences of the person you care for
• Reviewing stored data periodically and deleting entries that are no longer needed

Users who record information about another person remain responsible for ensuring they have any necessary authority or consent to do so.

The App is designed to be accessible to users with varying abilities, including those experiencing cognitive changes. We follow WCAG 2.1 Level AA accessibility guidelines, support screen readers, and provide adjustable text sizing. If you encounter accessibility barriers, please contact us.

Our community features are moderated to protect vulnerable users. We encourage community members to avoid sharing identifying information about care recipients. If you encounter content that you believe is harmful, exploitative, or puts a vulnerable person at risk, please report it immediately using the in-app reporting tools or contact us at admin@cassandras-compass-dementia-care.org.

Cassandra's Compass includes resources on elder abuse awareness and prevention. If you or someone you know is experiencing abuse, neglect, or exploitation, please contact the National Elder Abuse phone line: 1800 ELDERHelp (1800 353 374) or visit compass.info.

Cassandra's Compass is intended for users aged 18 years and over. The App is not directed at children under 13 years of age, and we do not knowingly collect personal information from children under 13 in accordance with the Children's Online Privacy Protection Act (COPPA) and the Australian Privacy Act 1988 (Cth).

If we become aware that we have inadvertently collected personal information from a child under 13, we will take immediate steps to delete that information. If you believe a child has provided us with personal information, please contact us immediately at admin@cassandras-compass-dementia-care.org and we will delete it promptly.

Users aged 13–17 may use this App only under the supervision and guidance of a parent, legal guardian, or qualified educator. By creating an account, you confirm that you are 18 years of age or older, or that you are aged 13–17 and have obtained parental or guardian consent to use the App.

Cassandra's Compass is an educational and care-planning platform focused on dementia, aged care, palliative care, and end-of-life topics. The App contains clinical, medical, and health-related content that is written for adult audiences — family carers, care workers, students, and healthcare professionals. Below is a summary of content categories that parents and guardians should be aware of before allowing a minor to access the App:

• Palliative care and end-of-life content: The App includes information about palliative care, terminal illness, dying, death, and funeral processes. This content may be emotionally distressing for children, particularly if a family member or loved one is unwell or has passed away.
• Behavioural and Psychological Symptoms of Dementia (BPSD): The BPSD Tracker and related educational content describe behaviours such as aggression, agitation, hallucinations, delusions, paranoia, screaming, and resistiveness to care. These descriptions are clinical in nature but may be frightening or confusing for children.
• Elder abuse awareness: The App contains resources about recognising and preventing elder abuse, including neglect, financial exploitation, and physical or psychological abuse. This content is intended for adult awareness and safeguarding.
• Clinical and medical imagery: Some educational pages include diagrams of the human brain, anatomy, or clinical procedures. These are anatomical/educational in nature but may be unsettling for younger viewers.
• Medical terminology: The App uses clinical terminology related to dementia subtypes, medication classes, disease progression, neurological changes, and care procedures. Children are unlikely to understand much of this content without adult explanation.
• Restrictive practices: Educational content about restrictive practices in aged care (including physical and chemical restraints) is included for professional compliance and awareness.
• Mental health and emotional wellbeing: Content addressing depression, anxiety, grief, caregiver burnout, and emotional distress is present throughout the App. While supportive in intent, these topics may be confronting for children.
• Community discussions: Community boards, student discussions, and Cass's Café allow logged-in users to post personal experiences, which may include accounts of loss, illness, or distress. Community content is moderated but is user-generated.

Children encountering the above content may experience confusion, anxiety, sadness, or fear — particularly if they are aware that a grandparent, family member, or loved one is living with dementia or approaching end of life. While the App is designed to be supportive and educational, it is not designed for children's developmental, emotional, or cognitive needs. Some content may:

• Be difficult for children to contextualise or understand without adult explanation
• Trigger anxiety about ageing, illness, or the mortality of family members
• Present clinical scenarios (e.g., behavioural symptoms, end-of-life care) that are distressing to a child who is not emotionally prepared
• Include user-generated community content describing personal experiences of grief, loss, or caregiver stress

Conversely, with appropriate adult guidance, some content may help older teenagers (e.g., students aged 16–17 studying health sciences) understand dementia and aged care in a structured, educational context.

Cassandra's Compass does not contain built-in parental controls, age gates, or content filtering mechanisms. The App does not restrict which pages a registered user can access. If a parent or guardian allows a minor (aged 13–17) to use the App under their supervision, we recommend:

• Co-viewing: Browse the App together, particularly when accessing palliative care, BPSD, elder abuse, or funeral process content
• Account supervision: The parent or guardian should monitor the minor's account activity, including community posts and care logs
• Content discussion: Be available to answer questions and provide emotional support if the minor encounters distressing content
• Community caution: Minors should not post personal information or engage in community discussions without parental awareness
• Time limits: Use your device's built-in screen time and app management tools (Apple Screen Time, Google Family Link) to manage access duration
• Regular check-ins: Discuss what the minor has read or used within the App and whether they have any concerns or questions

If a minor becomes distressed by content in the App, please contact a qualified counsellor or mental health professional. For immediate support in Australia, contact Kids Helpline: 1800 55 1800 or Lifeline: 13 11 14.

We do not knowingly collect, maintain, or use personal information from children under 13. Our registration process requires an email address and password (or third-party OAuth sign-in). We do not use age-verification technology or age gates, as the App is not directed at children. If you are a parent or guardian and believe your child under 13 has created an account without your knowledge, please contact us at admin@cassandras-compass-dementia-care.org and we will delete the account and all associated data immediately.

If you encounter content within the App that you believe is inappropriate for minors or that raises safeguarding concerns, please report it using the in-app content reporting tools or contact us directly at admin@cassandras-compass-dementia-care.org. We take all safeguarding reports seriously and will review reported content promptly.