At a glance
- Authentication cookies support secure store access.
- Browser storage can hold preferences and offline POS records.
- No advertising pixels are currently used by DigiKaha.
1. Cookies and other browser storage
Cookies are small values a website stores in your browser. DigiKaha also uses local storage, IndexedDB, and browser caches. These are different technologies, but this statement describes them together because they keep information on your device.
The public landing page does not require a store login. Store authentication storage is used when you open your dedicated workspace. The sample checkout on the landing page keeps its cart in page memory and does not create a real POS transaction.
2. What the service stores
Names can vary by deployment and secure-cookie prefix. The following reflects the current application configuration.
| Storage | Purpose | Duration or removal |
|---|---|---|
| Session cookies: digikaha-store-session, digikaha-superadmin-session, or authjs.session-token, with __Secure- prefixes in production | Keep an authenticated account signed in to the appropriate workspace. | Session validity is configured for up to 8 hours; a renewed session may extend access. Sign out to end the active session. |
| Security and redirect cookies: authjs.csrf-token and authjs.callback-url, with secure prefixes where applicable | Protect sign-in requests and remember the return address for authentication. | Managed by the authentication flow and browser cookie settings. |
| Local storage: digikaha_cookie_consent and theme preferences such as digikaha_theme_global | Remember that you acknowledged the storage notice and keep display preferences. | Persist until replaced or removed through the browser’s site-data controls. |
| IndexedDB: digikaha_offline_db | Store cached products and settings, queued POS orders, and offline staff verification records on a terminal where those features are used. | Until the application’s cleanup rules apply or local site data is removed. Pending orders must be synchronized first. |
| Service-worker caches: digikaha-pos-* and digikaha-static-* | Cache application resources and pages to support loading and the installed web app. | Replaced as cache versions change or removed through browser site-data controls. |
3. Third-party resources and tracking
DigiKaha does not currently use advertising pixels or cross-site advertising trackers. Technical error reporting and security checks are used for operating the service, rather than advertising profiling.
Google Fonts may receive connection details when typography is loaded from its servers. Protected login screens may use Cloudflare Turnstile, which processes browser and connection information to check for automated abuse. These providers have their own privacy practices. The DigiKaha ad is hosted with the website rather than embedded through a third-party video player.
4. The storage notice
The notice explains essential cookies and browser storage and saves your acknowledgement. It is not permission for unrelated marketing, and acknowledging or dismissing it does not turn off storage required for sign-in or POS functions.
There are currently no optional advertising-cookie categories to enable. If optional tracking is introduced, the statement and controls must be updated before it is used where consent is required.
5. Managing storage and shared terminals
Use your browser’s privacy settings to inspect or delete cookies and site data. Browser profiles and different subdomains may hold separate records, so check the relevant store address as well as the public website. Blocking authentication cookies can prevent sign-in; removing preferences resets display choices.
- Before clearing a POS terminal, reconnect and confirm queued sales have synchronized. Clearing IndexedDB can permanently remove unsent transactions.
- Sign out when you finish using a shared device, and limit access to the browser profile that holds store data.
- Deleting a cookie does not delete cloud business records or a subscription. Request those changes by email.
6. Questions and updates
For questions about a particular browser record or your store’s device setup, email parungao.johnlloyd07@gmail.com. We update this statement when storage practices change and show the updated date. Read the Privacy Statement for the broader handling of personal information.