1. Who is responsible for the data
Sergey Kubinski, a natural person, address: 15 Natalia Street, Smolyan, Bulgaria, is the controller of the personal data processed for the management of MenuGloss, the accounts, communication and security of the service. For questions and the exercise of rights: menugloss@gmail.com.
This policy covers visitors to the site and the public menus, persons who send inquiries, and users of the administrative panel. The venue is solely responsible for the personal data it chooses to publish in its menu and for its relationships with its own guests. Where MenuGloss processes data solely on the venue's instructions, a separate data processing agreement applies.
2. What data is processed
When an inquiry is submitted, we process the name entered, the venue's name, a phone number or email, and the optional message. The data is recorded in the service's database; where notification is configured, an email is also sent to the team. The form does not sign the sender up for a newsletter. Do not include sensitive data or data about other persons that is not necessary for the inquiry.
Upon registration and use of an account, we process the name, email, a protected value of the password, the association with the venue, the role, invitations, data for email confirmation and access recovery, and records of administrative actions. Uploaded photos, menus and contact details may contain personal data if the client has included them.
The public menu automatically records QR code scans, product views and selected language, linked to the venue, the product or the QR code and the moment of the event. These statistics records do not include an IP address, an IP hash, a browser description or the referring page address. The IP address is processed separately for protection against abuse; the request-limiting tables store a cryptographic hash that changes daily. This is pseudonymisation, not a guarantee of anonymity. Infrastructure providers may separately process technical logs.
3. Purposes and legal grounds
We process data relating to inquiries and accounts in order to respond to a request, and to prepare or perform a contract with a natural person — Article 6(1)(b) GDPR. For a client's contact persons and team members, the legal basis is legitimate interest in servicing and managing the contractual relationship — point (f).
For the prevention of abuse, protection of access, diagnostics and the establishment of legal claims, legitimate interest under point (f) applies, subject to an assessment of necessity and a balancing against the rights of the individuals concerned. For mandatory accounting, tax or regulatory actions, a legal obligation under point (c) applies, when such arises.
Statistics serve to provide reports on scans, viewed products, languages and QR-code activity for the venue. The current version enables it automatically, with no consent prompt; an old browser choice no longer controls collection. This description of the technical behaviour does not, by itself, establish an exemption from the applicable consent requirements. The legal basis for this configuration and the applicability of the terminal-storage rules must be confirmed before its public release.
The mandatory fields are necessary for the respective request or account. If they are missing, we may not be able to provide the requested feature. The free-text message field is optional.
4. Recipients, AI and external links
Access is granted to authorized persons and technical providers only for the relevant task. The application integrates Cloudflare R2 for files and images, Resend for transactional emails, and OpenAI for AI import, translations and suggestions. Vercel has been chosen for hosting. The application is configured to run its server functions in Frankfurt, Germany (fra1). This does not mean that all Vercel services, technical logs and sub-processor operations are confined to that region. The database is provided by Neon (Databricks group), on the Launch plan, with AWS Frankfurt, Germany (eu-central-1) as its primary region. The restore history window and retention periods for separate backups and infrastructure logs remain subject to separate confirmation; the database location does not mean all provider operations are confined to this region. When exercising a right of access, you may request the specific recipients of your data.
When an AI feature is used, the necessary texts, images or menu document are sent to the relevant provider. There is no need to include personal data about guests or staff. Published menus and contact details are accessible on the internet; a shared QR code is not a means of restricting access.
Links to Viber, maps and social networks lead to independent external services. Their own terms and data rules apply when they are used. A message sent via Viber is not the same as an inquiry submitted through the MenuGloss form.
Data may be provided to a competent authority on a valid legal basis, or where necessary to protect rights. Where a transfer outside the EEA is necessary, an applicable mechanism under Chapter V of the GDPR must be in place, such as an adequacy decision or standard contractual clauses together with supplementary measures where needed. The specific location and safeguards depend on the active configuration and the contracts with the providers; information and a copy of the applicable safeguards may be requested at the email address given.
5. Cookies and browser storage
For administrative login, cookies of the authentication system are used, including the session and request-protection cookies. Their exact prefixes may depend on the secure connection and the environment. The menugloss_admin_language cookie remembers the selected admin panel language for up to one year.
The current version does not create cookies for a statistics/analytics choice. Existing consent evidence, if any, is retained only until its original expiry and is not used as authorisation for this configuration.
6. Retention periods and deletion
Inquiries submitted through the form are kept for up to 180 days from submission. Raw statistics events are kept for up to 90 days, and audit records of administrative actions for up to 365 days. A daily job is scheduled to remove records whose retention period has expired; before it runs there may be a technical gap of up to the next successful daily run; if a run is missed, it is re-executed once the issue is resolved.
Evidence of consent is kept for up to 180 days from the time consent was given, including the record of any withdrawal. Unconfirmed registrations are deleted 7 days after the code expires. Unused team invitations are deleted 30 days after they expire. Expired password-reset tokens are removed during the daily cleanup. Inactive rate-limiting records are cleared after 1 day; an active block is not removed before it expires.
Data for an active account, menu and the accepted terms are kept for the duration of the service. Following a termination request, the provider clarifies the necessary export and processes the deletion within 30 days, except for specific data whose retention is mandatory by law or necessary for an established legal claim. For such an exception, the grounds, scope and duration are determined and access is restricted. We do not automatically delete an active venue or the data of other team members upon the request of a single individual.
Products and categories in the trash are removed after 30 days, including associated files, in accordance with the rules for shared images. Daily cleanup is configured through Vercel Cron in production. The database is hosted by Neon. Restore history, separate backups and infrastructure logs have their own retention periods, which remain subject to separate confirmation; deletion from the live database does not mean immediate erasure from those copies. Copies of correspondence in external mailboxes are managed separately from the application's database.
7. Security
The application uses role management, checks that data belongs to the correct venue, secure password storage, request rate-limiting, and checks on uploaded files. Access to internal data should be restricted according to need. No internet service can guarantee absolute security.
In the event of a security breach, the risk and the applicable obligations to notify the supervisory authority and affected individuals are assessed. If you suspect a compromised account or unauthorized access, write to menugloss@gmail.com without sending your password.
8. Your rights and how to exercise them
Where the applicable legal preconditions are met, you have the right to access, rectification, erasure, restriction of processing, and data portability. You may object to processing based on legitimate interest, for reasons relating to your particular situation. Where processing is based on consent, you may withdraw it without affecting the lawfulness of processing carried out before the withdrawal.
Send a request to menugloss@gmail.com with sufficient information for us to identify the data and the action requested. Where there is reasonable doubt as to identity, we may request proportionate additional verification; do not send a copy of an identity document by default. The response is generally provided within one month. Where a permissible extension applies, we will inform you of the reasons within the initial period. Exercising your rights is free of charge, except in the cases expressly permitted by the GDPR.
You may file a complaint with the Commission for Personal Data Protection: 1592 Sofia, 2 Prof. Tsvetan Lazarov Blvd., website cpdp.bg, or with another competent supervisory authority. The currently available ways of filing are listed on the CPDP's website. Prior contact with MenuGloss is not a precondition for filing a complaint or seeking judicial protection.
9. Updates and contact
When the purposes, categories of data or recipients change, this policy is updated. For material changes we provide appropriate notice; new consent is requested where the law requires it. The edition date allows you to identify which version you are reviewing.
For questions about this text, your data, or the external processors, use menugloss@gmail.com or the controller's postal address given in Section 1.
Contact
Sergey Kubinski · 15 Natalia Street, Smolyan, Bulgaria
menugloss@gmail.com