Cookies,all four of them.

Epafi sets no analytics cookies, no advertising cookies, no cross-site trackers, and no profiling identifiers. There are no third-party pixels on the marketing site and none on authenticated pages. That is not a temporary state we intend to quietly reverse — it is the same commitment made in the Privacy Policy.

The ePrivacy Directive requires consent before storing or accessing information on your device, except where that storage is strictly necessary to deliver a service you asked for. Every cookie listed below falls inside that exception, which is why you are not shown a consent banner. If we ever add a cookie that does not, the banner arrives first and nothing is set until you accept.

Two parties set cookies on epafi.app: Epafi itself, and Clerk, our authentication provider. Nothing else has access to your browser storage.

Clerk controls the exact composition of its own cookie set and may adjust names as its service evolves; the current authoritative list is published in Clerk’s documentation. We update this table when we observe a change.

The application also uses browser storage that is not transmitted to any server. It is covered by the same rules as cookies, so it is listed here:

• +Theme preference — remembers whether you chose light, dark, or system appearance.
• +Local query cache — holds the data already rendered on screen so navigating back does not refetch it. Cleared on sign-out.

This is the control surface linked from every page footer. It reads the cookies on this device and lets you remove the optional one.

Every major browser lets you block or delete cookies per site, and the Global Privacy Control signal is honored the moment we have anything to apply it to — see our Do Not Sell or Share page.

Blocking the cookies in the table above will sign you out and prevent you from signing back in. The application cannot function without a session cookie, and we do not fingerprint devices as a workaround.