Privacy

The short version

We do not keep your spreadsheet, and we never see the data you put in it. You tell us what you want to track, we design the structure, and you download an empty file. Whatever you type into that file afterwards stays on your own computer and never comes near us.

There is no database here. The few things this service does hold are listed below, and none of them lasts longer than a few minutes.

What happens to what you type

Your description goes to Anthropic's Claude API, which designs the structure and sends it back. It is sent as something to work on rather than as an instruction, so a description cannot tell this service to do anything. Anthropic handle it under their own terms.

Once the reply comes back, we have no further use for what you wrote and nothing here keeps a copy of it. It is not sent anywhere else and no part of it is used to improve this service.

While we are building it

Promising that the formulas work means actually checking them, and checking them means opening the spreadsheet. So we write the file into a temporary folder on the server, open it with LibreOffice, read the answers back, and delete the folder. That takes a few seconds and nothing survives it. It is the one point at which your spreadsheet touches a disk, and we would rather say so than let you assume otherwise.

Designing one takes a minute or two, which is long enough that you might lock your phone or switch apps while you wait. So the finished design waits for you to come back for it. It waits in memory, never in a file and never in a log. The first time you collect it, it is deleted. If you never come back, it is deleted within ten minutes anyway. It sits behind a random ticket of 32 bytes that only your browser is given, so nobody can collect somebody else's.

What your browser keeps

The design lives in your own browser between requests, which is why asking for a change sends it back to us each time. Your browser also keeps the ticket for anything still being built, and, if this service charges for downloads, a permit that lets you download the one you paid for.

All of that lives in session storage, which your browser empties when you close the tab. None of it goes anywhere except back to us when you ask for a change or a download.

The file itself

When you press download, the file is built in memory and sent straight to you. No copy is written to disk and no copy is kept.

What we write down

Every request gets a random identifier. We log that identifier alongside facts about the shape of the request: how many characters your description was, how many tabs the result had, how long it took, whether it worked. Never the words, never a formula, never a value. That is enforced in the code rather than left to good intentions: the function that writes a log line refuses any field that could carry your content.

The web server also keeps the ordinary access log that every web server keeps, with the time, the address a request came from, the path and the result. Because there is a hosting company in front of us, the address in that log is usually theirs rather than yours.

To stop one person using up the service, we count recent requests per address. For an ordinary address we count per address; for the kind handed out in large blocks we count per block, because otherwise the count would mean nothing. That count lives in memory only. It is never written to a file, it never appears in a log, and it is dropped once it has stopped telling us anything.

Cookies and tracking

There are none. No cookies, no analytics, no tracking pixels, no advertising and no scripts from anybody else. Every page loads only from this site. The only thing we ever read from the address bar is the payment reference that Stripe sends you back with, and we remove even that as soon as we have used it.

If you pay

Payments are handled entirely by Stripe, on Stripe's own pages. Your card details never reach this service and we could not see them if we wanted to.

What we send Stripe is the amount, the currency, a product name and a fingerprint of the design you are buying. The fingerprint is a hash, which only works in one direction, so it tells Stripe that you bought something without telling them what. Stripe will ask you for an email address so they can send you a receipt, and that stays with them. They keep the payment record, as they are required to, and their own privacy notice covers what they hold.

When you come back from paying, we ask Stripe whether that payment really completed before handing over the file. We do not take your browser's word for it.

Where it runs

On servers rented from a hosting company, who can see the traffic reaching us in the ordinary way that any host can. They do not get a copy of anything described above, because there is no copy to give them.

Your rights

You can ask what personal information we hold about you and ask us to delete it. In almost every case the honest answer is that we hold none. There was never an account, nothing you typed was kept, and the only thing ever tied to you was a count of recent requests that has long since been thrown away. If you paid, Stripe holds that record, and we will point you to them.

Getting in touch

Email Kelvin.kamau@bearx.co.uk.