Cookie policy
What is stored in your browser, why, and what refusing changes.
Not reviewed by counsel. Not in force.
This document has been drafted to describe what the product actually does, and it has not been reviewed by a qualified lawyer. It is published here so that it can be read, checked against the system, and corrected — not so that anybody can rely on it.
Nothing in it takes effect, nothing in it is an agreement, and no date has been set for either. Where it describes a practice, that description is accurate today; where it states a term, that term has not been settled.
If you need any of these in force before contracting — a data processing agreement, usually — say so and you will be told where the review has got to. Write to privacy@taxorch.com.
The short version
Nothing that observes you is stored before you agree to it. The site works completely if you never agree, and refusing costs you no functionality at all.
There is no advertising technology and no cross-site tracking on this site, so there is nothing to opt out of beyond what is listed below.
What is stored without consent
These are stored in your browser because the site cannot behave correctly without them. None of them leaves your browser and none identifies you — and none of them is a cookie sent to a server. They are local storage entries, which is a meaningful difference: a cookie travels with every request, and these do not.
| What | Why | How long |
|---|---|---|
| Your consent decision | So you are not asked again on every page, and so a change to this policy can ask again | Until you clear it |
| Your theme | So the site does not change appearance between pages | Until you clear it |
| Your motion preference | So animation stays off if you have turned it off | Until you clear it |
| Dismissed prompts | So a prompt you closed is not shown again during the same visit | Until you close the tab |
What is stored only with consent
Analytics. If you agree, the site records which pages and sections were read, which actions were pressed, and how forms progressed. These are event names and categories: there is no field in the event model capable of carrying what you typed, and an event carrying anything that looks like an address or a sentence is refused before it is sent.
A variant identifier. If an experiment is running and you have agreed to analytics, a random sixteen-character identifier is stored in a cookie so you see the same version of a page on each visit. It is not joined to anything and it is never sent to an analytics provider — what is reported is which version you saw, not who you are.
There are no experiments running, so no identifier is created. Consent permits one; it does not require one.
Changing your mind
Withdrawing consent stops the thing rather than stopping the next page from starting it, and the variant identifier is removed from your browser when you withdraw it. A framework that stops reading a cookie but leaves it on your machine has honoured nothing.
The preferences link in the footer reopens the decision at any time.
Third parties
None. No advertising network, no social pixel, no session recorder and no third-party analytics provider is loaded by this site — and while no analytics provider is configured at all, consenting to analytics results in nothing being sent anywhere.
How changes will be communicated
- Every version carries the date it took effect, and every earlier version stays reachable at the same address.
- A change is summarised in the terms a reader would care about. “Updated our terms” tells nobody anything and is why change notices go unread.
- A material change is notified to account holders in advance, not announced by a banner after the fact.
- Continuing to use the product is not treated as agreement to a change that was never sent.