Product: TablePing
(Android package com.techmind.tableping)
Company: TechMind together with LetMeDoit
Effective date: 16 September 2026
TablePing is a restaurant host-stand app for waitlists, table seating, reservations, and floor status. It is provided by TechMind together with LetMeDoit (“we”, “us”, “our”). By using TablePing you agree to this policy, together with our Terms and Conditions and Content Policy.
1. Who this applies to
TablePing is for restaurant staff (admins, supervisors, and hosts), not for diners as end users of the app store listing. Guest names and phone numbers entered by staff belong to the restaurant. The restaurant is the controller of that guest information and is responsible for telling its guests how it is used, where the law requires that.
2. Information we collect
Restaurant and staff
- Restaurant name, address, email, and contact number given at registration
- Staff username (login ID) and PIN/password (stored as a hash, not in plain text)
- Staff role and which dining area a supervisor is assigned to
Guest records entered by the restaurant
- Name, optional mobile number, party size, notes, tags
- Waitlist status, quoted wait, called/seated time, and assigned tables
- Reservation details entered by staff for the restaurant’s own venue
Device and service
- A random device ID created on the device, plus device model, OS, and app version, used to activate a licence and keep devices in sync
- Floor plans, table layout, dining-time settings, and service session times
- Technical logs needed to run and secure the service (for example connection errors)
Data is stored on the device (local cache) and on our hosted servers used by TablePing (currently the TablePing API at app.tableping.pro).
We do not collect precise location, contacts, photos, microphone audio, payment card numbers, or government ID numbers.
3. App store data safety summary
This summary is for Google Play and similar app store forms. It describes data the TablePing app handles.
| Category | Examples | Purpose |
|---|---|---|
| Personal info | Restaurant and staff name, email, phone; guest name and optional phone entered by staff | App functionality (accounts, waitlist, seating) |
| App activity | Waitlist, table status, reservations, service history | App functionality |
| Device or other IDs | Random device ID, model, OS, app version | Licence activation, multi-device sync, security |
- Data is not sold and is not used for advertising.
- Data is encrypted in transit (HTTPS).
- Staff on the same restaurant account can see the same waitlist and floor data.
- Hosting providers process data only to run TablePing.
4. How we use information
- To operate waitlist, seating, reservations, call display, and multi-device sync
- To create and manage the restaurant account, licence, and staff logins
- To provide support when staff call the support number shown in the app
- To keep the service secure and fix faults
We do not use this information for advertising, and we do not sell it.
5. Permissions
The Android app requests Internet access to talk to TablePing servers. If staff tap Support, the device dialer may open so they can call our support number. No other sensitive Android permissions are required for core seating features.
6. Sharing
- Staff on the same restaurant account see the same waitlist and floor data.
- Hosting and infrastructure providers process data only to run TablePing.
- We may disclose information if required by law.
Optional Google services: the app may load fonts from Google Fonts. Google Sign-In libraries may be present for older cloud-connect features that are not shown in the current product. We do not use third-party ad or analytics SDKs in TablePing.
7. Retention and deletion
Staff and restaurant account data is kept while the restaurant is active. Guest waitlist and seating records are kept until the restaurant clears them (for example by starting a new service) or the account is closed. Device cache can be removed by uninstalling the app or signing out, subject to what remains on the server for that restaurant.
Restaurant admins can edit or remove staff users and guest records in the app. To request access, correction, or deletion of account data, or to close a restaurant account, contact us using the details below. We may need to verify that the request comes from the restaurant that owns the account.
8. Security
Access uses staff login and licence activation. PINs/passwords are hashed. Transmission to the API uses HTTPS. No method of storage or transfer is completely secure, and restaurants should restrict who has staff logins.
9. Children
TablePing is a business tool for restaurants. It is not directed at children under 13, and we do not knowingly collect personal information from children.
10. Changes
We may update this policy when the product or the law changes. The effective date at the top will be revised. Continued use after an update means you accept the revised policy.
11. Contact
TechMind
Website: https://techmindsoftware.com/
LetMeDoit
Website: https://www.letmedoit.in/
You can also use Support in the TablePing app Account screen when a support number is configured.
Related: Terms and Conditions · Content Policy