Cookie policy

The cookie we use

It is set the first time you open Taxerly or ask it a question. It is sent only to Taxerly's own address on this site (/api/taxerly), over HTTPS only, and page scripts can't read it.

Because Taxerly can't keep its daily limit without it, it counts as strictly necessary for a service you choose to use, so it doesn't need your consent. If you block or delete it, the limit still applies through a salted hash of your IP address (see the privacy policy).

Other storage in your browser

When you type a question into an "Ask" box or the search palette on another page, the site keeps it for a moment in your browser's session storage (taxerly:pending-question) so Taxerly can open with it, rather than putting it in the address bar. Taxerly removes it as soon as it reads it, and the browser clears session storage when you close the tab. It never leaves your browser except as the question you asked.

What we don't use

No analytics, advertising, social media or tracking cookies, and no third-party scripts. Fonts are served from our own domain, so loading a page doesn't contact Google or any other font service.

If we ever add analytics, it will run only after you agree in a consent banner, and this page will list it first.

Managing cookies

You can see and delete cookies in your browser's settings. Deleting taxerly_anon does no harm: a new random ID is created the next time you use Taxerly.