Cookie Policy

1. Introduction & Storage Philosophy

At Hammer Ai (accessible via eng-hammerai.com, including all subdomains, client-side web applications, and mobile interfaces), we believe that intimate synthetic companions, uncensored creative roleplay, and emotional dating simulations necessitate an uncompromising standard of technical privacy. In stark contrast to conventional commercial web properties that blanket your browser with hundreds of persistent tracking cookies and data broker beacons, Hammer Ai operates strictly under a minimalist, zero-telemetry storage model.

This Cookie Policy explains in exhaustive, clear detail how and why we utilize HTTP cookies, client-side browser Local Storage, Session Storage, and ephemeral memory caches. By accessing or interacting with Hammer Ai, you acknowledge the storage and access of information on your device in accordance with the specific parameters detailed below.

2. What Are Cookies & Web Storage Technologies?

Cookies are compact alphanumeric data files placed on your computer, smartphone, or tablet when you navigate modern websites. They allow web servers to recognize your specific browser session, maintain authenticated states as you navigate between character rosters, and recall your customized interface preferences.

Beyond traditional HTTP cookies, modern web architectures utilize complementary client-side technologies:

• HTTP Cookies: Small string tokens sent automatically in HTTP header requests between your browser and our secure reverse proxy to maintain encrypted authentication and defend against Cross-Site Request Forgery (CSRF).
• HTML5 Local Storage (`localStorage`): A persistent browser key-value repository that resides strictly within your local machine. It allows our web app to load character interface states, UI layout preferences, and audio toggle levels instantly without transmitting unnecessary metadata to our server clusters.
• Session Storage (`sessionStorage`): A temporary client-side data store that automatically purges itself the instant you terminate your active browser tab or window, ensuring transient chat states do not leak beyond your immediate private session.
• IndexedDB / In-Memory Cache: Volatile client-side database storage used exclusively to cache character avatar imagery and encrypted client-side dialogue cards for smooth, lag-free rendering.

3. Categories of Cookies We Deploy

Hammer Ai restricts its use of browser storage strictly to mechanisms essential for platform operation, high-speed generative rendering, and account security. We categorize our storage tools into three narrow tiers:

• Strictly Necessary Authentication Cookies: These cookies are critical to the secure functioning of Hammer Ai. They facilitate encrypted token-based user authentication (JSON Web Tokens / JWTs), verify that requests originate from your authenticated browser, and prevent account hijacking. Without these cookies, you cannot log in, access your custom companion roster, or unlock VIP tier features.
• Security, Anti-DDoS & Rate Limiting Tokens: Distributed Denial of Service (DDoS) mitigation and automated bot protection networks utilize ephemeral security cookies (such as cloud security clearance tokens) to distinguish human users from automated malicious attack vectors. These tokens contain no personal identity information, prompt texts, or companion preferences.
• Functional UI & Preference Storage: Primarily implemented via HTML5 Local Storage, these records preserve your dark mode theme selection, active audio mute/unmute state for companion voice playback, preferred text font scaling, and sidebar collapse states. This ensures you do not have to reconfigure your UI settings on each visit.

4. What We Strictly Never Deploy

In accordance with our non-collection guarantee and commitment to uninhibited adult privacy, Hammer Ai maintains an immutable prohibition against invasive tracking technologies:

• Zero Third-Party Advertising Cookies: We do not host ad network scripts, tracking pixels, or commercial affiliate remarketing cookies (including Meta Pixel, Google Ads Remarketing, TikTok Pixel, or Outbrain). Your navigation on Hammer Ai will never cause adult companion ads to follow you across the public web.
• Zero Data Broker Tracking Beacons: We do not cooperate with commercial data syndicates, behavioral targeting entities, or audience profiling platforms.
• No Hardware Device Fingerprinting: We do not construct intrusive canvas fingerprinting or audio-stack telemetry signatures to identify your hardware profile outside of the platform.
• No Prompt Logging in Cookies: Conversational dialogue with personas (such as Sister Patience, Cora, Toji, or custom bots) is never serialized or written into plaintext browser cookies accessible to third parties.

5. Cookie & Storage Inventory Table

To provide complete visibility, the following table details the primary cookies and local storage tokens utilized across Hammer Ai:

6. Client-Side Vector & State Storage

Because Hammer Ai prioritizes client-side security, parts of your companion configuration and active interactive branches reside strictly inside your local browser memory rather than lingering on open central servers. When you switch characters or adjust a scenario backstory, this transient data is preserved in temporary memory structures until your session ends or you trigger a deliberate purge.

This architecture ensures two critical privacy advantages: first, inference requests are executed statelessly through high-performance GPU clusters without storing persistent prompt chains in non-essential databases; second, if an unauthorized third party attempts to intercept your connection, they cannot glean your conversation history from remote unencrypted cookies.

7. Panic Wipe & Immediate Storage Eviction

When the Panic Wipe mechanism is engaged by the user:

• All active HTTP session cookies (`__hammer_auth_token`) are immediately invalidated server-side and overwritten in the browser with null headers.
• The platform systematically executes localStorage.clear() and sessionStorage.clear(), obliterating all saved UI states, companion draft buffers, and audio settings.
• Cached character thumbnail images and profile cards in client memory are purged, preventing local browser history recovery.
• The browser window is instantaneously redirected to a neutral, benign public destination (such as a search engine or generic utility page).

8. Managing, Blocking & Disabling Cookies

You retain absolute sovereignty over the storage technologies accepted by your web browser. You may adjust your browser settings at any time to block all cookies, reject third-party cookies, or prompt you prior to writing cookie data.

To adjust cookie management across prominent web browsers:

• Google Chrome: Navigate to Settings > Privacy and Security > Third-party cookies > Adjust blocking preferences or clear site data for eng-hammerai.com.
• Mozilla Firefox: Navigate to Settings > Privacy & Security > Enhanced Tracking Protection > Set to "Strict" or customize cookie permissions.
• Apple Safari: Navigate to Preferences > Privacy > Toggle "Prevent cross-site tracking" and manage "Cookies and website data".
• Microsoft Edge: Navigate to Settings > Cookies and site permissions > Manage and delete cookies and site data.
• Brave & Tor Browser: Built-in shields actively block third-party storage by default; verify that First-Party Shields allow essential cookies for functional login.

Important Functional Notice: Because Hammer Ai relies on cryptographic session cookies for user login verification, disabling all cookies will prevent you from accessing authenticated accounts, saving companion storylines, or utilizing VIP subscription privileges.

9. Global Privacy Control (GPC) & Do Not Track

Hammer Ai honors universal, machine-readable privacy preference signals, including the Global Privacy Control (GPC) and Do Not Track (DNT) browser headers. Because our platform operates on a default Zero Data Brokering and Zero Cross-Site Tracking framework, your browser is treated as opted-out of all commercial tracking and data brokering by default, regardless of whether a GPC header is actively transmitted.

10. Statutory & Regional Directives (ePrivacy, GDPR, CCPA)

Our deployment of browser storage technologies adheres rigorously to prevailing international digital privacy and electronic communications regulations:

• EU ePrivacy Directive & GDPR: Under the ePrivacy Directive (Directive 2002/58/EC as amended), cookies that are strictly necessary for the delivery of an information society service explicitly requested by the user do not mandate prior opt-in consent banners. Because Hammer Ai limits cookie usage solely to strictly necessary authentication and security tokens, no invasive commercial tracking banner is required or displayed.
• California Consumer Privacy Act (CCPA/CPRA): We do not "sell" or "share" personal information or cookie identifiers as defined under California law. We provide transparent documentation of our local storage usage and respect all statutory consumer privacy rights.
• UK Data Protection Act & PECR: Our storage protocols mirror the rigorous standards of the UK Privacy and Electronic Communications Regulations, safeguarding end-user terminal equipment from unauthorized data inspection.

11. Updates to This Cookie Policy

Hammer Ai reserves the right to periodically update this Cookie Policy to reflect technical infrastructure updates, protocol advancements, or evolving legal frameworks. When material changes occur, we will update the "Last Revised" date at the top of this document. We encourage users to periodically review this page to remain informed of our storage safeguards.

12. Privacy Directorate & Cookie Inquiries

If you have technical inquiries regarding our cookie architecture, wish to inspect our client-side storage methods, or wish to communicate directly with our compliance desk, please contact us:

• Entity: Hammer Ai Global Network Privacy & Infrastructure Directorate
• Primary Portal: eng-hammerai.com
• Cookie & Technical Inquiries: [email protected]
• Legal & Compliance Desk: [email protected]