Cookies
Cookie Policy
Effective 1 September 2026. Automix AI sets one cookie of its own. Two other parties can set cookies, in two specific places, and only if you go there. This page names all three.
Most cookie policies are long because most products carry advertising tags and third-party analytics. Automix carries neither. We do use self-hosted Umami to count page views, but it is first-party and cookieless. Self-hosted Umami uses no analytics cookies, builds no advertising profile, and sends no analytics data to another company. This policy is not, however, zero: connecting your WhatsApp number and signing in with Google both hand you to another company for a moment, and both of those companies use cookies. Pretending otherwise would be the easy thing to write and the wrong thing to publish.
Everything below describes what this build does today. You can confirm all of it in your browser's developer tools in about a minute, and we would rather you did than take our word for it.
Our cookie
One cookie, and it keeps you signed in
automix_session — strictly necessary. Issued by accounts.automixai.in when you sign in, and sent back to us on later visits so you are not asked to sign in again on every page and every Automix subdomain.
- Lifetime: 30 days from your last sign-in or session renewal. Signing out ends it immediately.
- Scope:
.automixai.in, so one sign-in covers the dashboard and every agent subdomain rather than asking once per subdomain. - Protections:
HttpOnly, so page scripts cannot read it;Secure, so it is only ever sent over HTTPS;SameSite=Lax, which limits it on cross-site requests. - Contents: a random token. Not your email, not your name, nothing readable — it is a reference the server matches against its own record, and that record is revoked when you sign out.
There is no way to use a signed-in Automix account without this cookie. That is why the notice at the bottom of the site tells you about it rather than asking permission for it: refusing it and staying signed in are not both possible, and a consent control that cannot be honoured is worse than none.
Other parties
Two places where someone else's cookies appear
Both are inside the product, behind sign-in, and both start because you chose to start them. Neither happens on a marketing page and neither happens in the background.
- Connecting WhatsApp, on the Channels page. Linking your WhatsApp Business number uses Meta's own Embedded Signup flow, which requires loading Meta's JavaScript SDK from
connect.facebook.net. That SDK sets Meta's cookies, under Meta's policies rather than ours, and we cannot switch them off and still offer the flow — it is Meta's approved way of connecting a number. The SDK loads only when you open the Channels page, and only where Embedded Signup has been configured. If you never connect a number, it never loads. - Signing in with Google. Choosing Google sign-in sends you to Google, which sets its own cookies on its own domains under Google's policies. We receive only the identity token you approve. Signing in with an email address and password instead avoids this entirely.
One thing that is not a cookie but is still a third party, so we would rather name it than let you find it: our pages load their typefaces from Google Fonts. That request sets no cookie, but it does tell Google the IP address that asked for the font, on every page. We are moving these files onto our own servers so that stops being true; until that ships, this sentence stands.
What we do not set
No advertising or analytics cookies, no profiling
Automix AI does not set or permit:
- advertising or retargeting cookies;
- analytics cookies — self-hosted Umami counts first-party page views without cookies; there is no Google Analytics, Tag Manager, or Meta pixel anywhere in this site;
- cross-site or cross-device profiling of any kind;
- cookies that sell, share, or broker your browsing behaviour.
Umami runs on servers we control. It uses no session replay or heatmaps. It records page views and technical request data such as the requested path, referrer, browser, device, and IP address. See the Privacy Policy for how we use that information.
Our servers also keep ordinary request logs. That is not a cookie and happens whether or not you have one; it is also covered in the Privacy Policy.
Your control
Managing cookies
- Sign out from the account menu. This revokes the session on our side and clears our cookie across every subdomain.
- Clear them in your browser. Every browser can delete cookies for a site. Doing so signs you out; nothing else breaks.
- Block them entirely. Public marketing pages work normally. Signing in will not, because the cookie is what a signed-in session is made of.
- Avoid the third-party ones. Sign in with email and password rather than Google, and do not open the Channels page. Both are avoidable by choice; nothing loads them for you.
If we ever add analytics or any other non-essential cookie, the notice at the bottom of the site will ask for consent before it loads, and will re-ask everyone who only ever acknowledged this narrower version.
Changes
If this policy changes
A change that adds a cookie, widens what an existing one does, or extends its lifetime takes effect only after the effective date at the top of this page has been updated and the site-wide notice has been re-shown. We will not quietly broaden this page and rely on you to re-read it.
This page was corrected on 30 August 2026. An earlier version said Automix set one cookie and involved no third parties. The first part was accurate and the second was not, for the two flows described above. We are recording that here rather than editing it away.
Questions
Contact
Questions about this policy go to vivek@automixai.in, or any of the channels on our contact page. Related policies: Privacy Policy, Terms & Conditions, and our other policies.
Questions
Common questions
Do you use Google Analytics or a Meta pixel?
No. Neither appears anywhere in this site, and no analytics or advertising cookie is set. The only Meta code that ever loads is the Embedded Signup SDK on the Channels page, which exists to connect your WhatsApp number and not to measure you.
Can I use Automix without any third-party cookies at all?
Yes. Sign in with an email address and password rather than with Google, and do not open the Channels page. Then the only cookie involved is our own automix_session.
Why is there no cookie banner asking for consent?
Because there is nothing optional to consent to on a public page. Our one cookie is strictly necessary for signing in, and the two third-party cases only start when you deliberately begin a flow that needs them. If we add a non-essential cookie, a consent request appears before it loads.
Does the session cookie track me across other websites?
No. It is scoped to .automixai.in, so it is only ever sent to Automix. It contains a random reference, not your identity, and it is SameSite=Lax, which limits it on cross-site requests.