Legal
Cookie Policy
Digital Empire Holdings LLC · Last updated: August 20, 2026
In plain English: Digital Empire Holdings LLC uses a small number of cookies to keep you signed in, protect forms from cross-site attacks, and — only if you say yes on the cookie banner — to understand which pages people find useful and to catch errors before they become support tickets. We do not run third-party advertising cookies, we do not sell or share cookie data with data brokers or ad networks, and we do not use fingerprinting.
1. How your choice works
The first time you visit, a banner asks you to Accept all, Decline non-essential, or Manage preferences. Essential cookies always run (the site cannot function without them, see the table below). Analytics and error-tracking cookies only run if you accept.
If our system detects you're visiting from the EU / EEA / UK / Switzerland (via a coarse, server-side country signal — no precise location is stored), analytics defaults to off until you explicitly accept, per GDPR. Everyone else gets the CalOPPA default: analytics runs unless you decline.
Your choice is saved in your browser's local storage and a first-party cookie for one year; you can change it any time by clearing your browser's site data for this domain and reloading, or by emailing support@digitalempireholdings.com.
2. Cookie categories
3. Necessary cookies
These are strictly required for you to sign in, submit forms, or complete checkout. They are set by the first-party domain and cannot be turned off in the consent banner (turning them off would break the site). No consent is required for these under ePrivacy / GDPR because they are "strictly necessary" to deliver the service you explicitly requested.
4. Analytics & error-tracking
We use two analytics vendors, both loaded only after you accept:
- PostHog — product analytics (which pages, which buttons) and masked session replay (all text and input fields are masked before recording). US-hosted. See PostHog's privacy policy.
- Sentry — client-side JavaScript error tracking, so we can find and fix bugs. US-hosted. See Sentry's privacy policy.
Both vendors are listed as sub-processors on every per-product sub-processors page and in the DPA (/dpa).
5. Marketing attribution (first-party, no ad targeting)
When you click a UTM-tagged link (e.g. from a blog post, referral partner, or one of our emails), we set a first-party cookie so we can credit the referring source on signup. We do not use this data for ad retargeting or share it with any ad network. We do use Rewardful for referral-partner attribution (see the Rewardful cookie in the table above) — it is loaded portfolio-wide from the site layout and sets a single first-party cookie linking your session to a referring partner's code.
6. What we do not use
- No third-party advertising cookies (no Meta Pixel, no Google Ads remarketing tag, no LinkedIn Insight Tag on the app itself).
- No data-broker pixels or tag-manager containers loaded on our own site.
- No device fingerprinting or cross-site tracking.
- No sale or sharing of personal information as defined by CCPA / CPRA. We honor Global Privacy Control (GPC) signals as an opt-out for any future advertising purpose.
Bing UET (Microsoft Advertising conversion tag) is conditionally loaded from the site layout only when the site owner has configured it via environment variable (currently not live in production). If it goes live, it will be gated behind the same consent banner and disclosed here.
7. Per-product cookie disclosures
Each product page ships its own product-specific cookie disclosure, since the exact cookie names / vendors overlap but the product context differs:
8. Contact
Questions or opt-out requests: support@digitalempireholdings.com. The trust hub (/trust) links every legal document.
This portfolio-level policy is versioned; the per-product cookie pages remain the detailed source of truth for each product surface. Where this document and a per-product cookie page conflict, the per-product page controls for that product.