— legal —

Cookie policy.

Last updated: June 1, 2026

This Cookie Policy explains how Drobe ("we", "us", "our") uses cookies and similar tracking technologies on our website at drobe.app (the "Website"). It should be read alongside our Privacy Policy.


1. What are cookies?

Cookies are small text files that are placed on your device (computer, phone, or tablet) when you visit a website. They are widely used to make websites work properly, remember your preferences, and provide information to the site owners. Cookies can be "first-party" (set by the website you are visiting) or "third-party" (set by a service used by the website, such as an analytics provider).

In addition to cookies, we use similar technologies such as pixels (also called web beacons), local storage, and SDKs within our mobile app. In this policy, we refer to all of these collectively as "cookies".


2. How we use cookies.

We use cookies for the following purposes:

2.1 Strictly necessary cookies

These cookies are essential for the Website to function and cannot be switched off. They are usually set in response to actions you take, such as setting your privacy preferences, logging in, or filling in forms. Without these cookies, the Website cannot operate properly.

CookieProviderPurposeDuration
Session IDDrobeMaintains your login session across pagesSession
Cookie consentDrobeStores your cookie consent preferences12 months
CSRF tokenDrobePrevents cross-site request forgery attacksSession

2.2 Analytics cookies

These cookies help us understand how visitors interact with our Website by collecting and reporting information. All data collected is aggregated and therefore anonymous. These cookies help us improve the Website's performance and user experience.

CookieProviderPurposeDuration
_gaGoogle AnalyticsDistinguishes unique users by assigning a randomly generated number as a client identifier. Included in each page request to calculate visitor, session, and campaign data for site analytics.2 years
_ga_*Google AnalyticsUsed by Google Analytics 4 to maintain session state.2 years
_gidGoogle AnalyticsStores and updates a unique value for each page visited. Used to calculate visitor and session data.24 hours
_gatGoogle AnalyticsUsed to throttle the request rate to Google Analytics, limiting data collection on high-traffic sites.1 minute
_clckMicrosoft ClarityPersists the Clarity user ID and preferences. Ensures subsequent visits to the same site are attributed to the same user ID.12 months
_clskMicrosoft ClarityConnects multiple page views by a user into a single Clarity session recording.1 day
CLIDMicrosoft ClarityIdentifies the first time Clarity saw this user on any site using Clarity.12 months
ANONCHKMicrosoft ClarityIndicates whether MUID is transferred to ANID (a cookie used for advertising). Clarity does not use ANID; this is always set to 0.Session
MRMicrosoft ClarityIndicates whether to refresh MUID.7 days
SMMicrosoft ClarityUsed in synchronising the MUID across Microsoft domains.Session

2.3 Functionality cookies

These cookies enable enhanced functionality and personalisation on the Website, such as remembering your preferences and settings.

CookieProviderPurposeDuration
theme_prefDrobeRemembers your light/dark mode preference12 months
localeDrobeRemembers your preferred language/region12 months

2.4 Marketing cookies (future)

We do not currently use marketing or advertising cookies. If we introduce them in the future (such as Meta Pixel / Facebook Pixel for ad campaigns), we will update this policy and request your consent before placing any marketing cookies on your device.


3. Third-party services.

The analytics cookies listed above are set by third-party services. These services process data according to their own privacy policies:

  • Google Analytics: Google Privacy Policy. Google Analytics uses IP anonymisation on our website, meaning your full IP address is never stored by Google.
  • Microsoft Clarity: Microsoft Privacy Statement. Clarity records user sessions (clicks, scrolls, mouse movements) on our Website to help us understand usability. Clarity automatically masks sensitive content (such as form inputs) in recordings.

4. Firebase and mobile app analytics.

Our mobile app uses Firebase (a Google service) for authentication, database, analytics, and crash reporting. Firebase uses device identifiers and instance IDs rather than traditional browser cookies. The data collected is described in our Privacy Policy under "Information collected automatically".

Firebase Analytics data is aggregated and used to understand app usage patterns. Firebase Crashlytics collects crash reports to help us identify and fix bugs.


5. How to manage cookies.

5.1 Cookie consent banner

When you first visit our Website, we display a cookie consent banner that allows you to accept or decline non-essential cookies. You can change your preferences at any time by clicking the "Cookie Settings" link in the footer of any page.

5.2 Browser settings

Most web browsers allow you to control cookies through their settings. You can typically:

  • View what cookies are stored on your device.
  • Delete all or specific cookies.
  • Block all cookies or only third-party cookies.
  • Set your browser to notify you when a cookie is being placed.

Instructions for common browsers:

  • Chrome: Settings → Privacy and Security → Cookies and other site data
  • Safari: Preferences → Privacy → Manage Website Data
  • Firefox: Settings → Privacy & Security → Cookies and Site Data
  • Edge: Settings → Cookies and site permissions → Manage and delete cookies

Please note that blocking essential cookies may prevent parts of the Website from functioning correctly.

5.3 Opt out of analytics

You can opt out of specific analytics services using these tools:

  • Google Analytics: Install the Google Analytics Opt-out Browser Add-on.
  • Microsoft Clarity: You can disable Clarity tracking by blocking third-party cookies from clarity.ms in your browser settings, or by using a content blocker.

5.4 Do Not Track

Some browsers send a "Do Not Track" (DNT) signal with each request. There is no industry standard for how websites should respond to DNT signals. Currently, our Website does not respond to DNT signals, but you can use the opt-out methods described above to control tracking.


6. Data retention.

Cookie data is retained for the duration specified in the tables above. When a cookie expires, the data is automatically deleted from your device. Analytics data collected via cookies is retained in aggregated, anonymised form in our analytics platforms for up to 26 months (Google Analytics) or 13 months (Microsoft Clarity) before being automatically deleted.


7. Changes to this policy.

We may update this Cookie Policy to reflect changes in the cookies we use or for legal, regulatory, or operational reasons. When we make changes, we will update the "Last updated" date at the top of this page. Material changes (such as introducing marketing cookies) will be communicated through our cookie consent banner so you can review and update your preferences.


8. Contact us.

If you have questions about our use of cookies:

For broader privacy questions, please see our Privacy Policy.