Cookies

FreeFiler uses essential cookies needed for sign-in, account security, and keeping you signed in while you use the service. These are currently provided through Clerk authentication.

We do not currently use PostHog analytics. It is switched off in the code, and nothing about how you use FreeFiler reaches PostHog while it is off. Analytics are not needed to provide the filing service, so they need your consent — and accepting our terms is not consent. We will ask you properly, and publish an updated privacy policy, before we switch anything on.

Support replay, which would let us watch a masked recording of a filing session, is switched off in the code too, on the same terms: we will ask first and publish an updated privacy policy before it could ever run.

During beta, FreeFiler also keeps an internal interaction journal with structured form events such as checkbox choices, select/gate answers, validation state, and save or submit blockers. It is not a cookie, and it is not yet deleted on a timer; our privacy policy says how to have it deleted. Exact sensitive filing values stay in FreeFiler's own filing systems. We do not use advertising or marketing cookies in this filing app.

During early beta, FreeFiler may also generate a short-lived monitoring evidence link for a signed-in filing journey, for an OpenAI-hosted Codex agent or an Anthropic-hosted Claude agent to review. This is used to check whether the filing path is working and to support early users; it is not used for advertising.