Cookie Policy
Last updated: 2 July 2026
This Cookie Policy explains how Robust Devs Ltd (“Robust Devs”, “we”, “us”) uses cookies and similar technologies when you visit robustdevs.co. It sits alongside, and should be read with, our Privacy Policy, which describes how we handle personal data more broadly.
1. What cookies are
A cookie is a small text file that a website stores on your device when you visit. Cookies let a site remember your actions and preferences over time. “Similar technologies,” such as pixels, local storage, and software development kits (SDKs), do comparable jobs, and we treat them the same way in this policy. Cookies are either first-party (set by robustdevs.co) or third-party (set by a service we embed, such as an analytics provider).
2. Why we use cookies
We keep cookie use lean and purposeful. As a Next.js marketing site for a B2B engineering studio, we are not an ad-tech business and we do not sell your data. We use cookies to keep the site secure and working, to understand, in aggregate, how the site and our free tools are used so we can improve them, and, where you allow it, to measure whether our campaigns reach the right audience.
3. Categories of cookies we use
Every cookie on this site falls into one of three categories. Only the first is set automatically; the other two require your consent.
Strictly necessary (essential)
Always on- Purpose
- Make the site work. These keep the page secure, remember your cookie choices, balance server load, and let core features like the contact form and our free tools function.
- Legal basis
- Set without consent; PECR allows cookies that are strictly necessary to deliver a service you have actively requested. Cannot be switched off.
- Typical examples
- Cookie-consent preference, CSRF/security tokens, session and load-balancing cookies, and the state behind interactive tools like the Cost Estimator and Vibe Code Scanner.
Analytics & performance
Consent required- Purpose
- Help us understand how visitors find and use the site (which pages get read, where people drop off, and whether the site is fast and error-free) so we can improve it. Data is used in aggregate.
- Legal basis
- Consent. These are only set after you opt in through the consent banner, and you can withdraw consent at any time.
- Typical examples
- Aggregate page-view and traffic-source measurement, and product-analytics events for our free tools. We configure analytics for IP truncation / anonymisation where the provider supports it.
Marketing & advertising
Consent required- Purpose
- Measure whether our campaigns reach the right funded founders and CTOs, attribute enquiries to the channels that drove them, and, where enabled, support remarketing. As a B2B engineering studio we keep this category deliberately light.
- Legal basis
- Consent. Off by default and only set after you opt in. You can withdraw consent at any time.
- Typical examples
- Conversion / attribution tags for paid channels and, if enabled, remarketing pixels. These may be set by third parties named in the inventory table below.
4. Detailed cookie inventory
The table below lists the specific cookies and similar technologies in use, with their category, provider, purpose, and how long each one lasts.
| Cookie / technology | Category | Provider | Purpose | Retention |
|---|---|---|---|---|
| [PLACEHOLDER: cookie name] | Strictly necessary | First party (robustdevs.co) | [PLACEHOLDER: e.g. stores your cookie-consent choice] | [PLACEHOLDER: e.g. 12 months] |
| [PLACEHOLDER: cookie name] | Analytics & performance | [PLACEHOLDER: analytics vendor] | [PLACEHOLDER: e.g. aggregate usage measurement] | [PLACEHOLDER: expiry] |
| [PLACEHOLDER: pixel / tag] | Marketing & advertising | [PLACEHOLDER: ad platform] | [PLACEHOLDER: e.g. campaign attribution] | [PLACEHOLDER: expiry] |
This inventory is being finalised from a full scan of the live site. Until then, the rows above are placeholders; the authoritative, up-to-date list is always the one shown in our consent-preferences panel.
5. Managing your consent
When you first arrive, a consent banner lets you accept or reject non-essential cookies. Essential cookies load either way because the site cannot function without them. You can change your choice at any time by reopening the consent-preferences panel (via the “Cookie settings” control managed by our consent tool, [PLACEHOLDER: consent-tool vendor]). Withdrawing consent stops the relevant cookies from being set going forward; it does not delete cookies already stored, which you can clear in your browser.
6. Controlling cookies in your browser
Independently of our banner, every major browser lets you view, block, or delete cookies and clear local storage from its settings. Blocking all cookies is fine for reading the site, but may break interactive features, for example, our free tools that rely on essential cookies to hold their state. Many browsers also offer a “Do Not Track” or Global Privacy Control signal; where technically feasible we aim to honour a recognised opt-out preference signal.
7. Third-party cookies
Some cookies are set by third-party services we rely on: for example, our analytics provider or the platforms behind any paid campaigns. Those providers act as independent controllers or as our processors for the data they collect, under their own privacy notices. The relevant providers are identified in the inventory table in section 4 once the audit is complete.
8. Changes to this policy
We may update this Cookie Policy as the site, our tools, or the law change. When we do, we will revise the “Last updated” date at the top of this page. Material changes to non-essential cookie use will be reflected in the consent banner so you can review your choices.
9. Contact us
Questions about this policy or how we use cookies? Email us at hi@robustdevs.co or reach out through our contact page. Robust Devs Ltd is registered in England & Wales.