Every device
A therapist runs a session on a phone, a supervisor reviews on a laptop, a parent checks the schedule on a tablet. BrightPath is a native app on phone and tablet today, with a full web version anywhere, and it feels right on each. Here is where every platform stands, including the ones still being built, and how each one keeps data safe.
See it on every screen
A therapist runs a session on a phone, a supervisor reviews the caseload on a laptop, a parent checks the schedule on a tablet. It is one app, and it feels right on each.
The constant
Whatever device a person picks up, BrightPath works the same way: the same record, the same layout, the same care team. A note written on a phone is on the laptop a moment later. What changes from device to device is only the plumbing underneath, including how each one encrypts data and stores its keys, and the security page spells that part out in full.
Device by device
The documented platforms are exact. The ones still in progress show the intended direction and are marked plainly, so nothing here is a promise we have not kept.
The full BrightPath app runs here today, and this is also the reference the security model is built and documented against.
Under the hood
Encrypts with
Apple CryptoKit, on the device.
Keys live in
The iOS Keychain, available only after first unlock, bound to that device and backed by the Secure Enclave.
iPad is part of the iOS app, so it shares the iPhone implementation exactly.
Under the hood
Encrypts with
Apple CryptoKit, the same Swift code as iPhone.
Keys live in
The iPadOS Keychain, hardware-backed on modern iPads.
A native Mac app is in the works. Because it shares Swift with iOS, the intent is to carry the same CryptoKit and Keychain approach across. The design is still being finalized. Until it ships, the web version runs on a Mac.
Under the hood
Encrypts with
Planned: Apple CryptoKit, since the Mac app will be written in Swift.
Keys live in
Planned: the macOS Keychain, with Secure Enclave backing on Apple silicon.
The Android app is in development on the same secure foundation. The exact cryptography and key-storage choices are being worked out and will be documented here as they land.
Under the hood
Encrypts with
Being finalized. It will implement the same AES-256-GCM envelope contract.
Keys live in
Expected to use the platform's hardware-backed key store, the Android Keystore.
The web version is available today so anyone can use BrightPath without installing anything. The browser-side field-encryption approach is still being worked on, and this page will spell it out once it is settled.
Under the hood
Encrypts with
Being decided. The envelope format is cross-platform by design; which browser cryptography the web version uses, for example the Web Crypto API, is still open.
Keys live in
How the browser holds keys is part of that open design work.
A native Windows app is on the roadmap; the approach has not been picked yet. Until then, the web version runs on Windows in any browser.
Under the hood
Encrypts with
Not chosen yet.
Keys live in
To be determined.
The security page lays out exactly how BrightPath encrypts records, who can open them, and the honest limits, on the reference platform and across the rest.
