Privacy Policy

Tillwise is a business-management application for independent retailers — daily till reconciliation, supplier and expense tracking, staff hours, staff purchase accounts, and reporting, used by convenience stores, off-licences and similar small businesses to run day-to-day operations across one or more stores.

This notice covers two different groups of people, and it's worth being clear about the difference:

• Account holders — people who sign up for Tillwise, log in, and use it to run their business. This is the group Tillwise has a direct relationship with.
• Staff whose information is entered into Tillwise — an account holder's employees, whose name, pay details, hours or purchase-account activity a business may record in the app. Tillwise does not have a direct relationship with these individuals unless they are separately invited to log in themselves. The business using Tillwise is responsible for that information and for telling its own staff how it's used — see "Staff information entered by business users" below.

To create and operate an account, Tillwise collects your email address, and a password (or, if you choose to sign in with Google instead, an authentication token from Google — Tillwise never sees or stores your Google password). We also keep a record of which businesses and stores you're a member of, and your role within each (for example, owner, admin, or staff).

When you set up a business in Tillwise, you provide details such as a legal and trading name, business type, currency and country, and details for each store (name, address, and till float settings). This information is used to run the application on your behalf and is visible only to members of that business.

If you add staff records in Tillwise, this can include a staff member's name, contact details, pay rate and pay type, overtime terms, start date, and hours worked. If your business uses the Staff Accounts feature, it can also include a running record of what that staff member has purchased through the business (deducted from wages), payments made, and adjustments.

This information is entered and controlled by the business using Tillwise, not by Tillwise itself. If you are a business owner or manager entering staff information, you are responsible for having a proper basis to do so (for example, as part of your employment relationship with that person) and for telling your staff what information about them is recorded and why — Tillwise simply stores and displays what you enter.

The day-to-day records a business creates while using Tillwise — daily till closes, cash and card totals, supplier invoices and payments, business expenses, shift entries, and the reports generated from them — are stored so the business can review, correct and report on its own operations over time.

Tillwise uses Supabase Auth to handle sign-in. This involves a session token, stored in a cookie in your browser, that proves you're logged in on subsequent requests without you having to re-enter your password on every page. See "Cookies and similar storage" below for exactly what's stored.

Like any web application, ordinary server-side request logs and error logs are generated as Tillwise runs, to help diagnose problems. Tillwise does not run any analytics, advertising or user-tracking software — see "Cookies and similar storage" below.

Information is processed only for purposes connected to running the service, specifically to:

• Provide the service — store and display the records your business enters, calculate totals and balances, and generate reports and statements.
• Authenticate you — confirm who you are and which business/store data you're allowed to see.
• Maintain security and prevent misuse — for example, restricting actions to the roles permitted to take them, and investigating suspicious account activity.
• Troubleshoot problems — diagnose bugs or errors reported by users, using server logs and error messages.
• Operate and improve the product — understand how the application is used in aggregate (for example, which pages are slow) so it can be made faster or more reliable.
• Meet legal obligations — where Tillwise is required to retain or disclose information by law.

Tillwise is built on a small number of third-party infrastructure providers who process data on our behalf, strictly to provide the service:

• Supabase — our database, authentication and file-storage provider. All account, business, staff and operational data described above is stored in a Supabase project.
• Vercel — hosts and serves the Tillwise web application.
• Google — only if you choose "Continue with Google" to sign in, in which case Google acts as an authentication provider for that sign-in only.

Tillwise does not sell information to third parties, and does not share it with anyone for their own marketing purposes.

Tillwise's infrastructure providers (Supabase and Vercel) may process and store data in the United Kingdom, the European Economic Area, or other countries where they operate, subject to those providers' own data protection safeguards. If you have questions about where a specific provider processes data, contact us using the details below and we'll point you to the relevant information.

Information is kept for as long as your account and business remain active on Tillwise, so that you can continue to rely on your own historical records (for example, past daily closes or staff account statements). If a business account is closed, information may be retained for a reasonable further period to meet accounting, legal or dispute-resolution needs, before being deleted. Tillwise does not currently commit to a fixed number of days or years for every category of data — if you need a specific record deleted sooner, contact us and we'll handle it manually, subject to the legal and accounting exceptions described here.

Access to business data is restricted by account membership and role — a user only ever sees the businesses and stores they belong to, and some actions are restricted to specific roles (for example, deactivating a staff member). Traffic to Tillwise is served over HTTPS. As with any online service, no method of storage or transmission can be guaranteed completely secure, and we don't claim otherwise — we take reasonable, proportionate steps for a service of this size, and we'll tell affected users if we become aware of an incident that puts their information at risk.

If you are an individual whose information Tillwise processes, you have rights including the right to:

• be told what information is held about you and why;
• request a copy of it;
• ask for inaccurate information to be corrected;
• ask for information to be deleted, subject to any legal or accounting reason it needs to be kept;
• object to, or ask us to restrict, certain processing.

If you're a staff member whose details were entered into Tillwise by an employer, the quickest route for most of these requests is directly to that business, since they control what was entered — but you can also contact Tillwise directly and we'll help route the request appropriately.

Tillwise does not currently have a self-service "delete my account" feature. To request access to, correction of, or deletion of your information, email support@tillwise.example. We'll confirm receipt and deal with your request without undue delay.

Tillwise uses two kinds of browser storage, both essential to the app working, and nothing else:

• Authentication session cookies, set by Supabase Auth, which keep you signed in between page loads.
• A store-selection cookie, which remembers which store you last chose in the store switcher, so it doesn't reset every time you navigate.

Tillwise does not use advertising, tracking or analytics cookies, and does not run any third-party analytics or advertising scripts.

If this notice changes in a way that materially affects how information is used, we'll update the "last updated" date at the top of this page. Continuing to use Tillwise after a change means you accept the updated notice.

For any question about this notice or how your information is handled, email support@tillwise.example.