ReserveInbox

1. There are two different deletions – please do not confuse them

The ReserveInbox – staff app knows two kinds of personal data, and they are deleted by different routes. Treating them as one thing ends in asking for something other than what you wanted to be rid of.

A – A device's access (your “account” as a member of staff)

This app has no password and no registration. A device is enrolled once with a company code, and after that the device itself is the authorisation. What exists is an access bound to a device and to a seat (“host stand”, “service”) — not to your name. Sections 2 to 5 concern that access.

B – A guest's data (a reservation)

A reservation belongs to the restaurant, not to the app and not to us. It sits on the restaurant's server. Section 6 describes how a guest has it deleted.

Deleting a device's access deletes no reservation. And deleting a reservation signs no device out. That is deliberate: they are separate operations with separate controllers.

2. Route A – in the app, effective immediately

In the app: “More” → “Sign out”.

This is not a request somebody processes, and it sends no e-mail. The operation revokes this device's access immediately on the restaurant's server and then erases everything that was held on the device. Afterwards this device can only enrol again with a new company code.

3. Route B – without the app

You do not need the app in order to demand a deletion. There are two addresses, and which one is right depends on who is the controller:

First: your restaurant

Your seat and your enrolled devices sit on your restaurant's server. It is the controller for them within the meaning of the GDPR, and it can sign out any individual device in its own device list as well as dissolve a seat entirely. Approach the management or the person named in the house as the contact for data protection.

If that gets you nowhere: write to us

Send an e-mail to info@webpro.com.tr with the subject “Account deletion – ReserveInbox”. Name the restaurant in it and the label of the device (for example “iPad host stand”). For security we check that the request is legitimate before anything is set in motion — otherwise any person at all could have a stranger's tablet signed out in the middle of service.

Because we have no access to a restaurant's server, we cannot delete anything there ourselves. We receive your request, pass it to the controller, name the responsible body to you, and stay reachable until your matter is settled.

4. What is deleted

On the device – completely and irreversibly

  • the access credentials from the operating system's key store (Keychain, respectively Keystore),
  • the encrypted cache of the floor plan – and therefore the guest names held in it,
  • the encrypted outbox with entries not yet sent,
  • the encrypted cache of the restaurant's own texts.

On the restaurant's server

  • The device's access is revoked. It stops working from its next call — not only at the end of some lifetime.
  • All associated sessions are revoked in the same operation, so there is no moment in which a signed-out device could still renew anything.

An entry still sitting unsent in the outbox is lost with the deletion. If it is still needed, send it before signing out.

5. What remains – and why

WhatHow longWhy
The device record itself, marked as revoked: label, platform, app version, the time of enrolment and of last use, the time and reason of the revocation, and an irreversible checksum of the network range of the enrolling IP addressThe restaurant decidesEvidence of which device had access and when. The software does not remove this record by itself; that decision rests with the restaurant as controller.
The seat (“host stand”, “service”) with its permission scopeThe restaurant decidesA seat is a job in the operation, not a person. It is deactivated when it is no longer needed; every device enrolled against it loses its access in the same operation.
Reservations and their history entriesDefault: 365 days open, 3650 days completed – adjustable by the restaurantThey belong to the restaurant and not to the device access. A signed-out tablet changes nothing about them. More in section 6.
The restaurant's server log files and backup copiesThe restaurant, respectively its hosting provider, decidesTechnical operation and recoverability. Those systems are not ours; we deliberately name no period for them that we do not know.

6. Guests: deletion of a reservation

If you booked as a guest at a restaurant, that restaurant is the controller for your data — not we, and not the app on the counter. Address your matter to the restaurant; its privacy policy names the address.

In case you want to know what happens there technically: the restaurant's software carries a complete access and erasure function, wired into the system's own data-protection tools. A deletion removes every detail that points to you — name, telephone number, e-mail address, free-text notes, the origin of the request, the checksum of the IP address, the stored language, every message to you not yet sent, and all the personal links, which become invalid with it. The history entry, too, loses the record of who acted.

What remains is solely the shape of the booking: date, time, service and status, without any reference to a person. That is intended: the house can still reconstruct its evening, and nobody can infer you from those lines any more.

One limitation, so that it does not pass unnoticed: matching is done through the e-mail address. Somebody who left only a telephone number cannot be found this way — such a request has to be handled by hand in the house. Say so in your request.

7. Deadlines

Signing out in the app takes effect immediately.

A request by e-mail is dealt with without undue delay, and in any case within one month of receipt, as Art. 12(3) GDPR provides. In exceptional cases that period may be extended by two further months; you are told so, with reasons, within the first month.

8. Further rights

Besides erasure you have the rights of access, rectification, restriction, data portability and objection. The details are in the privacy policy. If you disagree with how your request is handled, you may complain to a data protection supervisory authority under Art. 77 GDPR.