Dropp logodropp
Sign in
All policy drafts

Cookies and Local Storage

Draft notice for Dropp sign-in storage, preferences, offline assets and optional services.

Draft for legal review • updated 2 November 2026 • not yet an effective agreement. Operator identity is verified against CAC records (BN 9776404). Fund custody (Flutterwave), provider permission and the data-retention schedule are now stated. Final sign-off by a Nigerian lawyer is pending before adoption. These drafts do not certify regulatory compliance or replace the currently accepted seller agreement.

1. Necessary device storage

Dropp uses browser storage for sign-in sessions, preferences, pending links and the wallet funding destination. The service worker stores static app assets and an offline fallback; authenticated financial responses must remain uncached so wallet information stays fresh. Signing out and browser storage controls affect what remains on your device.

2. Optional processing

Web Push needs browser permission and can be disabled in device settings. Camera permission supports QR scanning. Any non-essential analytics, advertising or tracking technology requires a verified inventory, lawful basis and consent controls where required. This draft does not claim there are no third-party cookies.

The final notice must list actual storage names or categories, providers, purposes and expiry periods based on an audit. Browser clearing may remove preferences but does not delete legally retained server records. Privacy requests follow the Privacy draft.

Official references

Current NDPC registration guidance and applicable gaming authorisations still require legal verification. A policy does not obtain a licence or cure an unauthorised service.