1. What are Cookies & Tracking

This Cookie & Tracking Policy details how [DooGhoont Software Operations] ("we", "our", or "us") uses cookies, localStorage variables, encrypted container blocks, and telemetry tracking technologies across our Next.js management website, web administrative dashboard portal, and mobile software applications (the "DooGhoont Platform").

Cookies are tiny files stored on your web browser by a website. Telemetry tracking structures include SDKs, APIs, and client-side memory spaces (like LocalStorage on web and SecureStore on mobile OS) used to cache parameters, retain auth sessions, and sync offline transaction records.

2. Strictly Necessary Storage

Necessary cookies and local variables are essential to log users in securely, keep administrative sessions alive, and prevent offline transaction data loss in areas with poor mobile reception. We utilize these tools for the following functions:

Authentication State: We store session tokens (`dooghoont_access_token` and `dooghoont_refresh_token`) securely. On web browsers, these are cached in `localStorage` or secure cookies. On mobile platforms, these are encrypted via OS-level hardware modules (`SecureStore`).
Cached Data & Telemetry Profiles: User profiles (`dooghoont_user_data` and last active sync logs) are saved locally to support immediate startup without waiting for remote API downloads.
Offline Sync Queues: Actions performed while offline (e.g. outbox dispatch entries and rider trip events) are stored locally in the web browser's LocalStorage (`dooghoont_outbox_v1`) or the mobile device's isolated file system (via JSON files managed by `expo-file-system`). This prevents the loss of financial audit metrics and bottle tracking counts.

3. Analytics & Telemetry Tracking

Analytics cookies help us evaluate page views, detect system errors, and monitor load speeds to optimize SaaS dashboards.

Vercel Analytics: Our public website integrates Vercel telemetry to evaluate operational visitor volume, geographical regions, and device configurations. No personally identifiable data is sent to external trackers.
Operational Logs: Telemetry logs capture active API latency and error traces (e.g., failed location synchronization warnings or outbox buffer limitations) to help our engineering teams prevent software bugs.

4. How to Manage Tracking

Most web browsers accept cookies automatically, but you can configure your browser preferences to reject cookies or prompt you before accepting them.

If you disable necessary storage options or clear your browser's LocalStorage, you will be logged out of your SaaS portals, and any unsynced offline ledger edits or transaction outboxes will be permanently lost.

For inquiries about cookies, contact us at: privacy@dooghoont.com.