Privacy policy

Last updated: 28 September 2026

BillPlz is operated by Carlo Martin, an independent developer in South Africa. For privacy questions or requests, email info@autorxgen.co.za.

What the service does

BillPlz lets customers ask their restaurant for the bill and lets staff respond. BillPlz does not process payments or collect card details.

Information we use

• Restaurant owners: email address, login credentials handled by our authentication provider, name, restaurant details, table labels and team setup.
• Waiters: the name supplied by their manager, an account identifier, restaurant membership, duty status, and actions on bill requests. Waiters joining with a code do not need an email address.
• Notifications: an app installation identifier and an encrypted Apple push token associated with a staff account and restaurant.
• Customers: a temporary browser session, restaurant and table identifiers, bill requests, reminders and their times. A customer account is not required.
• Operation and security: connection information such as IP addresses and technical request logs used by our hosting providers and to protect the service.

Why and with whom

We use this information to authenticate staff, keep restaurants separate, deliver bill requests and notifications, provide support and prevent misuse. Your restaurant's authorised staff can see its queue and relevant staff names. Owners manage their restaurant's staff and tables. We do not sell personal information, use advertising trackers, or track activity across other apps or websites.

We use Supabase for authentication and database hosting, and Apple for push notifications. Our Supabase project is hosted in London; service providers may process information outside South Africa. Hosting providers process the connections needed to run the website and API. We may disclose information when legally required.

Cookies and device storage

Essential browser cookies maintain customer sessions and owner login. Customer sessions expire after two hours. Staff login credentials are stored in the iPhone Keychain; a local installation identifier supports notifications. We do not use analytics or advertising cookies.

Retention and deletion

Restaurant records and bill activity are retained while the restaurant account is active. In the iPhone app, open My duty → Delete my account to start deletion without emailing us. If joining did not finish, the deletion option is also available on the sign-in screen for that saved account.

Waiter deletion removes their name, login identity from restaurant records, device tokens, duty record and accepted join codes. Bill history retains an anonymous “Deleted staff” attribution. Owner deletion also deletes their restaurant, tables, join codes and request history, and removes that restaurant's staff access. It does not delete other staff members' separate login accounts.

Application data removal happens when the deletion request is accepted. Login account removal is processed automatically, normally within a minute; provider outages can delay it. Contact us if it has not completed within seven days. A one-way security fingerprint is kept for 24 hours after login deletion to block old access tokens, then removed. Provider backups and technical logs expire according to their own retention schedules and are not used to restore a deleted account to normal operation.

Your choices

You can disable notifications in iPhone Settings and end duty in the app. You may contact us to request access, correction or deletion of your personal information, or to raise a privacy concern. To protect your account, we may need to verify a request. You may also complain to South Africa's Information Regulator.