Back to Edgify

Cookie Policy

Edgify uses a small number of cookies. This page lists each one, what it does, and how to control it.

Last updated 11 August 2026

1. What cookies are

Cookies are small text files a website stores in your browser. Edgify uses them for two purposes only: keeping you signed in, and understanding how the product is used.

Edgify does not use advertising cookies, tracking pixels, or third-party marketing cookies, and does not sell information about you.

2. Essential cookies

These are required for the service to work. Without them you could not stay signed in.

better-auth.session_token

Keeps you signed in as you move between pages. Without it you would have to sign in again on every request. Set only after you sign in, and cleared when you log out.

This cookie is set by our authentication library when you sign in. Its lifetime is that library's default; Edgify does not override it, so no fixed duration is stated here rather than one that might drift out of date.

3. Analytics cookies

These help us understand which features are used so the product can be improved. They are not required for Edgify to function.

ph_<project>_posthog

Set by PostHog to recognise a returning browser so that repeated visits are not counted as separate people. Contains a random identifier, not your name or email address.

Analytics is deliberately limited: automatic capture of clicked-element text is disabled, session recording and replay are disabled, and no document text, generated content, concept names or file names is ever included. Browsers sending a “Do Not Track” signal are respected, and no analytics cookie is set for them.

4. Controlling cookies

You can block or delete cookies through your browser settings, and you can enable “Do Not Track” to opt out of analytics.

Note that blocking the essential sign-in cookie will prevent you from signing in, because that cookie is the mechanism by which Edgify recognises your session. The public pages — including the landing page, the demo and these legal pages — work without any cookie at all.

5. Changes

If the cookies Edgify uses change, this page will be updated. The date at the top records when it was last revised.

Contact

Questions about this document, or about how Edgify handles your information, can be raised on GitHub Issues. Please do not include private study material or personal details in a public issue.

Privacy PolicyTerms of ServiceCookie PolicyAI Disclaimer