COOKIE, LOCAL STORAGE,
ANALYTICS AND ADVERTISING TECHNOLOGIES POLICY

1. Scope, Controller, contacts, and definitions

1.1. This Cookie, Local Storage, Analytics and Advertising Technologies Policy (the “Policy”) explains how HentaiStudio uses cookies, localStorage, sessionStorage, JavaScript tags, pixels, redirects, browser or device identifiers, consent records, and similar technologies on https://hentaistudio.com.

1.2. It applies to public browsing, Account access, age-gate status, fictional AI chat, browser-local chat history, interface preferences, User uploads, reports, USDT Checkout, Paid Support Access Activation, Google Analytics 4, and advertising supplied through TrafficStars Ltd. Content, conduct, age, and safety restrictions are governed by the Terms, the Acceptable Use, Age and Content Safety Policy, and the Upload Rules.

1.3. For this Policy, the “Controller” or “Operator” is the person or entity exercising operational control over HentaiStudio and determining the purposes and means of HentaiStudio’s own processing. HentaiStudio is the service name used for the Platform and is not represented as a separately incorporated company unless a binding Service disclosure expressly states otherwise.

1.4. Cookie, local-storage, analytics, advertising-technology, and consent questions may be submitted through the public Feedback page. Registered Users may also use profile support.

1.5. A cookie is a small data file stored through a browser. Similar technologies include localStorage, sessionStorage, IndexedDB, browser caches, pixels, scripts, tags, redirects, consent signals, frequency caps, online identifiers, and methods that store information on or access information from a browser, device, or other terminal equipment.

1.6. A technology may be regulated even where its data is pseudonymous, does not identify a User by name, remains on the device, or is used mainly for measurement, advertising, security, or fraud prevention.

1.7. This Policy supplements the Privacy Policy. Server-side processing, AI-provider processing, recipients, security logs, User uploads, reports, payment records, international transfers, legal bases, and privacy rights are described there.

1.8. The live consent interface, scripts, cookies, storage, network requests, and provider settings must remain materially consistent with this Policy. Where production differs, the integration or this Policy must be corrected before the affected optional processing continues.

• Strictly necessary: Technology genuinely required to transmit communications, authenticate or secure an Account, remember a privacy choice, prevent abuse, or provide a feature expressly requested by the User.
• Functional: Storage used to provide requested conversation continuity or remember a selected interface setting.
• Analytics: Optional Google Analytics 4 measurement used for aggregate traffic, feature use, performance, compatibility, and engagement.
• Advertising: Technology used to deliver ads, control frequency, measure impressions or clicks, process redirects, report performance, prevent invalid traffic and, where lawfully enabled, personalize advertising.
• Cookie Settings: The interface used to accept, reject, review, or withdraw optional Analytics and Advertising choices.

2. Disclosed production configuration

2.1. HentaiStudio discloses Google Analytics 4 with Measurement ID G-9SQB20ZW5X as its website analytics integration.

2.2. HentaiStudio discloses TrafficStars Ltd as an advertising provider. Depending on the live placement, device, country, consent choice, provider configuration, and demand, banner, native, or in-page advertisements may be displayed.

2.3. Google Signals, GA4 User-ID, Google Ads remarketing, enhanced conversions, customer-list uploads, and Google advertising personalization are not authorized under this Policy version.

2.4. Analytics and Advertising are separate optional categories. Accepting one does not accept the other.

2.5. Where prior consent is required, optional GA4, TrafficStars, advertiser, exchange, or comparable tags, storage, identifiers, pixels, redirects, or tracking requests must remain blocked until the User grants the relevant category.

2.6. Passing the age gate, accepting the Terms, creating an Account, starting a chat, uploading, reporting, paying, closing a notice, scrolling, clicking ordinary site content, or continuing to browse is not consent where affirmative consent is required.

2.7. Refusing optional Analytics or Advertising must not prevent access to the core free Service. Contextual or non-personalized advertising may appear only where the actual integration supports that mode and applicable law permits it.

2.8. Contextual or non-personalized does not necessarily mean that no network request, IP processing, security signal, or ad-delivery data is used. Any consent-exempt operation must be genuinely configured for that limited purpose.

2.9. HentaiStudio must update this Policy and the live consent interface before activating a materially different provider, Google advertising feature, new personalization purpose, special-category inference, or materially different optional technology.

3. Information used by browser technologies

3.1. Depending on the requested feature, browser, page, consent choice, provider, advertising format, and configuration, browser technologies may store, access, transmit, or generate the categories below.

3.2. HentaiStudio must not intentionally place private Chat Input, AI Output, conversation titles, intimate preferences, Account email, private Account identifiers, report descriptions, uploaded-file contents, wallet addresses, transaction hashes, passwords, authentication codes, private keys, seed phrases, or government identifiers into analytics or advertising event names, macros, parameters, dimensions, URLs, titles, or referrers.

• Random session, authentication, consent, preference, Checkout, security, analytics, advertising, frequency-cap, browser, or device identifiers.
• Consent category, timestamp, Policy version, withdrawal status, provider or vendor choice, and limited regional configuration.
• Age-gate response status and time without requiring a date of birth or identity document.
• Language, theme, layout, accessibility, display, and other interface settings selected by the User.
• Private User messages, AI responses, character identifiers, conversation titles, timestamps, and local conversation settings stored in browser-local chat history.
• Pending Invoice reference, selected access period, limited payment-status state, and Checkout expiration.
• Requested page or minimized contextual identifier, title, referrer, publisher and placement identifiers, timestamp, browser, operating system, device category, language, screen data, approximate location, and technical capability.
• Site support content, campaign, creative, impression, click, redirect, conversion or performance information where configured, together with frequency and anti-fraud signals.
• Authentication, rate-limit, consent, anti-abuse, or security state required to protect Accounts, forms, uploads, reports, payments, advertising inventory, and infrastructure.

4. Browser-local private AI-chat history

4.1. Ordinary private AI-chat history is designed to be stored in first-party localStorage or comparable browser storage in the User’s current device and browser profile.

4.2. HentaiStudio does not intentionally maintain a persistent server-side archive of ordinary private chat histories and does not provide the Operator with a routine administrative viewer for browsing those histories.

4.3. Local storage allows conversations to remain visible after reloads and later visits using the same browser profile. It is not intended to synchronize automatically between devices.

4.4. Local history may contain adult, intimate, or otherwise sensitive text. Anyone who can access the same unlocked device, operating-system Account, or browser profile may be able to read it.

4.5. Local chat history must not be intentionally read or transmitted by GA4, TrafficStars, an advertiser, or another advertising-supply-chain participant.

4.6. The current Chat Input and limited recent context must still be transmitted temporarily through HentaiStudio and/or an AI provider when the User requests a response. That network processing is separate from persistent browser-local storage and is explained in the Privacy Policy.

4.7. Local history remains until the User deletes a conversation or all history, clears site data, removes the browser profile or installed PWA, loses the device, or the browser removes stored data.

4.8. HentaiStudio ordinarily cannot restore locally deleted or lost history because no independent persistent server-side copy is intentionally maintained.

4.9. HentaiStudio treats persistent local conversation history as functional storage for a continuity feature requested by the User. Where applicable law requires a separate prior choice for that persistent storage, it must not be created before that choice.

5. Strictly necessary and functional technologies

5.1. HentaiStudio may use strictly necessary technology without optional Analytics or Advertising consent only where applicable law permits and the technology is genuinely required for communications, authentication, security, privacy choices, requested functionality, Checkout continuity, or proportionate fraud prevention.

5.2. Technology is not strictly necessary merely because it increases revenue, measures audience size, improves analytics, personalizes ads, performs attribution, limits ad repetition, or makes the Service commercially useful.

5.3. GA4 remains optional Analytics. TrafficStars targeting, advertising identifiers, cross-site measurement, and other non-essential advertising technology remain optional wherever prior consent is required.

5.4. A narrowly scoped security or fraud-prevention request may have different treatment only where it is technically separated from personalization and is genuinely necessary and proportionate.

• Authentication and session security: Secure cookies, tokens, memory values, or equivalent technology may maintain the authenticated Account and protect restricted functionality.
• Consent preference: A first-party record may remember separate Analytics and Advertising choices, timestamp, Policy version, later changes, and withdrawal.
• Age-gate status: A first-party record may remember that the adults-only notice was answered. The age gate is not Analytics or Advertising consent.
• Conversation continuity: First-party browser storage may keep private chat history available on the same browser profile.
• Interface preferences: First-party storage may remember language, theme, accessibility, display, and layout choices selected by the User.
• Checkout continuity: Temporary first-party storage may associate a pending USDT Invoice or Activation check with the correct browser, session, or Account.
• Security and abuse prevention: Temporary identifiers may protect login, uploads, reports, forms, payments, rate limits, advertising inventory, and infrastructure against replay, automation, malware, invalid traffic, fraud, or unauthorized access.

6. Google Analytics 4

6.1. HentaiStudio uses Google Analytics 4 with Measurement ID G-9SQB20ZW5X to understand aggregate traffic, sessions, pages and features used, approximate geographic distribution, device and browser compatibility, technical performance, and general engagement.

6.2. Where prior consent is required, the Google tag at https://www.googletagmanager.com/gtag/js?id=G-9SQB20ZW5X must remain blocked until Analytics consent is granted.

6.3. Under HentaiStudio’s intended Basic Consent Mode configuration, HentaiStudio does not intentionally send GA4 requests, consent pings, cookieless measurements, or Advanced Consent Mode events before required Analytics consent.

6.4. After Analytics consent, the standard GA4 tag may set the first-party cookies _ga and _ga_9SQB20ZW5X.

6.5. Google documents a default expiration of up to 2 years for those cookies. Actual persistence may be shorter because of browser restrictions, HentaiStudio configuration, consent withdrawal, deletion, or provider changes.

6.6. HentaiStudio intends to configure user-level and event-level GA4 retention at no more than 14 months. The live GA4 property must match this statement.

6.7. Once the tag is permitted to load, the browser communicates with Google. Google may process IP information during request handling, device and browser information, page and referrer data, approximate location, consent state, client identifier, session data, and configured events.

6.8. HentaiStudio must not intentionally send names, email addresses, private messages, AI responses, report text, uploaded-file contents, wallet addresses, transaction hashes, or other directly identifying or sensitive information through GA4.

6.9. Google processes information under its applicable terms, privacy documentation, data-processing terms, security measures, transfer arrangements, and product documentation.

6.10. Linking GA4 to Google Ads or enabling another Google advertising feature creates additional processing and must not occur until this Policy, the Privacy Policy, and the consent interface are updated.

• Provider: Google Analytics 4.
• Measurement ID: G-9SQB20ZW5X.
• Tag: https://www.googletagmanager.com/gtag/js?id=G-9SQB20ZW5X.
• Category: Optional Analytics.
• Cookies: _ga and _ga_9SQB20ZW5X.
• Private chat: Private Chat Input, AI Output, local history, and intimate conversation information are not intentionally supplied to GA4.

7. TrafficStars advertising technologies

7.1. HentaiStudio may display advertising supplied through TrafficStars Ltd to finance the free Service.

7.2. Advertising technology may deliver an advertisement, control frequency, measure impressions and clicks, process redirects, report performance, settle publisher and advertiser accounts, and detect invalid, automated, fraudulent, or malicious traffic.

7.3. Depending on the provider and configuration, advertising may use JavaScript, redirects, cookies, localStorage, pixels, online identifiers, device signals, campaign identifiers, consent signals, and advertising-supply-chain partners.

7.4. Exact third-party cookie names, domains, partners, and durations may vary by active placement, campaign, exchange, browser, geography, consent choice, and provider update. HentaiStudio does not invent a fixed third-party inventory that has not been observed in production.

7.5. Where prior consent is required, optional TrafficStars scripts, identifiers, cookies, localStorage, pixels, or comparable advertising requests must remain blocked until Advertising consent is granted.

7.6. Rejecting Advertising must prevent future optional advertising tracking initiated through HentaiStudio where technically controllable. It may not erase information already lawfully retained by a provider or prevent limited contextual advertising where that mode is genuinely supported and lawful.

7.7. HentaiStudio does not intentionally send private Chat Input, AI Output, local conversation history, Account email, report text, uploaded-file contents, wallet addresses, transaction hashes, payment secrets, authentication secrets, or government identifiers to advertising providers.

7.8. Page URLs, titles, tags, or character names may reveal adult interests. HentaiStudio should use generic placement identifiers, avoid sensitive query parameters, minimize detailed page-level signals, and apply an appropriate referrer policy.

7.9. HentaiStudio does not authorize advertising based on profiling that uses personal data concerning a User’s sex life, sexual orientation, health, or another protected special category where prohibited.

7.10. Clicking an advertisement may open a third-party website or application governed by the third party’s terms, cookies, privacy practices, security, products, and representations.

7.11. Site support contents must not be disguised as AI messages, User uploads, system notices, download buttons, consent controls, navigation controls, or HentaiStudio editorial content.

7.12. Advertising is limited to banner, native, or in-page placements and must follow provider, placement, and consent rules.

7.13. A provider-specific opt-out may stop specified collection or personalization without stopping every advertisement and may need to be repeated after clearing cookies or changing browser or device.

• Providers: TrafficStars Ltd.
• Possible formats: Banner, native, and in-page formats enabled in the live publisher configuration.
• Purposes: Ad delivery, frequency control, measurement, reporting, redirect handling, settlement, security, and invalid-traffic prevention; personalization only where lawfully enabled.
• Consent: Separate Advertising choice where prior consent is required.
• Private chat restriction: Private messages, AI responses, and local conversation history are not intentionally supplied to advertising providers.

8. Adult-interest privacy and sensitive-data safeguards

8.1. The HentaiStudio domain, page context, selected character, tags, and browsing behavior may reveal highly private adult interests.

8.2. Fictional adult browsing or roleplay does not by itself establish a factual statement about a User’s real-world sex life, sexual orientation, health, identity, or beliefs. HentaiStudio does not intentionally assign such characteristics merely from fictional browsing or chat.

8.3. Private Chat Input, AI Output, local chat history, and intimate conversation preferences must not be used for advertising targeting, audience creation, analytics dimensions, or data-broker disclosure.

8.4. HentaiStudio must not intentionally encode sensitive character, Account, payment, report, or chat information in advertising URLs, macros, placement names, event parameters, page titles, or referrers.

8.5. The Service should use an appropriate Referrer-Policy and minimize information disclosed to third-party destinations. Browser behavior and destination requests may still expose the source domain unless technically prevented.

8.6. Security and anti-fraud processing must not be repurposed for prohibited sensitive profiling merely because the same provider also participates in advertising.

9. Consent, rejection, category choices, and withdrawal

9.1. Where consent is required, it must be freely given, specific, informed, unambiguous, and expressed through a clear affirmative action.

9.2. Optional Analytics or Advertising must not be enabled through silence, inactivity, scrolling, continued browsing, a preselected switch, a pre-checked box, an age-gate response, or a control that requires the User to disable an already enabled category.

9.3. The initial interface must provide a clear Reject non-essential option. Rejection must not require more steps or materially more effort than acceptance.

9.4. Core access must not be denied merely because a User rejects GA4 or optional advertising tracking. Necessary and requested functional storage may remain available where lawful.

9.5. A first-party consent record may be retained for up to 12 months unless the User changes the choice earlier, clears storage, the record becomes unreliable, or a material change requires a new choice.

9.6. The record should identify Analytics and Advertising separately, timestamp, Policy version, later withdrawal, and provider or vendor choices where relevant. It must not contain private chat text, AI responses, uploads, payment secrets, or report descriptions.

9.7. The User must be able to reopen Cookie Settings through a persistent, reasonably accessible control and change or withdraw optional choices without deleting the Account.

9.8. Withdrawal applies prospectively. HentaiStudio must stop future loading of the withdrawn category where technically controllable and stop creating new identifiers through its integration for that category.

9.9. Existing third-party cookies or data may remain until deleted, expired, or handled by the provider. The User may need browser deletion or provider-specific controls.

9.10. A fresh choice may be requested after the consent period expires or when HentaiStudio introduces a new provider, materially different purpose, new personalization feature, or other material change.

• Accept all: Allows the disclosed optional Analytics and Advertising categories, subject to provider and browser controls.
• Analytics only: Allows GA4 while keeping optional advertising tracking blocked.
• Advertising only: Allows the disclosed Advertising category while keeping GA4 blocked.
• Reject non-essential: Keeps optional GA4 and optional advertising tracking blocked while allowing genuinely necessary or requested functional technology.
• Withdraw: Stops future loading of the withdrawn optional category through HentaiStudio after the updated choice is applied.
• Global Privacy Control: Where legally required and technically applicable, a recognized GPC signal may be treated as an opt-out for processing covered by that signal.
• Do Not Track: The legacy DNT signal is not uniformly standardized or technically actionable.

10. Current cookie and browser-storage inventory

10.1. The inventory below describes the intended production configuration. The live application, CMP, scripts, browser storage, advertising placement, provider requests, and tag loader must remain consistent with it.

10.2. If inspection reveals a different name, domain, category, purpose, duration, data field, or activation condition, HentaiStudio must correct the implementation, consent disclosure, or this Policy before continuing the affected optional processing.

10.3. First-party storage is described by function rather than an invented public key name. The actual production key or cookie name should be documented internally and may be added publicly after verification.

10.4. Provider-controlled advertising cookie names and durations may change dynamically. The inventory identifies the provider and technology category without pretending that an unobserved fixed list is complete.

11. User controls, deletion, retention, and expiration

11.1. Users may control browser technology through HentaiStudio Cookie Settings, local chat-history controls, Account or interface settings, browser controls, content blockers, and provider-specific controls.

11.2. Rejecting or withdrawing Analytics or Advertising does not delete browser-local chat history because those functions are separate.

11.3. Deleting local chat history does not change Analytics or Advertising choices.

11.4. Clearing all HentaiStudio site data may delete consent choices, age-gate status, authentication state, chat history, preferences, pending Checkout state, and provider opt-out cookies.

11.5. HentaiStudio ordinarily cannot restore locally deleted chat history.

11.6. Browser extensions, private-browsing modes, enterprise settings, operating-system restrictions, and browser policies may block or shorten storage independently of HentaiStudio.

11.7. Google’s opt-out add-on is an additional control and does not replace HentaiStudio’s duty to respect a required Analytics choice.

11.8. A storage item remains until expiration, User deletion, browser removal, provider deletion, Service replacement, or loss of the browser profile or device.

11.9. Some cookies use rolling expiration, so later permitted activity may refresh their expiration according to configuration.

11.10. GA4 cookies and user-level or event-level data follow the disclosed settings and Google configuration. Aggregated reporting may be treated differently by Google.

11.11. TrafficStars, advertisers, and exchange partners determine retention for information they independently control under their policies, contracts, settings, legal obligations, and User choices.

11.12. Separate server-side Account, upload, payment, support, security, consent, report, and moderation records are governed by the Privacy Policy and are not the same as cookies or browser-local chat history.

12. Audits, changes, contacts, and related documents

12.1. HentaiStudio may update this Policy when storage, providers, retention, Google settings, advertising formats, consent requirements, Service functionality, or law changes.

12.2. A materially different provider, Google advertising feature, personalization purpose, special-category inference, or use of private chat content must not be activated until the required disclosure and lawful control are available.

12.3. HentaiStudio should periodically inspect production cookies, localStorage, sessionStorage, IndexedDB, outgoing Google requests, TrafficStars requests, advertising redirects, exchange domains, page URLs, consent behavior, and provider settings.

12.4. The audit should cover a fresh browser before any choice, rejection, Analytics-only consent, Advertising-only consent, acceptance of all categories, withdrawal of each category, and browser-data deletion.

12.5. HentaiStudio should retain reasonable evidence of consent text, category choices, Policy version, timestamp, and the technical configuration used for material consent-controlled processing.

12.6. A fresh choice will be requested where required because of a material change.

12.7. Cookie, storage, Analytics, Advertising, or consent questions may be submitted through Feedback. Registered Users may also use profile support. Privacy rights requests are governed by the Privacy Policy.

12.8. No separate Legal Notice page is incorporated by this Policy. The Acceptable Use, Age and Content Safety Policy at /acceptable-use forms part of the Service rules together with the Terms and Upload Rules. The Operator is defined in Section 1, and official electronic contact channels are Feedback and profile support.

12.9. Provider-specific processing is also governed by each provider’s current privacy, cookie, opt-out, and product documentation.

Related policies and official contacts

Read the Privacy Policy for server-side processing, AI and advertising recipients, legal bases, retention, transfers, and privacy rights.

Read the Terms of Service and Acceptable Use, Age and Content Safety Policy for general Service, age, content, safety, Account, upload, and conduct rules.

Read the Cryptocurrency Payments, Activation and Refunds Policy for USDT Checkout and payment records.

Read the DMCA, Copyright and Content Removal Policy for copyright and content complaints.

Cookie Settings, Analytics, Advertising, localStorage, or consent questions may be submitted through the Feedback page. Registered Users may also use profile support.

General Platform information is available on the About page. No separate Legal Notice page is incorporated by this Policy. The Acceptable Use, Age and Content Safety Policy is part of the Service rules.