Privacy Policy
What we collect, why, who else touches it, how long we keep it, and how to ask for a copy or for deletion.
Draft: a lawyer has not reviewed this yet.Last updated 11 October 2026About 6 min to read
TablaOne policies
1Who this covers
This policy covers TablaOne, the ordering service for restaurants in Nigeria, and everyone whose data passes through it: restaurant owners and staff, and guests who order at a restaurant or on their way to one. It is written with the Nigeria Data Protection Act 2023 in mind. It does not claim that TablaOne has been audited or certified under that Act or any other standard.
Guests pay a restaurant by bank transfer into its own account or, where TablaOne offers them, through Paystack or vyyBe Bank. Paystack and vyyBe Bank each have their own privacy terms for their services, accounts and wallets.
2What we collect
Restaurant owners and staff
- Name, email address and phone number.
- A hash of the password. We never store the password itself.
- The country, whether the person signing up is the owner, and their role if not.
- The business's name, kind, cuisine, address, area and city, and each branch's name, address and hours.
- To verify the business: its registration number and registration certificate, and what the registration lookup returns (registered name, status, address and directors). The names of its directors or proprietors, and for each of them and the owner an ID: its type, number, expiry date and a photo. ID numbers are stored encrypted and only their last four characters are ever shown.
- To approve a payout account: a bank statement, the account name read from it and how closely it matches the registered name.
- Food safety permits and licences: their type, expiry date and file.
- The merchant agreement: which version was accepted, who accepted it and when, and the payout schedule chosen.
- To pay the restaurant: the number and name of the vyyBe Business account the owner links, or the bank, number and name of the account TablaOne pays out to and of each account guests transfer to. Bank account numbers are stored encrypted and shown back to staff with only their last four digits. We do not ask for a BVN or a selfie. The number on a National ID card is a NIN, and we store it like any other ID number; we do not check ID numbers with a government database.
- Each payout TablaOne sends: the amount, the orders it covers, the date and the bank's reference.
- The role each person holds and, if turned on, a two-factor secret and backup codes.
Customers with an account
- A first name, a phone number or an email address (or both), and a hash of the password. Neither is checked when the account opens. A code sent to the email confirms it when the customer resets their password or asks to confirm it; only a confirmed email or phone finds orders placed before the account existed.
How we protect identity documents, statements and permits
Registration certificates, ID photos, bank statements and permits are encrypted and kept in private storage, never in a public folder. Each opens only through a link that lasts five minutes and is issued to one person: the business's owner or a member of TablaOne's team allowed to review them. Other staff of the business cannot open them, every time TablaOne's team opens one is recorded, and these files and ID numbers are kept out of our logs.
Guests
- The name and phone number the guest gives at checkout. The name is how staff find the order and hand it over; staff can see the phone number to reach a guest about their order. Guests do not need an account or an email address to order. A guest who signs in or asks for a receipt by email gives us that email address, and it receives the order confirmation or the receipt.
- An anonymous session cookie, t1_guest, that lasts 30 days. It does not contain a name or a phone number.
- What was ordered, the note to the kitchen, any allergies the guest wrote, whether it is Dine in or Takeaway and the table chosen, and for a guest on the way the time they said they would arrive and what they told the restaurant on the way (for example that they are running late).
- Who handed the order over and when.
- A photo of a payment receipt, if the guest attaches one to their order. Its location and camera details are removed and it is stored privately. Only the guest, that branch's staff and TablaOne's support team can open it, each through a short-lived link, and every opening by staff or TablaOne is recorded. It is kept with the order and deleted when the guest's data is deleted.
- At a hotel: the room number or table the guest orders to, and the orders on that room's or table's bill.
- A rating only if the guest leaves one.
- Card details never reach TablaOne. They go to Paystack or vyyBe Bank, whichever takes the payment. For vyyBe wallet payments, vyyBe Bank gives TablaOne a payer id, which is used only to award Ascend points.
Operational records
- An audit log of staff actions: who confirmed a payment, prepared, handed over, cancelled or refunded an order, paused orders, or changed the menu, and when.
- A delivery log of the emails we send: to whom, when, and whether they arrived.
- Payment messages from Paystack and vyyBe Bank about payments, settlements, refunds and disputes.
4Who else processes it
- Paystack processes every payment made through it (card, bank transfer and USSD), and its refunds and disputes. It receives the amount, the order's reference, the guest's email address when TablaOne has one, and the card details or bank details the guest enters on Paystack's own page, and tells TablaOne whether the payment went through. TablaOne pays restaurants out of its Paystack account from its own bank.
- vyyBe Bank processes payments, settlements and refunds, and confirms that a restaurant owns the vyyBe Business account it links. It receives the order amount, the payment method and the account number given when linking. A restaurant opens its vyyBe Business account on vyyBe Bank's own website, under vyyBe Bank's terms; TablaOne does not receive what it gives vyyBe Bank there.
- A business-verification service (Dojah) receives a Nigerian business's registration number and returns what the Corporate Affairs Commission's records hold about it. It is told nothing else.
- Anthropic's Claude reads the account holder's name off a bank statement a business uploads, where this is switched on. It receives the statement and returns the name; we do not let it keep or train on the file under our agreement with it. (Draft: confirm against the signed terms.)
- An email provider delivers order confirmations, receipts, sign-in codes for restaurant staff, notifications and acknowledgements. It receives the address and the message.
- We do not sell data and do not share it with advertisers.
5How long we keep it
These periods are the current settings and are flagged for legal review.
- Guest sessions: 90 days.
- Orders and settlements: kept as financial records. After 2555 days the guest's email, phone number and note on an order are cleared.
- Registration certificates, IDs, bank statements, permits and agreement acceptances: for as long as the business has an account, and after that as long as the law requires. (Draft: the period is for legal review.)
- Email delivery logs: 90 days.
- Share and referral taps: 365 days.
- Audit log: 2555 days.
6Your rights
You can ask for a copy of the data we hold about you, or ask us to delete it. Use the form below. We reply to the email address you give. Records we must keep as financial records, such as paid orders and settlements, are kept for their retention period even after a deletion request, and we tell you which.
7Changes
We may change this policy. The date at the top says when it last changed.
8Contact
Anything else about privacy goes through the contact page.