Security & privacy

Authority on the server.
Consent in the record.

Dawnby is built so that roles, care access and money records follow fixed rules that the server checks. This page only describes what the current local build already does. Anything that is not built yet is labelled Planned.

This is a product explanation for the local preview, not a certification claim.

Access controls

Who can act, and on whose data.

Live in local build

Server-side sessions

What you can do comes from your signed-in session, which the server keeps. A page or app cannot ask for extra rights in a request. Permissions are checked again after each action.

Live in local build

Role permissions

Accounts use fixed, reviewed role templates. An administrator can limit an account to particular clients and programmes. Each action runs only if the current account is allowed to do it.

Live in local build

Two-step sign-in

People can turn on two-step sign-in (MFA) with a code from an authenticator app, plus single-use recovery codes. Administrators can require it for office roles. It cannot be required for workers yet, because the phone app cannot set it up.

Live in local build

Passwords stored safely

Passwords are never stored as written. Dawnby keeps only a scrypt hash, a slow one-way scramble that cannot be turned back into the password.

Live in local build

Consent-gated care records

Care records open only with current portal consent. Family and nominee access follows what the provider has shared for that account. Being family does not open every record.

Live in local build

Append-only records

Financial and evidence records cannot be edited or deleted. A correction is added as a new linked record, so the history stays visible.

Live in local build

Encrypted pending phone data

If the phone cannot confirm that a send went through, that unsent item, which may contain care text, is stored encrypted on the phone. It is locked to one account and cleared if a different account signs in. Only these pending items are stored this way today.

Live in local build

The preview stays on this computer

The preview server only accepts connections from the same computer (loopback, 127.0.0.1). It refuses any other address, so it is not reachable over a network.

Live in local build

No plan money handled

Dawnby does not process NDIS plan money or client-to-provider payments. Claim files and invoices are prepared for the provider to submit.

Live in local build

No trackers or session replay

Dawnby's pages and phone app load no analytics or advertising trackers, no session replay and no crash reporting that sends your information elsewhere. Nothing about the people you support, their health or your money goes to a third party. One could only ever be added with the owner's written approval and processing in Australia, and none has been. Every change is checked for known tracker services.

Not built yet

What is planned for production.

Planned

Australian hosting

Production hosting in Australia is planned. Today the preview runs only on the computer it is installed on, so it must not be treated as a hosted service.

Planned

AI and personal data

No AI features are live. If any are added, AI will only suggest and a person will confirm. AI content will be labelled, AI will never send anything by itself, and each provider will be able to switch it off. No outside AI service will handle personal or health data without an owner privacy decision and consent.

Planned

Encrypted drafts on the phone

Saving unfinished drafts encrypted on the phone, locked to one account and wiped on sign-out, is planned. Today only unsent pending items are stored encrypted.

Planned

Per-person extras

A small set of safe per-person extras, switched on or off on top of the fixed role templates, is planned. Today accounts use the fixed templates only.

Planned

External sends

Real emails, SMS, payments and government submissions wait for hosting and an explicit owner decision. Until then, receipts in local previews stay labelled as samples, not real outcomes.

A few useful answers

Security questions.

Is Dawnby certified?

This page does not claim any certification. It describes how the current local build works.

Where is data hosted today?

Australian hosting is planned. Today’s preview runs only on the computer it is installed on. Do not put real personal information into sample workspaces.

Can AI see care notes?

No AI features are live today. Before any are added, the plan is that no outside AI service will handle personal or health data without an owner privacy decision and consent, and providers will be able to switch AI off.

Where are the legal drafts?

The privacy policy, terms of use and accessibility statement are drafts pending legal review and are not in effect.

Keep reading

Draft policies.
Clear status labels.