EBD policies & transparency
Cookie Policy
Understand the technologies, purposes, and choices that affect your visit.
On this page 6 sections
Policy version: October 18, 2026
1 Scope and operating rule
This policy sets the rules for cookies and similar technologies used through ebd.pro, operated by Enterprise by Design, LLC. It supplements our Privacy Policy.
Cookies are small browser files. Similar technologies include local storage, pixels, scripts, device identifiers, and embedded services. Privacy requirements can apply to a technology described as "cookieless" or using first-party storage.
Optional analytics, referral attribution, and other optional tracking require an affirmative choice before activation unless EBD has documented a specific lawful exception and provides the required information and objection method. EBD's policy prohibits sale of personal information, cross-context behavioral-advertising sharing, and targeted advertising.
2 Categories and purposes
Category | Purpose | Choice |
|---|---|---|
Required functions | Requested account sessions, authentication, necessary checkout or security, and remembering privacy choices | Limited to what is necessary for the requested function |
Analytics | Permitted measurement of visits, content use, or events | Off until allowed, unless a disclosed, documented exception applies |
Referral attribution | Attributing an eligible signup or purchase to an affiliate | Optional tracking requires permission; commission records are handled separately |
Optional media or features | Loading a third-party feature you choose to use | Permission before any nonessential access, storage, or tracking |
Only optional categories actually offered are to appear in Customize. Before requesting permission, EBD must identify the provider, purpose, information or technology involved, and relevant duration. Different purposes must have separate choices where required.
An embedded service or payment provider can have both necessary and optional features. The provider's name alone does not determine the classification. Revenue generation is not a necessary-function exception.
Ghost analytics, member-source attribution, and newsletter engagement measurement require separate assessment. Cookieless website analytics does not authorize member-level measurement, affiliate tracking, or tracking inside email.
3 First visit choices
On a first visit without a valid saved choice, EBD will provide a consent window with Reject optional, Accept all, and Customize. Rejection must be as easy to find and use as acceptance. Closing the window, pressing Escape, scrolling, or continuing to browse does not grant permission.
Customize lets you select the available optional purposes and save your choice. Required functions remain available. Rejecting optional tracking must not prevent ordinary browsing or essential membership use; a particular optional external feature may need permission before loading.
EBD will keep Cookie preferences readily accessible throughout the website so you can reopen it and change or withdraw permission. Withdrawal must stop subsequent optional processing based on that choice and remove or expire relevant storage within EBD's control where appropriate. It cannot reverse a disclosure that already occurred. Required deletion or other privacy rights remain available separately.
These rules apply to every relevant EBD-controlled script and integration, including code injection and embedded features. A service must remain disabled unless its operation meets these rules or an identified legal exception.
4 Preference duration and technology details
EBD's consent-preference record is limited to 180 days, unless you clear it, replace it, or an earlier new choice is required. We will seek a renewed choice for a materially different optional purpose where required.
A saved choice normally concerns the current browser and website origin. Clearing storage, using another browser, or visiting a separate service can require a fresh choice. This does not narrow an account-wide privacy right where law provides one.
A requested appearance preference can be retained while you choose to keep that setting. Authentication and payment-security storage must be limited to their relevant functions. Provider-specific names and durations must be disclosed in the technology details accompanying the applicable choice before optional technologies are enabled.
A browser cookie's lifetime is different from retention of information already received by EBD or a provider. The Privacy Policy explains those retention rules. A 180-day consent record does not set the retention period for invoices, accounts, or newsletters.
5 Browser signals and separate services
EBD must give legally required opt-out preference signals, including Global Privacy Control, the effect required by law, including for associated accounts where applicable. A later interface action must not silently override a legally controlling opt-out signal.
EBD does not assign a separate automated response to legacy Do Not Track signals. Browser settings can delete or block storage, but they do not replace EBD's required consent and opt-out controls.
Third-party checkout, media, and other services can have their own interfaces and privacy controls. EBD remains responsible for the optional services it embeds or triggers. Website consent does not automatically control tracking inside an email or on another service.
6 Contact and updates
Write to Enterprise by Design, LLC, Privacy Requests, 107 Assateague Court, Ocean City, MD 21842, United States. Current online contact options are posted on the Contact page; use the postal address if no suitable option is available.
We will update this policy and the relevant choice information when technologies or purposes change, and obtain a renewed choice where required.