Last updated and verified: July 26, 2026.
Independent website notice: MiniMax-AI.chat is independent from MiniMax. This policy describes technologies used by this website and its verified providers; it does not govern cookies on official MiniMax services.
This Cookie Policy should be read with the Privacy & Data Use Notice. Cookie behavior can vary by visitor location, browser, consent choice, provider configuration, security event, and the advertising vendors displayed in Google’s consent interface.
Verified configuration
- Google AdSense is active.
- A Google Privacy & messaging European regulations message for MiniMax-AI.chat is published and enabled in English and additional languages.
- Cloudflare and Cloudflare Web Analytics are active.
- No active Google Analytics or Google Tag Manager tag was detected.
- GSC Terminal Tracker is installed but inactive and is not described as an active tracker.
- The demo’s recent conversation context uses browser memory during the open page session; no demo use of persistent localStorage, sessionStorage, or a first-party chat cookie was verified.
- Contact Form 7 is active, but no Flamingo message-storage plugin was active in the verified WordPress configuration.
What cookies and similar technologies are
Cookies are small values stored through a browser. Similar technologies include local storage, consent strings, pixels, tags, beacons, advertising identifiers, and browser-session memory. They can support page delivery, security, preferences, consent, advertising, fraud prevention, measurement, and performance reporting.
Technology categories
| Category | Purpose | Choice |
|---|---|---|
| Necessary delivery and security | Route traffic, deliver pages, apply security challenges or rate limits, protect login routes, and reduce attacks or abuse. | Some functions are necessary for the requested service. Blocking them can prevent pages or security checks from working. |
| Consent and preferences | Display privacy choices, record or communicate consent, and honor vendor and purpose selections. | Use the displayed Google privacy settings or browser controls. |
| Advertising | Deliver, limit, secure, personalize where permitted, and measure Google advertisements. | Consent is requested where required. Available options depend on location and the published message. |
| Performance measurement | Collect page-performance and aggregate usage metrics through Cloudflare Web Analytics. | Cloudflare documents Web Analytics as privacy-oriented and not tracking individual users across customer properties. Applicable consent requirements can still depend on law and configuration. |
| Session function | Keep a limited recent conversation context available while the demo page session remains open. | Reload, clear, or close the page to remove the visible session context. This does not delete provider-held records. |
Provider-documented cookie examples
The following table is a transparent inventory of documented examples relevant to the active providers. It is not a claim that every named cookie appears on every visit. Conditional cookies appear only when the corresponding provider feature, location, consent choice, browser state, or security event applies.
| Name or technology | Provider | Purpose | Documented or configuration-based lifetime | Status boundary |
|---|---|---|---|---|
| Google CMP consent record or TCF consent string | Google Privacy & messaging | Stores or communicates European-regulations consent information. | Controlled by Google’s current CMP implementation and configuration; no fixed site-controlled duration is claimed. | The exact browser key was not independently verified and is therefore not invented here. |
_gads | Google advertising | Supports Google advertising on third-party sites. | Google documents 13 months. | May appear depending on consent, region, browser, and advertising configuration. |
IDE or id | Google / DoubleClick | Advertising delivery, preferences, personalization where allowed, and measurement. | Google documents 13 months in the EEA, UK, and Switzerland and 24 months elsewhere. | Third-party and conditional; not guaranteed on every visit. |
DSID | Supports signed-in advertising preference handling on non-Google sites. | Google documents 2 weeks. | Conditional on Google account and advertising context. | |
NID | Stores preferences and can support advertising on Google services. | Google documents 6 months after last use. | Conditional; may relate to interaction with Google-controlled services. | |
__cf_bm | Cloudflare | Bot detection and mitigation. | 30 minutes of continuous inactivity. | Set only when an applicable Cloudflare bot feature is used. |
cf_clearance | Cloudflare | Records that a visitor passed a Cloudflare challenge. | 30 minutes by default; configurable by the site’s Cloudflare challenge setting. | Set when a challenge or related verification applies. |
_cfuvid | Cloudflare | Helps rate limiting distinguish visitors who share an IP address. | Configuration-dependent. | Set only when the relevant Cloudflare rate-limiting option is enabled. |
__cflb | Cloudflare | Load-balancer session affinity. | From several seconds up to 24 hours, as configured. | Set only if the corresponding load-balancer feature is used. |
cf_ob_info and cf_use_ob | Cloudflare | Support Cloudflare Always Online behavior during an origin error. | 30 seconds. | Set only when the corresponding feature and event apply. |
| Cloudflare Web Analytics beacon | Cloudflare | Sends page-performance and aggregate usage metrics. | Cloudflare states that unsampled beacon data is held for 7 days, with a reduced aggregate retained longer. | A beacon is not necessarily a cookie. The active script loads from static.cloudflareinsights.com. |
| Browser-session chat memory | MiniMax-AI.chat interface | Preserves limited recent context for a multi-turn demo session. | Active page session. | Browser memory, not a verified persistent chat cookie or account archive. |
For current provider details, read Google’s advertising-cookie information and Cloudflare’s cookie documentation. Provider documentation and live behavior can change after this page’s verification date.
Google advertising and consent
Google AdSense can receive the visited page URL, IP address, browser or device information, consent signals, advertisement interactions, and fraud-prevention data. Depending on the consent decision and applicable rules, Google and vendors shown in the message can use cookies or similar technologies for advertising delivery, frequency control, personalization, and measurement.
Google’s EU User Consent Policy requires participating publishers to obtain legally valid consent where required, retain consent records, provide a way to revoke consent, and identify parties that can receive data. The published Google message supplies the location-dependent vendor and purpose interface. Read Google’s EU User Consent Policy and Google’s partner-sites notice.
How to manage or withdraw choices
- Use the “Manage options,” “Privacy choices,” or equivalent control displayed by Google for your location.
- Use browser settings to inspect, block, or delete cookies and site data.
- Use Google My Ad Center for available Google advertising controls.
- Reload the page after changing browser or consent settings when necessary.
- Email [email protected] if the site’s consent control does not work as expected.
Blocking necessary delivery or security technologies can affect page access, rate limiting, challenge completion, or protection against abuse. Rejecting non-essential advertising purposes can change which advertisements are available and how they are measured or personalized.
Changes
This policy will be reviewed when a provider, plugin, consent message, advertising configuration, analytics service, or material cookie behavior changes. Email [email protected] with a cookie or consent question concerning this website.