Cookie & Storage Policy

DR.CORD uses browser-managed storage to keep users signed in, remember runtime preferences, operate the PWA, cache static assets, and preserve offline workflow continuity.

Storage may include localStorage, IndexedDB, Cache Storage, Firebase Authentication persistence, service worker state, notification permission state, and browser-managed PWA installation data.

IndexedDB is used for offline-first clinical and operational data including patients, billing drafts, sync queues, operational events, drafts, locks, hydration manifests, subscriptions, transaction journals, conflict records, background jobs, upload queues, runtime sessions, notification queues, device state, display state, presence state, storage manifests, secure cache, inventory batches, vendors, lab templates, and consent records.

IndexedDB schema migrations are versioned. Browser storage errors, quota pressure, manual clearing, private browsing, or profile corruption may affect offline operation.

The DR.CORD service worker supports installability, offline fallback, asset caching, background sync signals, upload sync prompts, periodic maintenance prompts, push notifications, and update lifecycle events.

Static assets and selected runtime URLs may be cached. Sensitive operational records should be treated as present on the device while a user is signed in and local caches are intact.

Authentication persistence is configured for browser-local continuity so staff do not lose work during normal refreshes. Clinics using shared machines must enforce logout and device-lock discipline.

Clearing browser site data may remove local sessions, cached drafts, queued offline actions, and install readiness state.

Notifications are optional browser permissions used for operational alerts and PWA behavior. Denying notifications does not prevent core clinical workflows, but may reduce timely awareness of workflow updates.