Cookie Policy
Last updated: 7 August 2026
This policy explains the cookies and browser storage Kyte uses. The short version: we store what is needed to keep you signed in and to remember your preferences, and we do not use advertising cookies.
1. What we use, and what we do not
Kyte is a business application, not an advertising-funded website. We use only the browser storage needed to sign you in and remember your preferences.
We do not use third-party advertising cookies. We do not run ad-network tags, cross-site tracking pixels, or data brokers on the application, and we do not sell or share your browsing data for advertising.
Because the storage we set is either strictly necessary to deliver a service you requested or stores a preference you chose, we do not show a consent banner for it. Strictly necessary storage cannot be switched off without breaking sign-in.
3. Browser storage
In addition to cookies, we use your browser’s local storage. It works like a cookie but is not transmitted with every request. We use it for your session tokens and for small interface preferences.
| Key | Purpose | Category |
|---|---|---|
auth_access_token, auth_refresh_token | Authenticates your API requests and renews your session without forcing you to sign in again. | Strictly necessary |
theme | Remembers your light or dark mode preference. | Preference |
Interface preferences | Remembers small layout choices such as table column widths, workflow builder panel state, and recently used items. | Preference |
4. Analytics and workspace-configured tracking
We use aggregate product analytics and error monitoring to keep the Service working and to understand which features are used. This is limited to operating the platform — it is not used to build advertising profiles.
Tracking configured by a workspace
Workspaces can enable their own tracking on their own properties — for example tracked links, a chat widget on their website, or a marketing pixel they configure. Where a workspace does this:
- the workspace owner is the controller of that data and is responsible for their own cookie notice and for collecting any consent required;
- any cookies set on their website are governed by that website’s cookie policy, not this one;
- our chat widget sets a first-party identifier on their site so a visitor’s conversation persists across page loads.
5. Third-party cookies from integrations
Some features hand you off to a third party who sets their own cookies under their own policy. This happens when you pay through Stripe’s checkout, or when you sign in or connect a channel through a provider such as Google, Meta or Telegram. We do not control those cookies. Review the relevant provider’s policy for details.
6. How to control or clear this data
You can clear or block cookies and site data at any time in your browser settings, usually under Privacy or Site settings. Most browsers let you clear data for a single site, and offer a private browsing mode that discards it when you close the window.
Clearing this data signs you out of Kyte and resets your interface preferences. If you block cookies for our domain entirely, sign-in will not work.
Signing out clears your session tokens. Browsers also honour “Do Not Track” and similar signals inconsistently across the industry; because we do not perform cross-site advertising tracking, these signals do not change what we store.
7. Changes and contact
We will update this policy if the storage we use changes. The “Last updated” date at the top of this page always reflects the current version.
Questions about this policy can be sent to privacy@flowtracker.io. For a fuller description of how we handle personal data, see our Privacy Policy; for the terms governing the Service, see our Terms of Service.