Cookie Policy

1. INTRODUCTION

This Cookie Policy explains how Amblash.AI, a platform owned and operated by Adforn LLC, a company registered at Wilmington, DE 19801 ("Adforn LLC," "we," "us," or "our"), uses cookies and similar technologies on our website at https://amblash.ai and in our B2B sales email automation platform (together, the "Services").

This policy should be read alongside our Privacy Policy, which explains more broadly what Personal Data we collect and how we use it.

2. WHAT COOKIES ARE

A cookie is a small text file that a website asks your browser to store on your device. On each later request to that website, your browser sends the cookie back. Cookies are how a website recognizes that a series of separate requests comes from the same browser, which is what makes staying signed in possible at all.

Cookies are described in two ways in this policy:

First-party cookies are set by us, under our own domain.
Third-party cookies are set by another company whose service we use, under that company's own domain and subject to that company's own policies.

We do not currently display a cookie banner or a cookie preference center. We are telling you that plainly rather than describing a control that does not exist. Section 6 sets out what you can do instead, which is to use the controls your browser already gives you.

3. STRICTLY NECESSARY COOKIES

These are the cookies our own platform sets. They exist to sign you in, keep you signed in, and protect your account while you are signed in. We set no first-party cookie for advertising, profiling, or tracking you across other websites.

All five are first-party cookies. Each carries the __Host- name prefix, which instructs your browser to accept the cookie only over a secure HTTPS connection, only for the exact site that set it, and never for a related site or subdomain. Each is marked Secure and is scoped to the whole site (path /). None carries a domain attribute, so none can be sent to any other origin.

Cookie	What it is for	How long it lasts
__Host-at	Your access token. This is the cookie that keeps you signed in and proves to our servers that a request is yours. It is marked HttpOnly, so no script running in the page can read it.	15 minutes, then renewed automatically while your session is active
__Host-rt	Your refresh token. It renews your session in the background so you are not asked for your password every few minutes. It is marked HttpOnly, so no script running in the page can read it.	30 days
__Host-csrf	A cross-site request forgery token. It protects you from another website trying to make a change to your account by using your signed-in session. It is readable by our own page's script so that the page can send the value back with each write request, and it carries no personal data.	For the length of your browser session, and cleared when you sign out
__Host-sess-hint	Holds only the literal value "1". It tells the interface that a session exists, so the page can show you the signed-in view without having to ask the server first. It carries no secret and no personal data.	30 days, and cleared when you sign out
__Host-at-exp	Holds the expiry time of your access token as a number. It lets the interface renew your session shortly before it lapses, rather than interrupting you with a sign-in prompt in the middle of your work. It carries no secret and no personal data.	15 minutes, alongside the access token it describes

These cookies cannot be switched off without breaking sign-in. They are not a convenience layered on top of the Services; they are the mechanism by which the Services recognize you. If your browser refuses them, you will not be able to sign in, and a session you already have will end.

Signing out clears all five.

4. ANALYTICS COOKIES

Our website loads Google Analytics, a measurement service provided by Google. We use it to understand how our website is used in aggregate: which pages people reach, how they move between them, and where the site is confusing or slow. We do not use it to build advertising profiles, and we do not sell what it tells us.

These cookies are set by Google as a third party, not by us. The main ones are:

_ga: Distinguishes one visitor from another, so that repeat visits are counted as one person rather than several.
_ga_<container-id>: Holds the state of the current visit for the specific analytics property our site is measured under. The trailing part of the name is the identifier of that property.

Google may set further cookies of its own, and the names and lifetimes above are Google's to set and change rather than ours. The authoritative and current description is Google's:

Refusing or removing these cookies does not stop you from using our website or signing in. It only means your visit is not counted in our usage figures.

5. PAYMENT COOKIES

Payments are processed by Stripe. We never handle or store your card details; you enter them on Stripe's own hosted checkout page, and you manage your subscription on Stripe's own hosted billing portal.

Stripe sets its own cookies in that context, including __stripe_mid and __stripe_sid, which Stripe uses for fraud prevention and to make the payment work correctly. They are set by Stripe as a third party, under Stripe's control and subject to Stripe's own policies.

These are set when you go through payment, not by browsing this website. Reading our marketing pages loads no Stripe script and sets no Stripe cookie. For Stripe's own account of what it sets and why, see:

6. HOW TO CONTROL COOKIES

Every major browser lets you see the cookies a site has stored, delete them, block cookies from particular sites, and block third-party cookies generally. These controls sit in your browser's privacy or site-data settings, and they apply whether or not a website offers a control of its own.

The consequences differ by category, and it is worth being clear about which is which:

Blocking the strictly necessary cookies in Section 3 prevents sign-in. There is no alternative route: without them our servers cannot recognize your session, so you will not be able to sign in, and clearing them while signed in will sign you out.
Blocking analytics cookies costs you nothing. The website and the platform work exactly as before; your visit simply is not counted.
Blocking the payment cookies may prevent a payment from completing, because our payment processor uses them to verify the transaction is genuine.

You can also opt out of Google Analytics across every website that uses it by installing Google's own browser add-on, available from Google.

7. CHANGES TO THIS COOKIE POLICY

We may update this Cookie Policy from time to time, for example if we add or remove a service that sets cookies. Changes take effect when the updated policy is posted on our website.

Where a change is material, we will give notice of it in the same way we give notice of changes to our Privacy Policy. Your continued use of the Services after a change takes effect constitutes acceptance of the updated Cookie Policy.

8. CONTACT INFORMATION

For questions about this Cookie Policy or about any cookie described in it, please contact us:

Amblash.AI, operated by Adforn LLC

Registered address: 1007 Orange St, Wilmington, DE 19801

Email: hello@amblash.ai

Contact us: contact us page

Privacy Policy: Privacy Policy

We will respond to all legitimate inquiries within a reasonable timeframe, typically within 30 to 40 business days.

Governing Language: This Cookie Policy is written in English. If this Cookie Policy is translated into other languages, the English version shall prevail in case of any inconsistencies or discrepancies.

Severability: If any provision of this Cookie Policy is found to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.