Cookie Policy

Cookies are small text files placed on your device when you visit a website. Similar technologies can also include pixels, scripts, local storage, tags, and other technologies used to store or access information on your device. ICO guidance makes clear that the rules do not apply only to traditional browser cookies, but also to similar storage and access technologies more broadly.

We use cookies and similar technologies to:

• make the website work properly;
• keep users signed in and secure;
• remember settings and preferences;
• measure website performance and usage;
• improve our services and user experience; and
• carry Google’s advertising signals, if you allow the marketing category.

Some cookies are strictly necessary for the site to function. Other cookies, including many analytics, advertising, and tracking technologies, may require your consent before they are used. ICO guidance states that consent is generally required unless an exemption applies, such as the communication exemption or the strictly necessary exemption.

Strictly necessary storage

This category keeps you signed in, keeps the site secure, and remembers the choice you make about the other categories. It cannot be switched off. ICO guidance confirms that certain technologies may fall within exemptions where they are strictly necessary or used for communication purposes.

On devdome.com, DevDome’s own code sets exactly one cookie, after you sign in, and keeps two values in your browser’s local storage, which never travels with a request:

• sb-<project>-auth-token (first party, local storage): your signed-in session, so you are not logged out on every page. Written only after you sign in, removed when you sign out or clear site data.
• dd_bi (first party, cookie, HttpOnly): a random identifier set when you sign in, so your account’s Security page can tell this browser apart from your other devices and sign one of them out. It is never derived from your IP address or browser details, grants no access on its own, and only its hash is stored on our side.
• devdome_consent (first party, local storage): the answer you gave on the banner or on the cookie settings page, so we do not ask again. Written only when you answer, kept until you clear it or we publish a new version of these categories.

Cloudflare hosts this site and runs the Turnstile challenge on our forms. Cloudflare’s edge can set its own security cookies on requests it inspects or challenges. Those are set by Cloudflare under its own policy, we do not read them, and we do not list names here that we cannot verify from our own code.

Functional

This category is offered in the banner for choices that are neither necessary nor analytics. Today nothing on devdome.com is loaded or stored because of it: allowing or refusing it changes nothing. We list it so the banner and this page agree, and we will describe what it covers here before anything starts using it.

Separately, once you are signed in, the dashboard remembers your own view settings (the site you last opened, which columns are shown, table density) in local storage. That is part of the product you signed in to use, it is first party, and it is never written on public pages.

Analytics

This category helps us understand how visitors use DevDome: which pages are visited, how people move through the site, and what content performs best.

Depending on how they are configured and used, analytics technologies may require consent. We will handle them in line with applicable UK rules and our consent settings. ICO guidance states that consent is needed for non-exempt storage and access technologies, and that PECR consent rules take priority where they apply.

The analytics category controls Google Analytics, which does not load until you allow the category. Our own measurement is listed here too, because it is analytics, but it is not switched by this choice: it runs on every visit and stores nothing on your device.

• Google Analytics 4 (Google): usage measurement. This is the only thing on the site that sets true cookies, and only after you allow this category. It sets _ga and _ga_<measurement id>, which Google uses to tell one browser from another and documents as lasting up to two years. They are Google’s cookies, on Google’s terms; ad-related signals inside the same tag are additionally controlled by the marketing category.
• DevDome Analytics (first party): our own traffic measurement, on every visit. On devdome.com it runs in cookieless mode, so it stores nothing on your device: no cookie, no localStorage. Visitors are counted using a temporary identifier our server derives from the request, which changes every day and differs per site; it is not stored on your device. If you arrive from a campaign link, the UTM tags are kept in session storage for that tab and one visit ping is sent, so a signup you submit can be attributed; nothing is written beyond that session. It builds no cross-site profiles and shares nothing with advertisers.

Marketing

This category controls one thing: Google’s advertising signals inside the Google Analytics tag described above (ad storage, ad user data, ad personalisation). They stay denied unless you allow this category.

Because those signals live inside that tag, allowing marketing on its own has no effect: if you have not also allowed analytics, the tag never loads and nothing is set. No advertising network, retargeting pixel, or affiliate tracker is loaded from this site.

ICO guidance states that online advertising technologies generally require consent.

We may use third-party services that place cookies or use similar technologies through our website, including services related to:

• analytics;
• authentication;
• email and newsletter services;
• fraud and bot protection;
• embedded content;
• performance monitoring; and
• advertising or campaign measurement.

Two of them can store or read something through this website: Cloudflare and Google Analytics. Cloudflare hosts the site and runs the Turnstile challenge on our forms; Google’s analytics tag loads only if you allow the analytics category.

The others do not set anything through these pages, but they do process data for us: Supabase, Hetzner, DigitalOcean, 2Checkout (Verifone), Resend. That is the same list as on our Trust page, and what each one receives is set out in the Privacy Policy.

Where required, we will ask for your consent before enabling non-essential third-party cookies or similar technologies.

When you first visit DevDome, you may see a cookie banner or consent tool that allows you to accept, reject, or manage non-essential cookies.

Under ICO guidance, non-exempt cookies and similar technologies should not be set before valid consent is obtained. Users must also be given clear and comprehensive information and an easy way to make choices.

You can change your answer at any time through:

• our Cookie Settings page, which shows every category and saves the change immediately;
• your browser settings; and
• third-party opt-out tools, where relevant.

Refusing or withdrawing a category takes effect on your next page view: a script that has already loaded on the page you are reading stays loaded until you navigate.

Please note that disabling strictly necessary cookies may affect site functionality.

• devdome_consent: no expiry date. It stays until you clear site data or we publish a new version of the categories, at which point you are asked again.
• sb-<project>-auth-token: until you sign out, your session expires, or you clear site data.
• dd_bi: about one year, or until you clear site data.
• _ga and _ga_<measurement id>: Google documents a lifetime of up to two years. Google sets them, so Google decides.
• Anything Cloudflare’s edge sets: under Cloudflare’s own policy, not ours.

Clearing your browser storage for this site removes the first two immediately. That also clears your saved answer, so you will be asked about cookies again on your next visit.

Some third-party providers we use may process data outside the UK. Where personal data is involved, we take steps intended to ensure that transfers are handled in accordance with applicable data protection laws.

For more information on how we handle personal data, please see our Privacy Policy.

We may update this Cookie Policy from time to time to reflect legal, technical, or business changes. The latest version will always be posted on this page with the updated effective date.

If you have questions about this Cookie Policy, please reach out via our Contact Page.

DevDome is operated from Kondrashina 17, Odesa, 65021, Ukraine. You can reach us at support@devdome.com.