Mithran Website Cookie Policy
Last updated: 2026-08-13
Mithran, Inc. ("Mithran", "we") operates the mithran.ai website and its paths (the "Site"). This policy explains what the Site stores in your browser, when it stores it, and how you change your mind.
The short version
The Site sets no cookies unless you opt in.
We verified this on 2026-08-08 against the live Site. The response carries no
Set-Cookie header. Until you choose to turn analytics on, nothing is written
to your browser by the Site.
The Site uses no advertising cookies and no cross-site tracking cookies at any point, whatever you choose.
What this policy covers
This policy covers the Site: mithran.ai and its paths, including /docs/,
/aegis-method/, /case-studies/, /agentic-journey/, and /thank-you/.
It does not cover:
- The Aegis software. The licence we distribute it under governs that.
- The hosted Forge product, or any customer tenant data.
- The customer Data Processing Agreement and the product sub-processor list. Both are in preparation.
Read this policy with Privacy Policy, which describes what happens to information after it leaves your browser, and Terms of Use.
Cookies and local storage are not the same thing
This distinction matters here, because your consent choice is stored in local storage rather than in a cookie.
A cookie is a small file the Site asks your browser to keep. Your browser sends it back to the server with every request to that domain. A cookie carries an expiry date set by whoever created it.
Local storage is a separate area of your browser. It stays on your device and is never attached to a request. The server cannot read it. It has no expiry date, so it persists until the site rewrites it or you clear your browser data.
The Site records your analytics choice in local storage. That record never travels to us. It exists so that your browser knows, on your next visit, whether to start analytics.
Everything the Site stores in your browser
| Name | Type | Purpose | When it is set | Lifetime |
|---|---|---|---|---|
mithran_analytics_consent_v1 |
Browser local storage | Records your analytics choice as granted or denied |
Only when you pick an option in the analytics panel. Never before. | No expiry. Persists until you change the choice or clear your browser storage. |
ph_phc_oSFwX…_posthog |
Cookie. Secure. Scoped to .mithran.ai. |
Holds the analytics device identifier and the session identifier | Only after you choose to allow analytics | 365 days |
ph_phc_oSFwX…_posthog |
Browser local storage | Holds the remaining analytics properties, which do not fit in a cookie | Only after you choose to allow analytics | No expiry. Persists until you refuse analytics or clear your browser storage. |
The analytics library uses the same name for both, because it splits its data across the two. The identifiers live in the cookie and the rest lives in local storage. The full name ends in the public analytics project key, which you can read in the page source.
There are no other items. The Site sets no other cookie and writes no other local-storage key.
The 365-day figure is the analytics library's documented default, and the Site does not override it. Nobody has yet opened a browser and read the real expiry off the cookie, so confirm it before this policy publishes.
PostHog, Inc. is the analytics provider. It is a US company and the Site uses its US Cloud service.
What analytics captures
If you allow analytics, the Site records how the pages are used:
- Page views and page leaves.
- Scroll depth at 25, 50, 75, and 90 percent.
- Section views and heatmaps.
- Clicks, with the visible label of what you clicked.
- Named calls to action and contact intent.
- The destination domain of outbound links.
- Page performance timings, errors, and dead clicks.
What analytics does not capture
The following are turned off in the Site's code:
- Autocapture. The Site does not blanket-record every interaction with the page.
- Session replay. No recording of your session is made.
- Surveys.
- Console-log recording.
- Copied-text capture. What you copy from the page is not sent.
Two further protections apply to the events that are sent:
- Your IP address is not stored. The analytics event your browser sends does not contain your IP address. The analytics provider's servers do see the address your connection comes from, because every web server sees the address it is talking to, so we have set the provider's project to discard it rather than keep it, and we have turned off the feature that would derive your approximate location from it.
- Query strings and fragments are removed from page URLs and from referrer
URLs. Only the origin and the path are sent. Campaign parameters are the one
exception: if you arrive by a tagged link, the analytics library records
utm_source,utm_medium,utm_campaign, and similar values as their own properties, so that we can tell which campaign brought you here. - A link in email we send you may carry an opaque identifier in the URL. It is not a campaign parameter, so it is removed with the rest of the query string and is never sent to analytics. It reaches our server logs only, because those record the URL requested. Section 3 of the Privacy Policy describes it.
No profile is created for an anonymous visitor. Contact-form field values are never sent to analytics. When you submit the form, the Site emits one event carrying a generated submission identifier and nothing else.
The Site uses no advertising cookies and no cross-site tracking cookies. It shares nothing with an advertising network.
Do Not Track
The Site honours the Do Not Track browser setting. If your browser sends a Do Not Track signal, the consent panel does not appear and analytics does not start.
Changing your choice
Use the Analytics choices control in the Site footer. It is on every page. You can move from allow to refuse, or back, at any time.
You can also use your browser's own controls to block or delete cookies and to
clear local storage for mithran.ai. Clearing local storage deletes your
recorded choice, so the panel asks you again on your next visit.
Refusing analytics does not degrade the Site. Every page works the same either way.
Current state
As of 2026-08-08 the Content Security Policy served by the deployed Site blocks the PostHog script from loading. The practical effect is that no PostHog cookie is set on the live Site today, even for a visitor who allows analytics. Analytics is not operating.
This is a deployment state, not a commitment. It changes as soon as the pending infrastructure change is deployed. This section must be re-checked against the live Site on the day this policy is published, and corrected if the state has changed.
Questions
Write to privacy@mithran.ai.