Cookie Policy

Learn how ColabaseAI uses essential, analytics, and marketing cookies, which third-party services may set them, and how to manage your preferences.

2026/05/21

Version: 1.0 · Effective date: 2026-05-21 · Last updated: 2026-05-21

1. About This Policy

This Cookie Policy explains how ColabaseAI ("we", "us", or "our") uses cookies and similar technologies when you visit ColabaseAI (the "Service"). It should be read together with our Privacy Policy and Terms of Service.

The Service is operated by Shanghai Fortune Singularity Tech Co., Ltd., a company registered in Shanghai, China.

2. What Are Cookies

Cookies are small text files placed on your device when you visit a website. They are widely used to make websites work, to improve your experience, and to provide information to website operators. We also use similar technologies (such as local storage and similar browser-based mechanisms) for the same purposes. We refer to all of these collectively as "cookies" in this Policy.

3. Categories of Cookies

We organize the cookies we use into three categories:

3.1 Essential cookies

These are required for the Service to function. They cannot be switched off through our cookie consent banner because the Service cannot operate properly without them.

Typical uses:

  • maintain your sign-in session;
  • remember your basic preferences (such as your selected language and dark mode setting);
  • enable security features and protect against fraud;
  • remember your cookie consent choices.

3.2 Analytics cookies

These help us understand how visitors interact with the Service, so we can improve it. They are loaded only after you give consent through our cookie consent banner.

Typical uses:

  • count visits and traffic sources;
  • measure feature usage and performance;
  • identify errors and slow pages.

Analytics services we may use, where enabled by us in our configuration, include Google Analytics, Microsoft Clarity, Plausible, and Umami. The list of providers actually in use at any given time is published at /legal/subprocessors.

3.3 Marketing cookies

These help us measure the effectiveness of our marketing and support optional engagement features. They are loaded only after you give consent through our cookie consent banner.

Typical uses:

  • attribute conversions to referral or affiliate sources;
  • support optional features like in-page customer chat;
  • support optional product communications.

Marketing-category services we may use, where enabled by us in our configuration, include Crisp (in-page customer chat), Affonso, and PromoteKit. The list of providers actually in use at any given time is published at /legal/subprocessors.

A note on Crisp. Crisp provides our optional in-page customer chat. Because customer chat is an optional support feature rather than a feature required to use the Service, we treat the Crisp script as a Marketing-category script that requires your consent before loading. If you do not accept Marketing cookies, the in-page chat will not be available, but you can still reach support via email at legal@colabase.ai.

4. Third-Party Services

Some cookies are set by third-party service providers, not by us directly. These may include the providers listed at /legal/subprocessors. Each provider is responsible for the cookies it sets on your device, in accordance with its own policies.

You can manage your preferences for Analytics and Marketing cookies through our cookie consent banner, which appears on your first visit and is also available at any time from the Cookie Settings link in our footer.

By default, non-essential cookies are not loaded unless you give consent. You may withdraw your consent at any time through the cookie consent banner. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.

You can also manage cookies directly in your browser settings (for example, blocking cookies or deleting cookies that have already been stored). Please note that if you block essential cookies, certain features of the Service may not work properly.

We will renew our consent request approximately every 12 months, in line with established privacy guidance.

6. Changes to This Policy

We will reflect changes by updating the Effective date at the top of this page and recording a corresponding entry in the Changelog below. For material changes, we will provide reasonable advance notice.

7. Contact

For questions about this Cookie Policy:

Changelog

  • 2026-05-21 · v1.0 — Initial version.