A little support. A lot of care.

You are in control

There is no diagnosis, assessment score, treatment advice, or automated risk judgement here. Mood notes are not monitored, and no one is notified when you write them. This app cannot provide emergency care.

Activities are optional wellbeing suggestions. You can adapt, skip, or stop them. Grounding is adapted from NHS inform guidance; sleep and routine ideas are informed by NHS wellbeing guidance, not a treatment plan. Each activity includes its source.

Sensitive information stays here

Private records are encrypted at rest with AES-256-GCM, a fresh random IV for every write, and a non-extractable key stored by the browser in IndexedDB. The key is not derived from a password.

There is no account, personal-data upload, advertising code, analytics added by this app, or cross-device sync. An app function checks public Portland resource websites when online; it receives no mood notes, wait-lists, or location. Hosting platforms and third-party websites may have their own logs. Your approximate area is entered by you; no GPS permission is requested.

Use a device screen lock. Encryption cannot protect against an unlocked session, malicious same-origin scripts, a compromised device, or browser-profile access. Exports are readable JSON and are not encrypted. Deleting local data replaces the snapshot and its encryption key; downloaded exports and device backups are not removed. For native distribution, use an encrypted SQLite store and an OS-keystore key; this web build does not provide that native guarantee.

What “fully offline” means

Framework: React + TypeScript as an installable progressive web app. After one successful online load on the published site, a service worker caches all app screens, styles, icons, and activity content. Then the plan, tracker, directory snapshots, and saved resources work without internet.

It cannot install itself for the first time without a connection, fetch current wait times while offline, open outside websites offline, or make a call without phone service. Private browsing and clearing site data can remove offline storage.

How updates and conflicts work

Personal entries are written directly to encrypted local storage, even offline. Reconnecting reloads the latest local snapshot, checks for app-shell updates, and retries public-source refresh if the last successful check is over 6 hours old. Personal data has no cloud queue and never leaves this device.

Browser Web Locks serialize reads and writes between tabs where supported. Each action applies to the newest stored snapshot. Edits to the same entry use the last completed write. On browsers without Web Locks, use one tab to avoid conflicts.

Directory imports merge by stable id and newest last-updated date. Equal timestamps keep the existing entry. Older-than-7-days details show a warning; saved snapshots update only when you choose to refresh them. Official Portland support sources refresh online. These sources do not supply a numerical wait-time feed, and the app never infers an estimate.