Cookie Policy

1. About This Policy

This Cookie Policy explains how Chat4U uses cookies, localStorage, sessionStorage, and similar technologies on the Chat4U marketing website, dashboard, hosted demos, and embedded chat widget. It should be read together with our Privacy Policy.

Some technologies are strictly necessary for the Service to function. Others, including the marketing-site widget, are consent-dependent where required by applicable law.

---

2. What We Mean by Cookies and Similar Technologies

Cookies are small text files stored by your browser. Similar technologies include localStorage, sessionStorage, pixels, scripts, and software identifiers that help maintain security, user state, and functionality across requests.

In this Policy, "cookies" includes both cookies and similar browser-storage technologies unless the context requires otherwise.

---

3. Categories We Use

3.1 Strictly Necessary Technologies

These technologies are used for functions such as:

• authentication and session continuity;
• security and abuse prevention;
• language or locale selection;
• consent-state storage;
• dashboard and account operation;
• widget runtime continuity where the widget is already allowed to load.

Blocking strictly necessary technologies may prevent login, dashboard access, or core site functionality.

3.2 Consent-Dependent Functional Chat Technology on the Marketing Site

On the Chat4U marketing website, the Chat4U widget does not load until functional chat consent is granted. On customer websites, ordinary widget chat does not use the marketing-site consent banner.

Before a first message, the widget may store a limited attention-nudge dismissal preference when a visitor dismisses or opens a nudge. Opening the widget alone does not create visitor, tab, or chat-session identifiers and does not create a conversation. Those identifiers are created only on first message send or, for tab state, when a Pro Agent operation actually requires it.

3.3 Analytics Technologies

We may use analytics-related technologies to understand website and product usage, diagnose technical issues, and improve reliability. These technologies may collect page views, approximate geography, device/browser information, referral data, and related interaction data.

Where analytics technologies are used and consent is required, they should not be activated until the relevant consent is granted.

3.4 Marketing Technologies

We may use marketing-related technologies for campaign measurement, attribution, or similar outreach functions. Where marketing technologies are used and consent is required, they should not be activated until marketing consent is granted.

3.5 Payment and Billing Technologies

Paddle, acting as Merchant of Record for Chat4U transactions, may set cookies or related technologies during checkout, billing, purchase management, subscription management, fraud review, or invoicing flows. Those technologies are governed by Paddle's own notices and policies.

---

4. Consent Object Version

Where consent state is stored in browser storage on the Chat4U marketing website, the consent object version is:

2026-07-workspace-notices-v1

A representative consent record may look like this:

{
  "version": "2026-07-workspace-notices-v1",
  "functional": true,
  "analytics": false,
  "marketing": false,
  "timestamp": "2026-07-01T00:00:00.000Z"
}

This example is illustrative. Field names, timestamps, and storage shape may vary by implementation over time.

---

5. Current Widget Data and Identifier Behavior

When the widget is enabled, current behavior may involve browser storage and identifiers used to support:

• visitor recognition across page views;
• chat session continuity;
• tab-specific runtime state;
• interrupted-stream retry behavior;
• Pro Agent or approval-related transient state where that feature is enabled.

Current widget page context is limited to the page origin and pathname. Query strings, fragments, and embedded credentials are removed before that context is stored or supplied to an AI provider. When privacy minimization is enabled, widget session payloads omit referrer, user-agent, timezone, screen dimensions, and fingerprint-like fields; server security and operational request logs are separate.

---

6. Customer Websites

Customers that embed Chat4U on their own websites are responsible for:

• deciding whether and how the widget is deployed;
• providing their own privacy and cookie disclosures;
• obtaining consent where required;
• explaining AI interaction and widget storage to visitors;
• disclosing visitor/session identifiers and related browser-storage behavior;
• configuring analytics, CRM, or other third-party technologies lawfully.

Chat4U does not control a customer's cookie banner, consent text, or website-specific notice obligations.

---

7. Managing Cookies and Browser Storage

You can manage cookies through your browser settings. You can also clear localStorage and sessionStorage through browser site settings or developer tools.

Blocking strictly necessary technologies may interfere with login, dashboard operation, or core site behavior. Removing functional chat storage may reset an in-progress conversation or widget continuity state.

---

8. Do Not Track

Some browsers send "Do Not Track" signals. There is no universal standard for interpreting those signals. We rely on implemented consent controls and applicable legal requirements rather than a uniform Do Not Track response standard.

---

9. Changes to This Policy

We may update this Cookie Policy as product behavior, consent requirements, providers, or legal requirements change. The version and last-updated date identify the current notice.

---

10. Contact

Questions about cookies or browser storage may be sent to support@chat4u.ai.