JUN FOOD SRLS · RISTOEASY
Privacy and cookies
Ultimo aggiornamento: 21 ottobre 2026
Dati di account e licenza per accedere. Contenuti e registri tecnici per le funzioni e la sicurezza. Permessi facoltativi, senza tracciamento pubblicitario. Nell’ambiente condiviso usa dati fittizi.
Controller and scope
JUN FOOD SRLS, Viale Genova 6, Lodi, Italy, VAT 12642140961, controls the central RistoEasy service, website and support enquiries. Privacy contacts: lansujunsrls@gmail.com and certified email junfoodsrls@pec.it. This notice is provided under Articles 13 and 14 of the GDPR (EU 2016/679).
Central account and licensing data are separate from operational data on the server configured by the restaurant. The restaurant determines the purposes and retention of that data and provides its own notice; any role of JUN FOOD SRLS is defined for the particular service. The workspace linked to the review account is hosted by RistoEasy and shared: use fictitious data only, without customers’ personal information.
Accounts, licenses and content
We store email, names and account/restaurant identifiers, passwords only as hashes, roles, license status and products, expiry dates and limits, random device and session identifiers, platform, access/verification dates and counters. We do not collect a hardware fingerprint. Restaurant registration on the website creates an account awaiting approval, not an automatically active license.
Management functions can store entered names, orders, carts, notes and messages. In the review account workspace this content is genuinely saved and persists after closing the app; other users of the same workspace may see it. No charges or fiscal receipts are issued without connected devices. Do not enter card details, health information or identity documents.
Purposes and legal bases
We use data for authentication, restaurant/device recognition, permissions, requested features and support: contract or requested pre-contractual steps, GDPR Article 6(1)(b). Professional communications, security, abuse prevention and diagnostics rely on legitimate interests, Article 6(1)(f); legal duties on Article 6(1)(c). Where optional processing requires consent, Article 6(1)(a), it can be withdrawn.
Sign-in data are necessary to use restricted services. We do not sell data, use behavioural advertising or advertising tracking, or make solely automated decisions with legal or similarly significant effects.
Security, cookies and retention
Essential cookies manage sign-in, security, language and table configuration. Without “Stay signed in”, an access session lasts at most 12 hours; with it, the license determines the duration, up to 90 days, subject to earlier expiry or revocation. Random device identifiers and language preferences may last one year and renew during use. Ordering sessions and local data have their own durations; client_name, when set, lasts one day. Clearing local data does not delete content already stored on the server.
Access/security events may be linked to accounts and devices; IPs in application events are pseudonymised. Anti-abuse counters use 15-minute windows. Login events older than 180 days are cleaned at the next login; administrative audits may be retained for security and legal claims. Technical logs may include IPs, requests, timing and errors, rotating by period or size. Accounts/content remain for the service and subsequent legal or documented needs; shared review content remains until deletion or reset. Backups follow their replacement cycle.
Optional permissions and on-device data
Camera/photos support scanning and capture chosen by you; the microphone supports requested recordings; location is used only while using location features. Local networking reaches the restaurant system. NFC returns tag content to the requesting feature. Granting a permission alone does not automatically upload photos, audio or location to our servers. You may deny/revoke permissions in device settings; dependent features may be unavailable.
Face ID/Touch ID are managed by the operating system: we receive the result, not biometric templates. Continuous GPS, VoIP calls and background audio are disabled. Server-side RistoEasy push registration and delivery are not currently active; a system token may remain on the device or in a technical cookie. Supported Apple translation/features run when requested; no external AI service is configured.
Android version
The Android version uses Google ML Kit for on-device barcode scanning and translation. Analysed images and text to translate are processed locally. Google components may transmit random installation identifiers, device, operating system and app version information, configured languages, component usage events, timings and errors for diagnostics and operational analytics. We do not use the advertising ID. Firebase push configuration is not active in Android version 1.0.
The central RistoEasy service uses HTTPS. Restaurant-local servers may use HTTP on the restaurant network; protection of that connection depends on the installation configuration. The Android version does not use the microphone, continuous location or background location. Camera and while-in-use location are optional; biometrics remain managed by the operating system.
Recipients and transfers
Authorised staff and necessary technical providers access data under their respective roles and applicable agreements, as may authorities when legally required. Other users of the shared workspace can read its contents. Email, WhatsApp and Apple components, when selected, follow their own policies; support email also uses Gmail.
Some providers may process data outside the EEA. Where required by the GDPR, appropriate safeguards such as adequacy decisions or standard contractual clauses apply according to the service. You may request information about recipients and safeguards relevant to your data.
Rights and deletion
Where applicable you may request access, correction, account/data deletion, restriction, portability, objection and withdrawal of consent by emailing lansujunsrls@gmail.com or junfoodsrls@pec.it. We verify only the information necessary to identify the request. Legal duties or legal claims may limit deletion; we will explain the applicable reasons.
You may complain to the Italian Garante or your competent supervisory authority. For data in a restaurant’s own operational installation, contact that restaurant. Updated: 22 October 2026. New features or processing require this notice to be updated.