Short version: embold.io sets no cookies. There is nothing to accept, nothing to reject and no preference centre, because there is no non-essential storage to govern.
1. The current position
When you load a page on embold.io, the site writes nothing to your device beyond the page, stylesheets, fonts, scripts and images your browser needs in order to display it — all of which are served from embold.io itself and held only in your browser’s ordinary HTTP cache.
Specifically, this site sets:
| Storage mechanism | Used on embold.io? |
|---|---|
| Cookies (first-party) | None |
| Cookies (third-party) | None |
localStorage | None |
sessionStorage | None |
| IndexedDB | None |
| Cache Storage API | None |
| Analytics tags | None |
| Advertising or retargeting tags | None |
| Tag manager (e.g. Google Tag Manager) | None |
| Third-party hosts contacted on page load | None |
2. Why there is no consent banner
Article 5(3) of the ePrivacy Directive requires consent before storing information on, or gaining access to information already stored on, a user’s device — unless that storage is strictly necessary to deliver a service the user asked for. This site stores nothing at all, so the obligation is not engaged and asking you for consent would be asking about nothing.
A banner that appears where no storage occurs is noise, not compliance. If that position ever changes, the banner arrives with the change, not after it — see section 4.
3. The BrowserStack notice bar
The bar at the top of each page announcing that Embold is now part of BrowserStack has a dismiss button. Dismissing it hides it for the rest of that page view only; the choice is not stored, so the bar returns on the next page you open. We would rather show it again than write a cookie to remember that you closed it.
4. How this page stays true
Statements like the ones above go stale the moment someone adds a marketing tag. To prevent that, embold.io is covered by an automated scan that loads the site and reports any cookie, browser-storage key or third-party host that was not there before.
Adding analytics, advertising or any other non-essential storage to this site requires a consent mechanism to be deployed in the same change — not retrofitted afterwards — and this page to be updated to describe what is set, by whom and for how long.
5. Cookies elsewhere
Other sites behave differently and publish their own notices:
- browserstack.com cookie policy — for the BrowserStack platform and marketing site.
- docs.embold.io — the Embold documentation site.
- Your own Embold Enterprise deployment, which runs on your infrastructure under your control.
6. Controlling cookies in your browser
Nothing here needs blocking, but every major browser lets you view and delete cookies and site data, and block them by site: Firefox, Chrome, Safari and Edge all expose this under privacy or site-settings. Blocking storage for embold.io has no effect on how this site works, because it uses none.
7. Questions
Write to compliance@browserstack.com. Our privacy policy covers the rest of how this site handles personal data.