Where your shop's data is

Everything happens in your browser

When you open a tool page, your browser downloads the page and the tool's code once. After that, making the QR, calculating the VAT, laying out the sign and producing the PNG file all happen on your device. Nothing you type is sent back to us — except in two cases you start yourself: pressing publish on a menu (section 7 below), and the paid slip-check service, which has to send the slip image to a server to be checked.

We have no database holding your shop name, PromptPay number, sales figures or product list from ordinary use of the tools, because that data never travels to us in the first place. The only thing we store is the menu of a shop you have told us to publish to a public link yourself.

It still works with the internet off

The easiest way to prove it is to try it yourself. Let the tool page come up completely first, then turn on aeroplane mode or switch off Wi-Fi and mobile data. Then carry on typing your shop name and PromptPay number: the QR still comes up, the sign can still be created, and the save-image button still works, because once the page has finished loading, no step needs the internet any more.

A limit we have to state clearly: if you turn the internet off, close the tab, and then open the page again while you still have no internet, the page won't load, because at the moment we haven't made a version that installs onto the device. What works with the internet off is the stretch while the page is already open.

So where is the information you filled in kept?

So that you don't have to type your shop name again in every tool, we keep the information you fill in in the browser's own storage (localStorage), which is on your device, not with us. You can clear it yourself by clearing website data in your browser.

An important warning: on iPhone and iPad, the Safari browser deletes this data automatically if you don't visit this site at all for about 7 days in a row. This is Safari's own behaviour, not something we chose. If you have filled in a lot of shop data, press the button to download a backup file of your shop data and keep it on your device, then you can restore it any time.

What we don't do

• No ad scripts, no third-party tracking tools, and no cookies for tracking users.
• We don't force you to enter an email or phone number before using it.
• We don't keep the slips or the images you choose. Images you put into a poster are shrunk down on your device and are not uploaded.
• We don't show made-up reviews or made-up user numbers. Every example shop on this site says clearly that it is a fictional shop.

What the tools can't help with, and you have to check yourself

The PromptPay QR we make for you is always correct to the standard, but there is no way for us to know whether the number you typed is really yours. If you type one digit wrong, the QR will still scan — but the money will go into someone else's account.

Because of this, the scan-to-pay sign tool page has a step where you scan the QR on the screen with your own bank's app and check whether the payee name matches you, before you print it out and put it up at the shop. Please do this step every time you change the number.

What we count: the number of times each tool is used

We want to know which tools people really use and which tools nobody uses, so that we can put our time into fixing and improving the right one. So we count two things per opening: the moment the tool page has come up and is ready to use, and the moment you press print, press save image, press share, or press copy text.

There are only four things that get sent: the version number of the data format, whether it was an opening or a use carried through to the end, the name of the tool (for example, scan-to-pay sign), and whether the screen being used is a phone or a computer. That's all.

What does not get sent: shop name, PromptPay number, amounts, product list, or any text you type. No cookies, no identifier or session ID, no IP address, no address of the web page you came from, and no time more precise than the day. So all we can say is how many times this tool was used today — we can't say who used it.

If your browser has Do Not Track or Global Privacy Control turned on, we don't count you, automatically. And if you want to turn it off just for this device, go ahead and press the switch below. The numbers we get we keep to look at ourselves, internally — we don't put them up on the site as numbers to show off.

The one exception: when you press publish

The QR menu tool has a “Publish menu to a link” button. Pressing it sends your shop’s menu — shop name, tagline, categories, dishes and prices — to us, so we can create the public menu page your customers open when they scan the QR. That is what publishing means. We write it here so you do not have to guess.

This is the only place in any of the tools where what you type leaves your device, and it happens only when you press that button yourself. Nothing is saved to a server automatically, nothing syncs in the background, and no request is made when the page loads. The other thirteen tools have no such button at all.

There is no sign-up and no login. When you publish, we generate one edit code. That code is the key to the menu page — whoever holds it can edit or delete that page. We store only a one-way encrypted value (a hash) of it, so there is no way for us to give the code back to you. If you lose it, the menu page stays online but can no longer be edited; the only way forward is to publish a new one.

The edit code is never printed on a table card or a paper menu, because everything on a table card is visible to every customer. We offer it as a recovery file to keep on your own device instead. And a published menu page is not added to Google’s index until it has a shop name, a way to get in touch, and a location.

If you change your mind, the tool has a button to take the menu page offline at any time. The draft on your own device stays exactly as it is.

Demo clip

We're filming a short clip demonstrating turning the internet off and carrying on using the tool, so that you can see it really is the way it's written here. It will go up here.