Skip to main content

Updated: 2026-09-22

Cookie Policy

Effective: 2026-09-22

This Cookie Policy explains how QingBo uses cookies and similar browser technologies when you visit our public site or use a browser-based QingBo service. It should be read together with our Privacy Policy.

You do not need to wait for every production integration to read this policy: the inventory below describes what the current site actually stores. We will review it again when production domains, identity, payment, security, analytics, and other service providers are finalised.

Read the Privacy Policy

1. What cookies and similar technologies are

A cookie is a small text value that a website asks a browser to store and return. Similar technologies include local storage, which lets a browser retain values for a site without automatically sending them with every network request, and scripts that read information from the browser, such as screen size or language, and send it to a server for measurement.

These technologies may be session-based or persistent. A session value usually ends when the browser session ends. A persistent value remains until its stated period ends, the site replaces or removes it, or you clear browser data.

2. How we use them

We use necessary technologies to remember privacy choices, support account and authorisation state, protect the Services, and operate requested features. If you remove these values, you may be signed out, your privacy choices may need to be set again, or part of a service may stop working.

We distinguish necessary technologies, cookieless audience measurement, and optional analytics and marketing technologies. Cookieless audience measurement produces aggregated statistics without setting cookies or storing anything in your browser, and is described in section 4. Optional categories remain off unless a corresponding tool is configured and your recorded choice permits its use, including consent where required by law.

3. Current cookie and browser-storage inventory

The table lists the first-party cookie and persistent browser storage keys deliberately used by the current public-site and account interface code, together with the one local-storage key that our cookieless measurement script reads. Temporary in-memory values and development-only tooling are not included.

SourceTechnologyNameDurationCategoryPurpose
QingBo public siteFirst-party cookieqingbo_privacy_preferences1 yearNecessary · privacy choiceRecords whether analytics and marketing categories are allowed so the site can respect your choice.
QingBo public siteLocal storageqingbo:privacy-preferences:v1Until changed or browser site data is clearedNecessary · privacy choiceRestores the privacy choices shown in the footer control on this browser.
QingBo account interfaceLocal storageqingbo_v2_auth_tokenUntil sign-out, replacement, or browser site data is clearedNecessary · accountKeeps an authenticated browser session available to the QingBo interface.
QingBo account interfaceLocal storageqingbo_v2_refresh_tokenUntil sign-out, replacement, or browser site data is clearedNecessary · accountAllows the account interface to renew an authenticated session when supported by the identity flow.
QingBo account interfaceLocal storageqingbo_v2_user_idUntil sign-out, replacement, or browser site data is clearedNecessary · accountAssociates the browser account state with the signed-in user identifier.
QingBo-operated analytics serverMeasurement script · reads local storageumami.disabledNever written by QingBo sites; read only if presentCookieless audience measurementRead by the self-hosted Umami measurement script to check whether measurement has been switched off in this browser. If the key is present, the script sends no measurements. The script itself sets no cookies and writes nothing to browser storage.

4. Cookieless audience measurement

QingBo websites, namely qingbo.ai, wave.qingbo.ai (WaveAPI), chat.qingbo.ai (WaveChat), help.qingbo.ai, and academy.qingbo.ai, use Umami, an open-source audience-measurement tool that QingBo hosts itself. The script is loaded from, and reports to, an analytics server operated by QingBo; nothing is sent to the company that develops Umami or to any other third party. It sets no cookies and writes nothing to browser storage. The only browser value it reads is the umami.disabled key listed above.

For each page view or measured event, it records a cleaned page address, the origin and path of a referring site, the page title, screen size, browser language, browser, operating system and device type, the country, region, and city derived from the IP address, and page-performance measurements. Cleaning removes the part of the address after “#”, removes query parameters other than the campaign parameters utm_source, utm_medium, utm_campaign, utm_term, and utm_content, and replaces identifier-like path segments, such as conversation, order, or organisation IDs, with “:id”. The IP address itself is not stored.

Visits are counted with an identifier that the analytics server calculates as a one-way hash of the site, the IP address, the browser’s User-Agent, and a salt that changes every calendar month. It cannot be turned back into an IP address and cannot link your visits across months or across sites. The measurement is used only for aggregated statistics about visits and site performance. It is not used for advertising or profiling, is not combined with account data, and does not receive user IDs, email addresses, or other account identifiers. Raw events are kept only for as long as they are needed for these aggregated statistics, and the Privacy Policy section on how long we keep information applies. The Privacy Policy explains the legal basis and your rights.

Because this measurement sets no cookies and is designed not to identify you, it is not controlled by the Analytics switch in “Your privacy choices”. If your browser sends a Global Privacy Control or Do Not Track signal, the Umami measurement script is not loaded at all.

QingBo websites are also served through Cloudflare, our CDN and network-security provider, and Cloudflare Web Analytics is enabled for the qingbo.ai domain. Cloudflare inserts a small measurement script (its “beacon”, loaded from static.cloudflareinsights.com) into the HTML of the pages it serves for qingbo.ai and its subdomains. The script is not part of QingBo’s own code; Cloudflare adds it at its network edge. According to Cloudflare’s documentation, it collects page-load timings and Core Web Vitals from the browser’s Performance API, together with the current page path, landing page, referring page, and browser and device type. It sets no cookies, writes nothing to local storage, session storage, or IndexedDB, and does not fingerprint visitors by IP address or User-Agent, which is why it has no row in the inventory above.

Cloudflare, Inc. processes this information as our service provider under its own privacy policy (https://www.cloudflare.com/privacypolicy/). Cloudflare states that it discards the IP address at the data centre that receives the measurements, which is the one nearest to you and may be outside your country or region. We receive only aggregated statistics about how our pages load and perform. Cloudflare’s documentation does not state a fixed retention period, so retention is governed by Cloudflare’s own policies. Unlike our Umami measurement, this script does not respond to Global Privacy Control or Do Not Track signals; section 7 explains how to block it. The Privacy Policy explains the legal basis and your rights.

5. Optional analytics and marketing categories

The optional Analytics category covers third-party analytics tools, such as Google Analytics, that use cookies to measure visits, feature use, and performance. Marketing technologies can help measure communications or campaigns across sites. The current site does not run a tool in either category, even if you choose to allow it in the privacy control.

No such cookie-based tool is configured today. The cookieless measurement described in section 4, our own Umami statistics and the Cloudflare Web Analytics script, is not in either category and is not controlled by the privacy control. If we enable a cookie-based tool, such as Google Analytics, it will load only after you switch on Analytics in “Your privacy choices”; it will not load on signed-in console or sign-in pages, or when your browser sends Global Privacy Control or Do Not Track; and it will stop when you switch Analytics off. Before enabling a tool in either category, we will identify the provider and its cookies here, state their purpose and duration, and apply the recorded choice and any consent required by law. Enabling a preference alone does not install a provider that has not been configured.

6. Third-party sites and services

A QingBo page may direct you to a separate identity provider, product, payment service, model provider, or other third-party domain. That domain may use its own cookies or storage under its own notice. Values set only on another domain are not included in the first-party inventory above.

The Cloudflare Web Analytics script that our CDN provider inserts into QingBo pages is described in section 4. Before production launch, we will review the final public, identity, payment, and product domains and add any technologies for which QingBo is responsible. Links to another service do not mean that its cookies are active on the QingBo public site.

7. Manage your choices

Use “Your privacy choices” in the footer to review or change the optional analytics and marketing categories. The choice is stored for this browser and may need to be made again on another browser, device, profile, or after site data is cleared.

The footer control does not switch off cookieless measurement. To stop our Umami measurement, turn on Global Privacy Control or Do Not Track in your browser or a privacy extension; the Umami script will then not load on QingBo websites. Those signals do not stop the Cloudflare Web Analytics script, which Cloudflare inserts at its network edge; to block it, use a browser content blocker or privacy extension, or block requests to static.cloudflareinsights.com. Clearing cookies or site data does not stop either of them, because they store nothing in your browser.

You can also block or remove cookies and local storage using browser settings. Necessary technologies cannot be disabled through the site control because they are used to remember that control or provide requested account and security functions. Removing them through the browser may affect how the Services work.

8. Updates and contact

We may update this policy when our products, domains, providers, technologies, or legal obligations change. The current version and effective date will appear on this page. Where required, we will provide additional notice or request consent before a materially different optional use begins.

For questions about this inventory or the way a browser technology is used, email contact@qingbo.ai. For broader information about personal-information processing and your rights, read the Privacy Policy.

Privacy PolicyTerms of Service