Privacy

This page describes what the Batcher website and the Batcher app actually send, in the version of them you are using right now. It is short because we collect little.

This website sets no cookies

No cookies, no local storage, nothing written to your device. The analytics on this site hold a random visitor id in memory for as long as the tab is open, and it is gone when you close it. Come back tomorrow and you are a new visitor to us.

That is why there is no consent banner. It also means we cannot tell how many people return, which we have decided we can live without.

What this website records

When you click through to create an account, that session's visitor id is added to the link, so we can tell that the sign-up came from this page. The two sites are on separate domains, so nothing else would connect them.

What the app records

Once you are signed in, Batcher records that certain things happened: an account was created, a recipe was saved, a batch was completed. Each event carries your user id, your organization's id, and its name.

It never carries the contents of your work. No recipe, ingredient, client or product names, no quantities, no costs, no supplier details. Those live in your own database and are not sent to any analytics service.

Your batch records, recipes and account details are stored on Google Firebase, which hosts the app itself. That is not analytics — it is where the product keeps your data so it can show it back to you.

Who processes the analytics

PostHog Inc., on their US cloud, as our processor. They are the only third party that receives any of the events described above.

How long it is kept

Analytics events are deleted after 12 months. Nothing in them identifies you as a person beyond the ids above, and the website's visitor id has already expired with your browser tab.

How to opt out