1. Who is responsible for what
We make this app, but we do not operate it. That is not a turn of phrase but the way the product is built, and it decides whom you approach with a concern.
The restaurant is responsible for operation
Every restaurant runs ReserveInbox on its own server. The app connects exclusively to the address that was entered when the device was enrolled. Reservations, guest data, seats and enrolled devices sit there and only there.
The controller within the meaning of the General Data Protection Regulation (GDPR) for all of this data is therefore the restaurant concerned. Its own privacy policy applies, and you address requests for access, rectification and erasure to it.
We are responsible for the pages of reserveinbox.com and for our correspondence
We process personal data only where you actually deal with us: when you visit the pages of reserveinbox.com and when you write to us. A WEPRO server through which a restaurant's reservations would pass does not exist.
- Provider
- WEPRO YAZILIM VE DANIŞMANLIK LTD. ŞTİ.
- Address
- Şekerhane Mah. Çaybaşı Sk. 24/3, 07400 Alanya, Antalya, Türkiye
- info@webpro.com.tr
- Phone
- +90 507 947 3333
No data protection officer has been appointed; there is no statutory requirement to do so.
2. Controller under Turkish data protection law (KVKK)
Under Turkish Law No. 6698 on the Protection of Personal Data (KVKK), the controller (“veri sorumlusu”) for the processing described above is:
- Provider
- WEPRO YAZILIM VE DANIŞMANLIK LTD. ŞTİ.
- Address
- Şekerhane Mah. Çaybaşı Sk. 24/3, 07400 Alanya, Antalya, Türkiye
- info@webpro.com.tr
- Phone
- +90 507 947 3333
- Tax number
- 8100751785
- Tax office
- Alanya Vergi Dairesi
Under Art. 11 KVKK you have the following rights against the controller: access, rectification, erasure or destruction, information about domestic and foreign recipients, objection to individual decisions based solely on automated processing, and compensation for damage caused by unlawful processing. These rights exist alongside your rights under the GDPR and leave them unaffected.
3. What the app stores on the device
Four things are held on the tablet or phone, and all four belong to the device, not to us:
- The device's access credentials – exclusively in the operating system's key store (Keychain on iOS, Keystore on Android). There is no password and no user name; the enrolled device itself is the authorisation.
- An encrypted cache of the floor plan, so that the plan stays readable when the Wi-Fi drops. It contains the day's reservations, and therefore guest names too.
- An encrypted outbox for entries that could not yet be sent.
- An encrypted cache of the texts of the restaurant concerned (labels, notes).
Signing out removes all four – see Delete your account and data.
4. What is transmitted to the restaurant's server at enrolment
When a device is enrolled with a company code, a device entry is created on the restaurant's server. It contains:
- the label entered at enrolment (for example “iPad host stand”),
- the platform and the version of the app,
- the time of enrolment and the time of last use,
- a salted, non-reversible checksum of the network range of the IP address the enrolment came from. The IP address itself is not stored.
The entry names a device and a seat (“host stand”, “service”), not a person. Which person works at a seat is decided by the restaurant, and the app does not know it.
5. App permissions
Camera
The app requests access to the camera in order to read a guest's arrival QR code. There is no other purpose: no images are stored, no recordings are transmitted and no faces are recognised. In the demo the camera is deliberately not started at all.
Photos and notifications
When you attach a screenshot to feedback for the restaurant, the app opens your device’s image picker at your request; only the picture you choose is sent. On Android the app also asks for permission to show notifications. The app does not request location, contacts or the microphone.
6. No tracking, no advertising – and what leaves the restaurant
The app contains no advertising SDKs, no analytics tools and no crash reporting to third parties. Usage data is not sold. Two paths lead beyond the restaurant: push notifications to staff are delivered by the restaurant’s server through the services of Apple (Apple Push Notification service) and Google (Firebase Cloud Messaging), and feedback from the app – with a screenshot if attached – goes to the restaurant’s inbox and can be forwarded from there to us as the maker.
The pages of reserveinbox.com set no cookies and embed no fonts, maps, videos or scripts from other servers. They remember only one setting you choose yourself – light or dark display – in your browser’s local storage. It is not sent to us or to anyone else; you remove it by deleting the site data of reserveinbox.com in your browser.
7. Visiting the pages of reserveinbox.com (server log files)
When you visit these pages, our hosting provider automatically processes the information your browser transmits: IP address, date and time, the address requested and the HTTP status code, the amount of data transferred, where applicable the previously visited page, and browser type and operating system.
- Purpose: delivering the pages, technical operation, and detecting and defending against attacks.
- Legal basis: Art. 6(1)(f) GDPR; our legitimate interest lies in secure and stable operation.
- Retention period: 52 days. After that the log files are deleted or truncated.
This data is not combined with other data sources and is not used to create usage profiles. The pages are delivered exclusively over an encrypted HTTPS connection.
8. Contacting us by e-mail
If you write to us, we process your address and the content of your message in order to handle your enquiry.
- Legal basis: Art. 6(1)(f) GDPR; for enquiries in the context of a contract or its initiation, Art. 6(1)(b) GDPR.
- Retention period: we delete the correspondence as soon as it is no longer needed and no statutory retention obligations stand in the way.
The demo form on this website sends nothing by itself: it opens your e-mail program with a prepared message to info@webpro.com.tr. We receive it as an e-mail only when you send that message.
9. Retention in a restaurant's operation
How long a restaurant keeps its reservations is decided by the restaurant – it is the controller and it knows its own retention obligations. The software ships with defaults for this, which are a starting point and not a legal statement:
Software defaults
| Type of entry | Default | Meaning |
|---|---|---|
| Open request (requested or confirmed, never completed) | 365 days | A request that never turned into a visit. |
| Completed entry (attended or cancelled) | 3650 days (10 years) | A completed transaction for which a business may have a commercial reason to keep it longer. |
| Clean-up operating mode | report only | As delivered, nothing is deleted automatically: the software only counts what would be due. Only when the restaurant switches to “enforce” is anything actually deleted. |
These defaults can be read in the program code and are not estimates. Each restaurant enters the figure that its own published policy states.
10. Recipients and third countries
Beyond the hosting provider named above, we do not disclose personal data to third parties unless we are legally obliged to do so.
The controller for these pages is established in Türkiye. Personal data processed in operating these pages and in our correspondence is therefore accessible to us from Türkiye. There is no adequacy decision of the European Commission for Türkiye. Access takes place on the basis of appropriate safeguards under Art. 46 GDPR (the specific safeguard will be named here once the ongoing legal review is complete).
This does not apply to the data that arises in a restaurant's operation: it sits on the restaurant's server, and where the restaurant transfers it is stated in the restaurant's own privacy policy.
11. Your rights
With regard to the personal data concerning you, you have the right to:
- access (Art. 15 GDPR)
- rectification (Art. 16 GDPR)
- erasure (Art. 17 GDPR)
- restriction of processing (Art. 18 GDPR)
- data portability (Art. 20 GDPR)
- object to processing (Art. 21 GDPR)
- withdraw consent you have given, with effect for the future (Art. 7(3) GDPR)
Whom to contact: if it concerns a reservation, a seat or an enrolled device, the restaurant is the right address – it is the controller for that. If it concerns these pages or your correspondence with us, write to info@webpro.com.tr. We answer requests without undue delay and at the latest within one month of receipt (Art. 12(3) GDPR).
12. Right to lodge a complaint with a supervisory authority
Irrespective of this, under Art. 77 GDPR you have the right to lodge a complaint with a data protection supervisory authority, in particular in the Member State of your habitual residence, your place of work or the place of the alleged infringement. As we maintain no establishment in the EU, there is no lead supervisory authority within the meaning of Art. 56 GDPR. The competent authority is therefore the supervisory authority of the German federal state in which you reside; a list of all German supervisory authorities is published by the Federal Commissioner for Data Protection and Freedom of Information.
13. No automated decision-making
No automated decision-making, including profiling, within the meaning of Art. 22 GDPR takes place.
14. Changes to this policy
We adapt this policy as soon as the functionality described changes. The date currently in force is shown at the top.