Where your data lives, in plain words
This page explains our restaurant POS data security in plain words: where your data is hosted, how it is backed up, who can see what, and how you take it with you. It also says clearly what we do not claim. We would rather you know the facts than read a wall of badges.

How we look after your data
Our own servers
The POS is hosted on servers we run and manage, not on a shared website host.
Daily backups
Your business data is backed up every day, so a bad day on a server does not mean lost menus or sales.
Roles for every user
Each staff member has a role that decides what they can see and do, such as voids, refunds and reports.
Service-staff PINs
Servers use their own PIN on shared tablets, so every order and void carries a name.
Per-location permissions
Managers can be limited to the locations they run, so one store manager does not see another's reports.
Card data stays with your processor
Card payments run on your processor's terminal. Card numbers do not come to our servers.
Export any time
Download products, customers and sales to spreadsheets whenever you want, no request needed.
Readable after you leave
After cancellation your account stays readable for 30 days so you can export everything.
Where is my restaurant's data hosted?
Your data is hosted on servers we run and manage ourselves. Your menu, sales, staff and customer records live there, and you reach them through the browser with your login. We back the data up every day. We do not sell your data or share it with advertisers.
Hosting on our own servers means we control the setup, the updates and the backups. When something needs fixing, our own team fixes it. Daily backups protect against mistakes and failures. If a server has a problem, we restore your business from the latest backup. Updates are tested before they reach your account.
Your data is used to run your POS and to support you. It is not used to market other restaurants' products to your guests. If you want a copy at any time, export it yourself from the back office in a few clicks. The export is yours to keep, store or hand to your bookkeeper.
- Servers run by our own team
- Daily backups
- Access by your login only
- No selling of your data
Who in my restaurant can see what?
You decide. Every user has a role, and the role sets what they can see and do. Servers ring orders with their own PIN. Managers can void, comp and refund. Owners see every report. Managers can be limited to the locations they run, and you can remove a user the moment they leave.
Most restaurant losses come from inside, not from hackers: an unexplained void, a refund at close, a shared login. Roles and personal PINs put a name on every action. Set the roles once. A host can manage bookings but not refunds. A bartender can open tabs but not change prices. Change a role and every user with it updates.
When someone leaves, deactivate their user before the next shift. Their old sales stay in your reports under their name. Review your users list every month. Remove anyone who has left, check that managers only see the locations they run, and make sure nobody shares the owner login. It takes five minutes and closes the most common gaps.
- Roles with permissions
- Personal PINs for service staff
- Per-location access for managers
- Remove users instantly
What happens to card data?
Card data stays with your processor. When you take cards on your processor's integrated terminal, the card number goes from the terminal to the processor, not to our servers. The POS records that a payment was made and its amount, which is what your reports need.
This setup keeps the most sensitive data with the company built to handle it: your card processor or acquiring bank. They set the card security rules for your account. Never type full card numbers into notes, customer fields or messages. If a guest phones in a card, use your processor's own tools for that.
We do not charge PCI fees, because card processing is not part of our service. Ask your processor what they require of you. If your bank or processor asks for a security questionnaire, they will mostly ask about card data. Point them to your processor's terminal setup and its documents, and tell them the POS does not store card numbers.
- Card numbers stay with your processor
- POS keeps payment amount and type
- No card numbers in notes or messages
- No PCI fees from us
Can I export or delete my data?
Yes. Export products, customers and sales to spreadsheets any time from the back office. If you cancel, your account stays readable for 30 days so you can download everything. After that, ask us to delete your data, or use the data request page if you are a guest asking about your own details.
Your data belongs to your restaurant. Export it monthly for your bookkeeper, or before a big change, without asking us. Guests sometimes ask what a restaurant holds about them. You can find and edit their customer record, and we help with deletion requests that reach us. No form or waiting period is needed.
We would rather you leave with all your data than stay because leaving is hard. We would rather you leave with all your data than stay because leaving is hard. Export files are plain spreadsheets, so they open in any spreadsheet program and can be imported into another system if you ever move.
- Spreadsheet export any time
- 30 days readable after cancelling
- Deletion on request
- Guest data requests supported
What security certifications do you have?
We do not claim any security certifications, such as PCI DSS, SOC 2 or ISO 27001. We describe what we actually do instead: our own servers, daily backups, roles and PINs, card data kept with your processor, and export any time. If your business requires a certification, ask us on a demo before you commit.
Many software sites show badges that are hard to check. We prefer to state the facts and let you decide. Because card numbers stay with your processor's terminal, your processor's certification covers the card side. Ask them for their compliance documents if your bank requires them. Those claims are easy to make and hard to verify.
If we ever gain a certification, it will be listed here with what it covers and the date. If we ever gain a certification, it will be listed here with what it covers and the date. Until then, this page describes our practices plainly, and we answer security questions honestly on a demo, including the ones we cannot say yes to.
- No certifications claimed
- Plain description of real practices
- Card side covered by your processor
- Ask us before you commit
What we do not claim
We do not hold PCI DSS, SOC 2 or ISO 27001 certifications, and we never say we do. Card payments run on your card processor's terminal or gateway, so card data stays with the processor that is certified for it.
Security questions
Onboarding desk · usually replies within a business day
Is my restaurant's data backed up?
Yes, every day. Backups let us restore your business if a server fails or data is damaged. You can also make your own copies by exporting to spreadsheets any time.
Can you see my sales numbers?
Our support team can access your account when needed to help you, for example to fix a setup problem you report. We do not use your sales numbers for marketing or share them with other restaurants.
What happens if a server leaves and knows a PIN?
Deactivate their user in the back office before the next shift. Their PIN stops working at once. Their old orders stay in your reports under their name.
Do you store guests' card numbers?
No. When you use your processor's integrated terminal, card numbers go to the processor, not to us. The POS only records the payment type, amount and reference.
Are you PCI certified?
We do not claim PCI certification. Card processing runs through your own processor, which handles card data and sets your PCI requirements. We do not charge a PCI fee.
How long do you keep my data after I cancel?
Your account stays readable for 30 days after cancellation so you can export everything. After that, you can ask us to delete it. Backups age out on their normal cycle.
Can I limit a manager to one location?
Yes. Per-location permissions let you choose which locations each user can see. A manager at one location will not see another location's sales or staff.
What should I do if I think someone used my login?
Change your password right away and contact support. Check the users list for anyone you do not recognize and deactivate them. Never share the owner login with staff; give them their own users.
Your data, your export button.
Start the free trial and download your data any time from the reports.