Legal

DUBHCORE — Cookie Policy (dubhcore.com)

Version 1.0 — Date: 30 August 2026 — Final version

Verified result of the Hub's technical audit

The technical audit of the code of the DUBHCORE Hub (dubhcore.com) has confirmed that, based on the current implementation of the Hub:

  • the Hub code does not install first-party cookies;
  • no analytical, marketing or profiling cookies are installed;
  • no localStorage, sessionStorage or IndexedDB is used;
  • no analytics (incl. Google Analytics/GTM), pixels (Meta/TikTok), advertising, fingerprinting, heatmaps or session recording are present;
  • no cookie consent banner is currently used (as no non-technical cookies are present);
  • the payment checkout takes place on Stripe's external domain (buy.stripe.com), outside the Hub;
  • fonts and the "Origin" image are hosted locally: the previous external requests to Google Fonts and Unsplash have been removed.

Verification limit (technical honesty): the above concerns the Hub code. Any cookies or headers at the infrastructure/hosting level (set by the platform provider outside the Hub code) are not verifiable from the code and must not be invented: if present, they remain subject to the hosting provider. The Emergent DPA defines the "Log Data" (IP, approximate location, browser, session/device identifiers, telemetry), and the relevant retention period was not communicated or confirmed by the provider (Emergent): these logs are managed by the provider within its own infrastructure and applicable terms/documentation; DUBHCORE does not state an unverified numerical period.

DUBHCORE mobile application (for completeness)

In the code of the DUBHCORE app (not the Hub):

  • No analytics/tracking/advertising system (absence VERIFIED).
  • On the device, AsyncStorage/SecureStore are used for technical purposes (session/token, preferences): functional local storage, not aimed at profiling.

Contacts

DUBHCORE — info@dubhcore.com — https://dubhcore.com.

IMPORTANT: do not declare the presence of analytics/pixels/profiling, as they are not present according to the audit; do not declare the absolute absence of every possible cookie at the infrastructure level if it is not verifiable from the code.