Cookie Policy

This policy covers cookies, browser local storage, and IndexedDB — collectively "storage" below — used by the ReliefCommand web app. Read it alongside our Privacy Policy, which covers the data itself rather than where it's stored in your browser.

1. The short version

ReliefCommand doesn't use advertising or third-party tracking cookies. Everything we store in your browser is either your own app data (sign-in, offline inventory) or diagnostic data for our error monitoring — none of it is optional, so there's no cookie preference toggle to set.

2. What we store, and why

• App local storage keys: theme, contrast, and text-size store display preferences; selectedWarehouseId stores the selected warehouse; userRole stores a display hint while the server verifies the session; rc-cookie-notice-ack-v1 remembers dismissal of the storage notice. A legacy selectedOrgId key is cleared on sign-out and is not used for authorization.
• reCAPTCHA Enterprise may use cookies and browser storage for abuse-prevention signals when App Check is configured.
• Sentry replay storage uses session storage to retain replay session identifiers and buffers diagnostic events in memory before upload. Text and images are masked by default.
• Sign-in session (Firebase Authentication) — keeps you logged in between visits so warehouse staff and org managers aren't re-authenticating constantly. Removing it signs you out. Stored in IndexedDB, not a server-readable cookie.
• Offline inventory & order cache (Firestore) — the dashboard keeps a local copy of recently loaded products, boxes, and orders for offline reading. Plain edits can queue for reconnection; transactional changes such as receiving stock or changing order status require a connection. Clearing it means the next load starts from a clean cache. Stored in IndexedDB.
• Display preferences — remembers lights (day or night), high contrast, and text size on this device. Stored in local storage.
• Error monitoring (Sentry) — when something goes wrong, our error-monitoring provider may briefly buffer diagnostic data and, for a sample of sessions and any session where an error occurred, a session replay (see our Privacy Policy for what that can capture) in your browser before sending it to Sentry. This isn't a cross-site tracking cookie — it exists to help us find and fix bugs.

3. What we don't use

No advertising cookies, no third-party analytics or cross-site tracking, and no cookies sold or shared with anyone.

4. Managing storage

Your browser's settings let you clear cookies, local storage, and IndexedDB for this site at any time. Doing so will sign you out and drop the offline cache — the app will rebuild both the next time you load it and sign in.

5. Changes to this policy

If what we store changes — say, we add an analytics tool — we'll update this page. Questions about it: support@dyltec.com or 1741 Dexter St, Dubuque, IA 52001. See also the contact page.