Skip to content

Legal

Cookie Policy

Exactly what Umikflow stores in your browser and why. There are two things: a sign-in token and Google Analytics.

Last updated 11 September 2026

This page lists the cookies and browser storage this site and the billing workspace actually use. It is short because there is not much: one thing that keeps you signed in, and one analytics tool.

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 two purposes only: keeping you signed in, and measuring how the public website is used.

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-F6M0BMXRT3), 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.What we do not use

To be specific, because “we value your privacy” banners rarely are, this site does not run:

  • Advertising networks or ad cookies of any kind.
  • Retargeting or conversion pixels — no Meta pixel, no LinkedIn insight tag, no Google Ads remarketing tag.
  • Session recording, heatmapping or mouse-tracking tools.
  • Third-party live chat or support widgets.
  • Social media embeds that set cookies.
  • Cross-site tracking of any kind.

There is no advertising on this site today. If that ever changes, this page and the privacy policy will be updated before it does, not afterwards.

5.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.

6.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.