Privacy Policy
This Privacy Policy explains how Systems Mastery Pty Ltd ATF Mann Family Trust trading as Systems Mastery (ACN 138 024 441, ABN 62 698 393 859), of Albert Road, Lilydale, Victoria 3140, Australia, collects, uses, stores and shares information when you use Lifestyle Journal OS (LJOS).
LJOS is a private journal. Most of what follows is a description of how little we do with what you write.
1. Information we collect
Account information
Your email address. A hashed password, if you choose to set one — you can log in with a one-time link instead and never create a password at all. Your display name, if you give one. Metadata about your sessions — IP address, browser user agent and login times — which we use for security and rate limiting.
What you write
Everything you enter in the app: your morning and evening reflections, journal entries, goals, habits, tasks, the people you add to your own register, your identity page, and every log you keep against the five SEEDS dimensions. This is stored in your own workspace in our database.
Diagnostics
When the server hits an unhandled error we email ourselves a report containing the error message and stack trace, rate-limited so a fault cannot flood the inbox. These reports are about code, not about you: they are not designed to carry journal content, and we do not attach it. We do not run third-party analytics, and there is no advertising, tracking or behavioural profiling anywhere in LJOS.
2. Health and other sensitive information
This deserves its own section rather than a line inside the one above. LJOS invites you to record how you slept, what you ate and drank, how you exercised, what supplements you take, how you felt, and who you spent time with. Some of that is health information — “sensitive information” under the Australian Privacy Act 1988 and a “special category” of personal data under the GDPR. Both give it a higher level of protection than ordinary personal data, and both require your consent before it is collected.
You give that consent by choosing to write it down. Every field in LJOS is optional; nothing is required for an entry to count, and a day you leave blank stays blank. We collect this information for one purpose — to show it back to you and to compute your own scores and patterns from it.
We do not, and will not:
- Sell it, rent it, or share it with advertisers or data brokers.
- Use it to train machine-learning models, ours or anyone else’s.
- Disclose it to insurers, employers, or any third party, except where the law compels us and we are not permitted to tell you.
- Read it as part of routine support. If you ask us for help we will ask you to describe the problem rather than open your journal, and we will say so if that ever has to change.
LJOS is not a medical device and makes no medical or mental-health claim. See Section 6 of the Terms of Service.
3. How we use information
- To run the service — logging you in, keeping you logged in, and scoping every query to your own workspace.
- To send transactional email. Today that is exactly two things: a login link, and a password reset. Both are sent because you asked for them seconds earlier.
- To keep the service secure — rate limiting, abuse detection, and diagnosing faults.
- To comply with legal obligations.
We send no marketing email, no reminders and no nudges — not because we are being generous, but because the features that would send them have not been built. If that changes, it will come with a preference you set and an unsubscribe link, and this page will say so before the first one is sent.
Scout is off unless you turn it on, and nothing goes to an AI provider until you do. That is a property of the product, not a promise about our current workload: a new account has Scout disabled, the switch is on its own settings page, and that page tells you who processes your data, what is sent and how long conversations are kept before you decide. The public demo forces it back off every time it resets.
What is sent when it is on. Your question, and the figures this app has already worked out from your entries — your daily scores, your dimension averages, your habit runs. Not what you wrote. Scout reaches an actual journal page only when you ask something that needs one, and that request is recorded in the conversation so you can see it happened. It goes to Anthropic, who return an answer and do not keep it to train models.
Conversations are stored in your workspace for a period you control, travel with your export, and are deleted with your account.
4. Voice dictation
The journal has a dictate button that uses your browser’s own speech recognition. What happens to your voice depends entirely on the browser you use, and we want to be specific because the differences are real:
| Browser | Where your voice goes |
|---|---|
| Chrome and Chromium browsers | Streamed to Google to be turned into text, under Google’s terms, not ours. |
| Safari (macOS and iOS) | Transcribed on your device. |
| Firefox | Not supported — the button is absent rather than disabled. |
In every case, your audio never reaches our servers. We receive only the text that the browser produces, and only once you save it as part of an entry. We store no recording, and there is no recording for us to store. If you would rather Google were not involved, dictate in Safari or type.
5. Sub-processors
These are the only third parties that receive any of your data as part of running LJOS. Each is bound by their own privacy commitments.
| Provider | Purpose | Region |
|---|---|---|
| Railway | Application hosting, PostgreSQL database, and database backups | EU West (Amsterdam) |
| Resend | Transactional email delivery (login links, password resets) | US |
| Anthropic | AI inference for Scout — receives only what a Scout conversation needs, and only while Scout is switched on. Scout is off by default; each workspace turns it on for itself. | US |
A short list, and that is the point. There is no payment processor, because nothing is charged yet. There is no file storage, no analytics vendor and no advertising network.
Anthropic was listed before it was used, which is the promise this policy makes. They appeared in this table on 8 November 2026, when the code that calls them entered the application — before any credential existed and before Scout could be switched on by anyone. Scout now works (Section 3). Nothing from your journal reaches Anthropic while your Scout switch is off, and when it is on, what goes is described above. A reader deciding whether to trust this product with a journal is owed the earlier of those two dates, not the later one.
6. Cookies
We set one cookie to keep you logged in, and store your theme choice in your browser. There is no tracking of any kind. The Cookie Policy lists every one by name.
7. Getting your data out, and deletion
Export works today and needs no one’s permission. Settings, under Data & API, gives you your entire workspace as a ZIP — every entry, every log, every score — in open formats, as often as you like.
Deletion is by request, and we would rather tell you that than imply a button exists. There is no self-serve “delete my account” control yet. Email us at contact@systemsmastery.com from your account’s address and we will delete your workspace and account from the live database. We will confirm when it is done, and we will do it within 30 days of the request. Export first if you want a copy — deletion is not reversible by us.
8. Retention
We keep your account and journal for as long as your account exists. There is no inactivity sweep: an account you do not open for a year is still yours, and we will not delete it to tidy up.
After we delete your data from the live database, copies persist for a period in our database backups. Our host, Railway, keeps continuous point-in-time recovery for our database — a rolling archive that lets us restore to a moment in the recent past if something goes badly wrong. Deleted data ages out of that archive as the window rolls forward past the deletion date. We do not operate a separate long-term snapshot schedule, so there is no older copy sitting behind it.
Email delivery logs held by Resend are retained under their standard retention for deliverability and anti-spam compliance.
9. Security
HTTPS everywhere. Passwords hashed, never stored in a form we can read. Encryption at rest for the managed database. Rate limiting on login and on the public API. API keys you create are stored as SHA-256 hashes and shown to you exactly once, so a leak of our database does not hand anyone your key.
Every workspace is isolated at the database level — each query carries the workspace it belongs to — and that isolation is covered by an automated test suite that runs against a real database on every change, including tests that have been deliberately broken to prove they can catch a leak.
No system is perfectly secure. If we confirm a breach affecting your data we will tell you without undue delay, and within 72 hours where the law requires it.
10. Your rights
Depending on where you live, you may have the right to:
- Access the personal information we hold about you.
- Correct it, if it is wrong — though in a journal you can edit almost all of it yourself.
- Delete your account and its contents (Section 7).
- Receive your data in a portable format (Section 7 — this one is a button).
- Withdraw consent, including for the health information described in Section 2, by deleting the entries or the account.
- Lodge a complaint with your data-protection authority — in Australia, the Office of the Australian Information Commissioner.
Email contact@systemsmastery.com to exercise any of these. We respond within 30 days. If we refuse a request we will explain why and how to challenge it.
11. International transfers
We are an Australian company. Our database and application run in the European Union (Amsterdam); our email provider is in the United States. If you are reading this from somewhere other than those places, your data crosses a border to reach us. We rely on standard contractual clauses and equivalent safeguards for those transfers.
12. Children
LJOS is not directed at children under 16 and we do not knowingly collect their information. If you believe a child has created an account, contact us and we will delete it.
13. The public demo
The demo workspace is shared, public and periodically reset. It contains synthetic data, not anybody’s real journal. Treat anything you type there as public and temporary — it is not private to you and it will be erased.
14. Changes
We will update this policy as the product changes. Where a change materially affects you — a new sub-processor, a new category of data, anything to do with Scout — we will notify you by email or in the app before it takes effect.
15. Contact
Privacy questions go to contact@systemsmastery.com. For requests under the Australian Privacy Act, the GDPR or similar laws, please include enough detail for us to verify who you are.

