Privacy policy

Mini Till ("we", "us") operates mini-till.co.uk. This policy explains what personal data the site and the paid stock system handle, who else handles it for us, and what you can ask us to do about it.

1. Who is responsible for what

For visitors to this website, and for the account details of the person who signs a team up (their name, email address and billing details), we decide why and how the data is used, so we are the controller.

For everything a business puts into the paid stock system about its own staff, customers and trade (members' names and roles, products, stock, sales and shifts), the business is the controller and we are its processor. We use that data only to run the service for the business and on its instructions. If you are a member of a team and want to see or correct your own data, ask the person who runs your team first. We will help them answer.

2. The free till

Everything you enter into the till (products, prices, sales and settings) is processed and stored in your browser's local storage on your own device. None of it is sent to us or to anyone else. We cannot see it, back it up or recover it.

• Clearing your browser data permanently deletes your products and sales history, so download a backup from the till regularly.
• The "share product list" feature encodes your product names and prices into a link. Anyone you give that link to can import the list. Nothing is stored on a server.
• When you open the till, your browser fetches the till's page and files from our server and its styling library from cdn.tailwindcss.com, so that service sees the request, including your IP address, as any website would. That request carries none of your till data.

Anonymous usage counts

So we can see which parts of the till people use and what to improve, the free till sends us a small report now and then, only when there is something new to count. The first one waits until the till has been open for 20 seconds, or has been used, so the line about it at the top of the till has been on screen first. A report can say:

• that the till was used today, this week or this month, so each device is counted once per day, week and month;
• roughly how long ago the till was first used on this device, and roughly how many products it has, in broad bands such as "1 to 9 products";
• whether it is a phone, tablet or computer, and whether the till was opened as an installed app;
• how many sales were rung up since the last report, how many were paid by card, cash or a split, and how many had a discount;
• how many times features such as Reports, backups, CSV import, printing a receipt or sharing a product list were used;
• milestones, such as the first product added, the first sale, or coming back on another day.

A report never contains an amount of money, a product name or price, a business name or anything else you typed in, and it carries no identifier for you or your device. We add each report to that day's totals and keep nothing else from it in the database: not your IP address and not your browser. Your address is held in the server's memory so that one address cannot send hundreds of reports, and is cleared about ten minutes after its last report. Our web server's ordinary access log (section 5) records the request, as it does for any page. The totals are not shared with anyone.

To count a device once a day without an identifier, the till keeps a small record in your browser's local storage: the date it was first used on this device, the last day, week and month it was counted, the time of the last report, which milestones it has reached and how often each feature was used since the last report. If you tick or untick the box in Settings, it also keeps that choice. None of this leaves your device except as the counts above.

You can object at any time, free and in one step:

• untick Share anonymous usage with Mini Till under Settings on the till's Products tab, which also deletes the record from your device;
• or answer No to the measurement question in our cookie notice;
• or turn on Do Not Track or Global Privacy Control in your browser.

Each of these stops the reports. Ticking the box in Settings turns counting back on despite the objections that stood when you ticked it; a No or a browser setting that comes afterwards stops it again. Reports stop when the till joins a team in Team Mode, because those sales go to your team's account as described in section 3: the last report says the till has joined. The law allows counting like this without asking first, because it is only for statistics about how the till is used, it is not shared, and you can object (the Privacy and Electronic Communications Regulations, Schedule A1, paragraph 5).

3. Mini Till Pro and Mini Till Teams

The paid stock system needs a server, because it keeps several tills in step against one stock. When a team signs up and uses it, we store:

• The team name, its locations and its product catalogue
• Each member's name, role and sign-in details: an email address for members who sign in by email, and a password or PIN, which is stored only as a salted hash and never in plain text
• When each member signed in
• Stock movements, deliveries, transfers, waste and stocktakes
• Sales and shift records (floats, cash-up figures) sent from tills linked to the team
• For billing: your Stripe customer reference, plan, price, subscription status and billing period

We use this data to provide the service to your team, to bill you, to keep the service secure and to answer support requests. We do not sell it, use it for advertising or share it with anyone other than the providers listed below. The team owner chooses who is added and what role they have.

Setup emails. In a new team's first two weeks we may send the owner up to five short emails about setting it up, such as adding products or connecting a till. Each one is sent only if that step has not been done yet, so we look at whether the team has products, stock, sales and members, but not at the detail of any of them. Every email has a link that stops the rest, and they stop by themselves after the first two weeks. Members other than the owner get none.

4. Who else handles data for us

We use these providers. Each receives only what it needs for its job.

• DigitalOcean hosts the service. The application runs as a Node server with a SQLite database on a server we rent from DigitalOcean, which we manage using Laravel Forge. The database holds the data described in section 3.
• Stripe takes payment for subscriptions. It receives the owner's email address and the team name, and the card details you type into Stripe's own checkout. Mini Till never sees or stores your card details.
• Resend sends the emails the service needs: password reset emails to members, setup emails to a new team's owner (see section 3), messages sent to us through the contact form and our replies to them (see section 13), and notifications to us about the running of the service. It receives the recipient's name and email address and the content of the message.
• Google provides Google Analytics and Google AdSense, only on the terms in section 6.

5. Visiting the website

The site counts page views: how many times each page was opened on each day, and which site the visitor came from (the referring site). These counts are aggregate only. We do not record IP addresses, set cookies or store any identifier for this, so a count cannot be traced back to a person.

Separately, the web server keeps ordinary access logs (which include IP addresses and the pages requested) for security and to diagnose faults. We use them for nothing else.

6. Analytics, advertising and cookies

Analytics. We use Google Analytics to count visits. It is set up so that no analytics cookie is stored until you agree. When you first visit, a notice from us asks, and you can answer yes or no. Declining is as easy as agreeing. Your answer is kept in your browser's local storage on your device and is not sent to us. Until you agree, Google Analytics runs in a restricted mode that sets no cookies, although Google may still receive basic, non-cookie information about the visit.

Advertising. The free content pages are partly paid for by Google AdSense. Advertising consent is a separate question that our notice does not ask: on this site the three advertising consent signals are set to denied by default. Where Google's own certified consent notice is shown, that notice, not ours, records your choice. Adverts appear on the home page, About, FAQ, the guides, the blog and the stock control page. There are none on the till, the pricing page, the contact page, this policy or the terms.

• You can opt out of personalised advertising by Google at Google Ads Settings.
• You can opt out of some third party vendors' use of cookies for personalised advertising at www.aboutads.info/choices.
• For more on how Google uses data from sites that run its adverts, see the Google privacy policy and Google's partner sites notice.

We set no advertising cookies of our own, and nothing you enter into the till or the stock system is passed to any advertiser.

Your cookie choices

You can change your analytics choice at any time with the Cookie settings link in the footer of any page. You can also control and delete cookies in your browser settings. The till itself does not use cookies. It keeps the small usage record described in section 2 in local storage, unless you turn usage counts off.

7. How long we keep data

• Free till: we hold none of your till data. It stays on your device until you delete it. The anonymous usage counts are kept as daily totals, which contain no personal data.
• An active paid team: we keep its data while the subscription runs. People the owner deactivates are kept in the records so that past sales and stock history stay correct, but they cannot sign in and do not count towards the five-person limit on Pro.
• After cancelling: nothing is deleted. The team becomes read-only: its members can still sign in, see everything and export every table to CSV. If you subscribe again it carries on where it left off.
• Deletion: email us and we will delete your team's data and your account details, within 30 days. We may keep what the law requires us to keep, such as invoices and payment records held by Stripe.
• Messages you send us through the contact page or the help forms are deleted after 12 months (see section 13).
• Page-view counts contain no personal data, so they are kept as totals.

8. Your rights

Under UK GDPR you can ask to see, correct, delete, restrict or object to the use of personal data we hold about you, and to receive it in a portable form. For the free till we hold no personal data: your till data is already on your device, and the usage counts cannot be linked to you. For a paid account, email us and we will act within 30 days. If you are a member of a team rather than its owner, see section 1.

9. Security

The site and the service are served over HTTPS. Passwords and PINs are hashed, a person's role is checked on every request so that removing them takes effect immediately, and roles limit who in a team can see or change what. No system is perfectly secure, so we hold as little as we can.

10. Children

The site is not aimed at children under 16 and we do not knowingly collect their personal information.

11. Changes to this policy

If this policy changes, the new version appears here with a revised date. If a change affects how we handle a paid team's data, we will email the team owner.

12. Contact and complaints

Questions or requests: hello@mini-till.co.uk or the contact page.

If you believe we have mishandled your data, you can complain to the Information Commissioner's Office: ico.org.uk/make-a-complaint, 0303 123 1113.

13. Messages you send us

The contact page, the "Need a hand?" form in the free till and the Help screen in the stock console all send a message to us. Sending one is the only time the free till shares anything with us, and only what you type into that form.

• What we keep: your name, email address, the topic you chose and your message, the page you sent it from, and a short description of your browser and device (for example "Chrome 130 on Android"). If you send it from the stock console while signed in, we also keep which team and member it came from, so we can find your account. If we reply from our console, we keep the reply with your message. We do not keep your IP address with it.
• Where it goes: into our database, which is described in section 4, and by email to our support inbox through Resend. If the email cannot be sent, the message is still kept and we see it in our own console. We do not send an automatic reply to the address you give. When we answer, a person writes the reply, and it is emailed to you through Resend with your message quoted under it.
• How long: 12 months, after which it is deleted automatically from our database, along with any reply we sent you from our console. The email we receive about it also sits in our own mailbox and in Resend's sending logs, which we clear by hand and Resend keeps for its own period. Our database backups keep deleted rows until they rotate out, 14 days by default. You can ask us to delete it sooner, as in section 8, and we will remove it from the database and our mailbox.
• What we use it for: replying to you, and looking back at what was asked so we can fix problems and improve the product. We do not use it for marketing or share it with anyone else.