Drop Along Logistics (DAL) relies on web cookies, local storage solutions (like the `localStorage` object handling your theme choice), and similar passive technologies. These instruments allow us to memorize authenticated sessions, configure rapid page transitions, and maintain your custom routing preferences seamlessly between visits.
To provide ultimate transparency, review the three core categories our mobile and web applications use below:
| Category | Functionality | Duration / Behavior |
|---|---|---|
| Essential (Strictly Required) | Enables core security components, routing API authorization (Supabase Auth sessions), and load balancing across server endpoints. Disabling these halts your ability to sign into the DAL Dashboard. | Session length (expires exactly when the browser runtime concludes) to up to 12 months for securely hashing ongoing user profiles. |
| Analytics & Performance | We passively monitor how Port Harcourt maps are navigated and loaded. Tools like PostHog collect anonymous structural data identifying UI bottlenecks and 404 dead ends. | Persistent objects (up to 2 years) unless regularly expunged by user OS settings. Doesn't harvest personal identity metrics. |
| Preferences (Customization) | Stores front-end interface adjustments locally. (e.g. Setting UI `dark-mode` rendering, verifying your initial cookie consent, caching recent searches). | Persistent until completely overwritten, cleared actively, or reaching manual expiration thresholds. |
Upon your first visit to the DAL hub, a localized consent banner allowed you to selectively opt into analytical matrices or limit deployment purely to the "Essential Only" category. You maintain absolute rights to revoke permission or purge active tokens via your browser environments.
Please note that entirely suppressing first-party data via restrictive browser measures will corrupt or completely interrupt DAL's core mapping interface and personal dashboard synchronization.