TapTime provides booking, menu, loyalty and appointment tools for restaurants, cafés, salons, barbershops, clinics and workshops. Guests use it to book a table, order from a menu or collect stamps; businesses use it to run those bookings from a panel. This policy explains, in plain language, what happens to personal data on both sides.
It applies to tapti.me and its country pages, to the business panel at app.tapti.me, and to the booking, menu and loyalty pages a venue publishes through us.
Who we are
TapTime is the service described above, operated by the company that runs tapti.me. For anything in this policy you can reach a person at [email protected], and we answer in the language you wrote in.
Where this policy says “we”, it means TapTime. Where it says “the venue” or “the business”, it means the restaurant, salon or clinic you booked with or work for.
Two relationships, two roles
TapTime sits between two kinds of people, and the answer to “who decides what happens to this data” is different for each. Getting this distinction right is what the rest of the policy depends on.
| Data | Who decides | Our role |
|---|---|---|
| Your TapTime account and website use | TapTime | We are the controller |
| A booking you make with a venue | That venue | We process it on their instructions |
| A venue's guest list, menu, loyalty program | That venue | We process it on their instructions |
| A business user's panel account and billing | TapTime | We are the controller |
In practice: we decide how the product itself works and keep your account safe. The venue decides what it does with the bookings and guest records it collects through us — including how long it keeps its own notes about you. If you want a venue's records about you changed or removed, ask the venue; if they ask us, we help them do it.
What we collect
We collect what the product needs to work, and we try not to collect anything else. Nothing here is sold, and nothing here is used to build an advertising profile of you.
- Guest account: your phone number, the one-time codes we send to verify it, your display name if you give one, and your language.
- Business account: your name, work email, password (stored hashed, never in readable form), role, and the businesses and locations you belong to.
- Bookings and orders: the time, party size or service, the specialist or table, notes you add, the venue, and whether you showed up.
- Loyalty: which cards you hold, stamp and reward history, and the rotating code your phone shows at the till.
- Menu orders: the items in a basket, the table or room, and the status of the order.
- Payments: subscription payments from businesses run through our payment provider, which handles the card details — we see the amount, the currency, the outcome and the last four digits, never a full card number.
- Device: operating system, browser, and the language your device is set to.
- Location: only if you allow it, and only to sort venues by distance — a coarse position, used at that moment and not stored as a trail.
- Support: what you write to us, the address you write from, and the page you were on when you wrote.
- Technical logs: IP address, request time and user agent, kept short-term to keep the service up and to stop abuse.
Why we use it, and on what basis
European data protection law asks for a lawful basis for each purpose. Ours are these.
| Purpose | What it uses | Basis |
|---|---|---|
| Signing you in and keeping the account yours | Phone or email, one-time codes, session data | Performing our contract with you |
| Making and keeping a booking | Booking details, name, contact | Performing the venue's booking with you |
| Running a loyalty card | Stamps, rewards, card codes | Performing the venue's program you joined |
| Confirmations and reminders | Contact details, booking times | Performing the contract; you can turn reminders off |
| Billing a business subscription | Company details, plan, payment outcome | Contract and our legal accounting duties |
| Keeping the service safe and available | Logs, device data, rate limits | Our legitimate interest in a working, unabused service |
| Product news to business users | Work email | Consent, or legitimate interest where you are already a customer — either way, one click to stop |
| Answering support requests | What you wrote, and the account it concerns | Contract and our legitimate interest in helping you |
Who else sees it
A short list, and it is the whole list.
- The venue you booked with sees the name, phone number and notes attached to that booking, and the staff of that venue can see it in their panel.
- Our SMS and push providers deliver the codes and reminders we send — they see the phone number and the message, and nothing else.
- Our payment provider handles business subscription payments and holds the card details we never see.
- Our hosting and error-monitoring providers run the servers and tell us when something breaks.
- Professional advisers, or an authority with a valid legal order, when we genuinely have to.
- A buyer or successor, if the business is ever sold — with this policy still applying to what they receive.
Every provider in that list works under a contract that limits them to what we ask them to do. None of them may use your data for their own purposes.
Where it is stored
Our servers and backups are in the European Union. Some of the providers above operate outside it; where that happens the transfer runs on the European Commission's standard contractual clauses or an equivalent safeguard, and we can show you which one on request.
How long we keep it
| What | How long |
|---|---|
| Your account while it is open | Until you delete it |
| A deleted guest account | Removed within 30 days, including tokens, devices and loyalty cards |
| Bookings and orders | Kept by the venue for its own records; hidden from your account as soon as you delete it |
| One-time codes | Minutes — they expire almost immediately and are not readable afterwards |
| Invoices and accounting records | As long as tax law requires, typically several years |
| Technical logs | Up to 90 days |
| Support messages | Up to 24 months, so a later question has its history |
Your rights
Wherever you are, you can ask us for these, and we do not charge for it.
- A copy of the personal data we hold about you, in a portable form.
- Correction of anything wrong — most of it you can edit yourself on the guest page.
- Deletion of your account and the data tied to it.
- Restriction or objection: tell us to stop a particular use, including any use based on legitimate interest.
- Withdrawal of consent at any time, without affecting what was done before you withdrew it.
- A complaint to your national data protection authority, if we have not put something right.
Write to [email protected] from the address or phone number on the account and we answer within 30 days. If the request concerns a venue's own records, we will tell you which venue to ask and help them respond.
Deleting your account
You can delete a guest account yourself, from the guest page, without writing to anyone.
Profile Delete account
That removes your account, sign-in tokens, devices and loyalty cards. What it cannot remove is a venue's own record of a visit you actually made — the name and phone you gave them for that booking stay with them, the same way they would if you had phoned. Business panel accounts are deleted by an owner from the team settings, or by writing to us.
Messages we send
Three kinds, and they are not the same thing.
- Service messages: the code that signs you in, a booking confirmation, a change of time. These are part of the booking and cannot be switched off while you have one.
- Reminders: before an appointment or a reservation. Turn them off per channel on the guest page, or in the venue's own settings if you work there.
- Product news to business users: occasional, one click to unsubscribe, never sent to guests.
Cookies and similar technology
We keep this deliberately small. The marketing site sets a cookie remembering which country and language you chose, so the switcher does not forget on the next visit. Signing in sets a session cookie.
We run no third-party advertising trackers and no cross-site profiling. Any analytics we use is aggregate — page counts, not people.
How we protect it
Traffic runs over TLS. Passwords are stored hashed with a modern algorithm and are not readable by us. Access to production data is limited to the people who need it, over individual accounts. Loyalty codes rotate so a screenshot of one is useless a minute later. Backups are encrypted.
If a breach ever affects your rights, we will tell the relevant authority within 72 hours and tell you directly when the risk to you is high.
Children
TapTime is for adults. We do not knowingly create accounts for children under 16, and if we learn we have, we delete the account. A parent booking a table for a family does not need a child to have an account.
Changes to this policy
When we change something meaningful, we update the date at the top of this page and, for changes that affect you materially, tell account holders by email or on the guest page before it takes effect. Older versions are available on request.
Contact
Questions, requests and complaints: [email protected]. Tell us the phone number or email on the account so we can find you, and write in whatever language you prefer.
Write to us and name the section. A person reads every message and answers in the language you wrote in.
Write to us