Skip to content
dika.studio
Join the waitlist

Cookie Policy

DIKA DESIGN LTD, a company registered in England and Wales under company number 16251779, registered office 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. Contact: hello@dika.design.

Effective 20 August 2026. Last updated 26 October 2026. We will tell you before a material change takes effect.

This policy lists everything we store in your browser on dika.studio (this website) and app.dika.studio (the Dika Studio application): cookies, local storage and session storage. It is written from what the product actually sets, not from a template.

1. The rules we follow

In the UK, the Privacy and Electronic Communications Regulations (PECR, regulation 6) and the UK GDPR apply. In the European Union, Article 5(3) of the ePrivacy Directive and the GDPR apply. Both say the same thing: anything that is not strictly necessary for the service you asked for may only be stored with your prior, informed consent.

  • Nothing optional is stored until you say yes. Closing or ignoring the banner is not consent.
  • Refusing is as easy as accepting. "Reject all" and "Accept all" are the same size, side by side, on the first screen.
  • Nothing is pre-ticked. Every optional category starts switched off.
  • You can change your mind at any time with Cookie settings in the footer of every page, or Settings > Privacy inside the app. Withdrawing takes one click.
  • Your choice is kept for 180 days. After that we ask again.
  • If your browser sends a Global Privacy Control or Do Not Track signal, our product analytics stays off even if you allowed it.

2. Strictly necessary

These make the site and the app work and keep them secure. They are always on and do not need consent.

  • better-auth.session_token (app.dika.studio, first party). Keeps you signed in. Up to 7 days.
  • better-auth.state, better-auth.two_factor, better-auth.dont_remember (app.dika.studio). Short-lived helpers set only during a sign-in step: protecting a Google sign-in, completing a two-factor check, or remembering that you chose not to stay signed in. Minutes, or until the browser closes.
  • cc_consent (dika.studio and app.dika.studio). Records the cookie choice you made, so both sites respect the same answer. 180 days.
  • cc_cookie_consent (local storage). A copy of the same choice for parts of the product that read it there. Until you clear it.
  • cc-beta. The closed-beta invitation pass. 14 days.
  • cc_pv. Carries a pending email address between sign-up and email verification. 20 minutes.
  • Workspace tab claim (session storage). Stops two open tabs writing into the wrong workspace. Cleared when the tab closes.
  • Session cache (session storage on dika.studio). Remembers for a few minutes whether you are signed in, so the site does not ask the app on every page. Cleared when the tab closes.
  • cc_impersonate. Set only while a member of our support staff acts inside an account with permission, so the notice saying so can be shown. 30 minutes.
  • Cloudflare Turnstile (challenges.cloudflare.com). Protects our contact, sign-in and sign-up forms from automated abuse. It checks signals from your browser to tell a person from a bot and does not track you across sites. Cloudflare may also set a short-lived security cookie such as __cf_bm (30 minutes) when it needs to check that traffic is not automated.

3. Functional

  • Dismissed announcement (local storage on dika.studio). Set only when you close the announcement bar, so it stays closed.
  • sidebar_state (app.dika.studio). Whether the sidebar is open or collapsed. 7 days.
  • Interface preferences (local storage in the app and editor). Panel layouts, editor settings, recently used colours and similar. They stay on your device and are not sent to us.

4. Analytics

  • Our own product analytics (app.dika.studio, first party). Page views and feature use inside the signed-in application, with your IP address, device and, while signed in, your account. Runs only if you allow analytics, never with a Do Not Track or Global Privacy Control signal, and the data stays with us.
  • Third-party analytics: none. This website currently loads no Google Analytics, Microsoft Clarity or any other third-party analytics. If that changes, this policy and the banner will name the provider first, and nothing will load until you allow it.

5. Marketing

  • Referral code (session storage). If you arrive through someone's invite link, the code is held for that tab so sign-up can credit them. Cleared when the tab closes.
  • cc_ref. Keeps that referral for up to 400 days so the person who invited you gets credit if you sign up later. Set only with marketing consent.
  • In-product notices. Whether a notice or promotion inside the app was shown, clicked or dismissed. Only with marketing consent.
  • Advertising trackers: none. We do not use Meta Pixel, TikTok, LinkedIn Insight or any cross-site advertising cookie today.

6. What does not use cookies

Sending the contact form stores your message with us (see the Privacy Policy), not in your browser. Fonts, images and scripts on dika.studio are served from our own domains; we do not embed third-party video players, social widgets or chat scripts on the website.

7. Managing cookies in your browser

You can also delete or block cookies in your browser settings. If you block strictly necessary cookies, signing in will not work. If you delete them, we will simply ask for your choice again.

8. Contact

Questions about this policy: hello@dika.design. You can complain to the UK Information Commissioner's Office at ico.org.uk, or to the data protection authority where you live in the EU.

Cookies on dika.studio

We use necessary cookies to run the site. Everything else is optional and stays off until you allow it. Choose what you allow, or read our cookie policy.