Mobile device
- 1.A caregiver records a medication, note, task, or visit.
- 2.The change is written immediately to local SQLite.
- 3.A local key encrypts the sync payload before it leaves the device.
Local-first, encrypted by design
How your care data moves.
Caregiver Dashboard keeps the working record on the device first, encrypts changes before they leave it, and brings approved devices back into sync when connectivity returns.
The two-way sync cycle
The original sync-cycle graphic below shows how a care event moves from local capture to encrypted server persistence and back to approved devices.
THE TWO-WAY SYNC CYCLEMobile-only local-first end-to-end encrypted sync hub
STAGE 1: WRITE EVENT (LOCAL TO SERVER)
Server persistence and sync hub
The encrypted payload waits in the sync queue, then reaches server persistence with family scope, actor metadata, and timestamps.
CIPHERTEXT + RLS METADATASTAGE 2: SERVER PERSISTENCE AND BROADCAST
Database operations
- 4.Store the encrypted row and its scope metadata.
- 5.Apply automated retention for old sync records.
Realtime coordination
A realtime event tells approved family devices that new encrypted data is available. The broadcast carries coordination metadata, not plaintext care notes.
NO PLAINTEXT PHISTAGE 3: RECEIVE EVENT (SERVER TO LOCAL)
Local device receives the change
- 6.The device receives a sync event when it is online.
- 7.It fetches the encrypted row for its authorized family scope.
- 8.The local key decrypts the payload.
- 9.The local projection merges the row into SQLite for the next screen render.
What the caregiver sees
The same care record appears across approved devices, with offline writes preserved and conflicts resolved by explicit version and timestamp rules.
CONVERGENT LOCAL UXThree principles behind the cycle
The mechanics are intentionally straightforward: the device stays useful without a network, while the sync layer protects scope and keeps every approved device aligned.
Work does not stop offline
Caregivers can capture what happened immediately. The local record is the source of truth for the active workflow.
Payloads leave the device protected
Sync transports encrypted blobs with the metadata needed for routing, authorization, and convergence.
Only approved contexts converge
Family and patient scope stays explicit so the right people see the right record on the right device.
Clear handoffs start with a dependable record.
From a family caregiver’s phone to an independent caregiver’s caseload, the workflow keeps documentation close at hand and synchronization deliberate.
Get Started