Skip to content

Legal

Cookie Policy

Browser storage and cookies used on Umikflow: sign-in session tokens, Google Analytics, and Google AdSense advertising cookies.

Last updated 09 October 2026

This page lists the cookies and browser storage this site and the billing workspace use: session tokens for signing in, Google Analytics for usage measurement, and Google AdSense cookies when advertising is enabled on public marketing pages.

For the wider picture of what data we hold, see the privacy policy.

1.Cookies and browser storage

A cookie is a small file a website asks your browser to keep, so it can be read again on a later request. Browsers also provide local storage, which works similarly but is read by the page itself rather than sent with every request.

Umikflow uses both for essential authentication, website usage measurement via Google Analytics, and advertising cookies via Google AdSense when ads are active.

2.Authentication (strictly necessary)

When you sign in, Supabase Auth stores a session token in your browser's local storage. Without it you would be signed out on every page load, so it cannot be turned off while using the workspace.

  • What it holds — a session token and a refresh token issued by Supabase for your account.
  • How long — until the session expires or you sign out, which clears it.
  • Who reads it — the Umikflow application and Supabase. Nobody else.

This is not an advertising identifier and is not used to track you across other websites.

3.Analytics

The site loads Google Analytics 4 (measurement ID G-CVS0ZBGYSR), which sets cookies in order to count visits and understand which pages people read and how they arrived.

  • Typical cookies — _ga and an identifier of the form _ga_<container>, set by Google and generally lasting up to two years.
  • What Google receives — page paths, referrer, approximate location derived from IP address, and device and browser characteristics.
  • What we use it for — deciding which pages are worth improving. We do not build advertising audiences from it.

Google processes this data under its own terms. You can prevent it by blocking cookies for this site in your browser, using a content blocker, or installing Google's opt-out browser add-on. Blocking analytics does not affect the workspace.

4.Advertising cookies (Google AdSense)

When Google AdSense is enabled on public marketing pages, Google and its partner ad networks may place cookies, web beacons, or read device identifiers in your browser. These cookies enable Google and its partners to serve ads based on your visit to this site and/or other sites on the Internet, and to measure ad performance.

  • Personalized advertising— Google uses cookies to serve ads based on a user's prior visits to this website or other websites.
  • Opting out — You can opt out of personalized advertising by visiting Google Ads Settings. Alternatively, you can opt out of third-party vendors' use of cookies for personalized advertising by visiting aboutads.info.

5.What we do not use

Aside from the essential sign-in tokens, Google Analytics measurement, and Google AdSense ad serving described above, this site does not run:

  • Social media tracking pixels (e.g. Meta pixel, LinkedIn insight tag).
  • Session recording, screen capture, or mouse-tracking heatmaps.
  • Third-party invasive live chat or support widgets.

6.Managing cookies

Every major browser lets you view and delete cookies and block them for particular sites, usually under privacy or site settings. Most also offer a “do not track” signal and a private browsing mode that discards storage when you close the window.

Blocking analytics cookies leaves the whole site working normally. Blocking storage for the workspace will sign you out and keep you signed out, since the session token has nowhere to live.

7.Changes and contact

If we add or remove anything that sets a cookie, we will update this page and the date at the top. Questions go to support@umikflow.com or through the contact page.