Audimind Cookie Policy

Last Updated: September 7, 2026

Effective Date: September 7, 2026

This Cookie Policy explains how Shenzhen Audimind Technology Co., Ltd. ("Audimind," "we," "us," or "our") uses cookies and similar technologies on the Audimind websites, web applications, and related online services that link to this Policy (collectively, the "Services"). It should be read together with our Privacy Policy.

This Policy does not control cookies placed on websites or checkout pages operated independently by third parties. Where an eligible Audimind software purchase is processed by a third-party payment processor or merchant of record identified at or before checkout (the "Payment Provider"), that Payment Provider controls the technologies used on its own checkout and buyer-support pages. Those technologies are governed by the Payment Provider's privacy and cookie notices.

1. What cookies and similar technologies are

Cookies are small text files stored on a browser or device. We may also use local storage, software development kits, pixels, tags, and comparable technologies. In this Policy, "cookies" includes these technologies where appropriate.

Cookies may be:

  • Session cookies, which expire when the browser session ends;
  • Persistent cookies, which remain until their configured expiry date or deletion;
  • First-party cookies, set by Audimind; or
  • Third-party cookies, set by another service integrated with the Services.

2. How we use cookies

The cookies actually available on a particular Audimind page depend on the page, feature, region, and current production configuration. The Cookie Settings interface, where presented, is the current operational inventory for that page. We do not treat a generic example in this Policy as proof that a particular vendor or cookie is active.

2.1 Strictly necessary cookies

These cookies support functions needed to provide a service requested by the user or to protect the Services. They may be used to:

  • keep users signed in and maintain sessions;
  • authenticate requests and prevent cross-site request forgery;
  • remember security, language, or consent choices;
  • route traffic and maintain service availability;
  • detect fraud, abuse, and unauthorized access; and
  • support checkout handoff and transaction status.

Because these cookies are necessary for the requested service, they generally cannot be disabled through our consent interface. Users can block them in browser settings, but doing so may cause parts of the Services to stop working.

2.2 Functional cookies

Where enabled, functional cookies remember optional preferences or provide enhanced functions, such as interface settings or an optional integration. When applicable law requires consent, we do not activate non-essential functional cookies before obtaining it.

2.3 Analytics cookies

Where enabled, analytics cookies help us understand aggregated use of the Services, diagnose performance issues, and improve product flows. When applicable law requires consent, analytics cookies remain disabled until consent is given.

We configure analytics tools, where reasonably available, to reduce unnecessary collection and do not use analytics cookies to train AI systems on private Project content or analyze the semantic content of private Projects.

2.4 Advertising or cross-context behavioral cookies

Audimind does not use advertising or cross-context behavioral cookies by default. If we introduce them, we will update the Cookie Settings interface and obtain consent where required before activation. We do not sell personal information through cookies.

3. Third-party services

Some features may direct a browser to or embed functionality from another provider. Depending on the feature used, third parties may include:

  • the applicable Payment Provider, where it processes the transaction, for checkout, tax, payment, invoicing, and buyer support;
  • an identity or sign-in provider selected by the user;
  • infrastructure, security, content-delivery, or error-monitoring providers; and
  • optional integrations expressly enabled by the user or workspace administrator.

Third parties process data under their own privacy and cookie notices when they independently determine the purposes and means of processing. Their cookies are not converted into Audimind Credits and do not make Audimind a payment facilitator or marketplace.

4. Your choices

4.1 Cookie Settings

Where a consent interface is available, users can accept, reject, or later change optional cookie categories through Cookie Settings. Withdrawing consent does not affect processing that was lawful before withdrawal.

4.2 Browser and device controls

Most browsers allow users to view, delete, or block cookies. Browser controls may need to be configured on every browser and device. Blocking all cookies may prevent authentication, saved settings, checkout status, and other requested functions from operating correctly.

4.3 Global privacy signals

Where applicable law requires recognition of a supported browser-based opt-out signal, such as Global Privacy Control, we process the signal for the relevant browser and purpose. Because Audimind does not use advertising or cross-context behavioral cookies by default, a signal may not change the visible experience.

4.4 Mobile applications

If an Audimind mobile application uses device identifiers or similar technologies, choices may also be available in the operating-system privacy settings. We will provide a feature-specific notice if required.

5. Cookie duration

Cookie duration is limited according to purpose and configuration:

  • security and session cookies generally last for the session or the period reasonably necessary to maintain account security;
  • preference and consent records last long enough to remember the user's selection and demonstrate compliance;
  • optional analytics cookies, if used, follow the duration displayed in Cookie Settings or the applicable vendor configuration; and
  • a cookie may be deleted earlier by the user or changed when we update the Services.

We periodically review active cookies and remove or shorten cookies that are no longer reasonably necessary. The production cookie scanner and consent configuration should be treated as the source of truth for exact names, providers, purposes, and durations.

6. International data transfers

Cookie-derived information may be processed in countries other than the user's own. Where required, we use appropriate safeguards for international transfers as described in the Privacy Policy.

7. Updates to this Policy

We may update this Policy when technologies, vendors, legal requirements, or the Services change. We will post the revised version with a new "Last updated" date and provide additional notice where required by law. A material change to optional cookies will also be reflected in Cookie Settings before the affected cookie is activated where consent is required.

8. Contact

Questions about cookies or privacy may be sent to: