Skip to content

App privacy

This page covers the four Nexur applications: Nexur Sell (the point of sale), Nexur Make (the production lab), Nexur Team (the staff app) and Nexur Hub (the management console). The website has a separate privacy notice, and cookies are covered by the cookie policy.

Version 4, updated on 17 October 2026.

The reference version of this notice is the Italian one; this is a courtesy translation, and if the two ever differ the Italian text applies.

In short

Who decides what happens to the data

A gelato shop uses the apps to run its business, and two kinds of data pass through them, with different owners.

If you work for or buy from a gelato shop, the one to ask about your data is the gelato shop: it decides why it collects the data and how long it keeps it, and it owes you its own privacy notice. If you write to us, we pass the request on to the shop and help it answer you.

Who we are

Nexur Group S.r.l., Via Piave 18, 20039 Canegrate (MI). VAT no. 14821860963. You can reach us at support@nexurgroup.com, and, if you have a certified email address (PEC), also at nexurgroup@pec.nexurgroup.com.

Data we are the controller of

Data we process on behalf of the gelato shop

Below, app by app. The legal basis for this processing is chosen by the gelato shop, as controller: we give the usual one, but the shop’s own notice is the one that applies.

Nexur Sell — the point of sale

The gelato shop's till. It handles the details of customers who ask for an invoice, payment data, staff shifts and the names of whoever signs off hygiene checks.

  • Details of a customer who asks for an invoice

    Business name, VAT number, tax code, address, e-invoicing recipient code and certified email (PEC). They are saved in the gelato shop's customer address book on our servers, so they can be found next time, and they also leave inside documents: the sales journal and the electronic invoice, which goes to the Italian Revenue Agency's exchange system (Sistema di Interscambio). When you type a VAT number, the till looks up the company's details in public registers through Openapi, and the result stays with us for 30 days (7 if the company is not found).

    Why: To issue the invoice, which is a legal obligation (Article 6(1)(c)).

    How long: The address book: for the whole length of the contract, and today the till has no command to remove a customer: to do it, write to us. The documents: for the whole length of the contract and then ten years from the last entry (Article 2220 of the Italian Civil Code). An invoice that has been sent and archived cannot be deleted.

  • Purchases

    The receipt lines (products, quantities, discounts, VAT rates), the payment method, the delivery platform if the order comes from one and, if the customer asks, their tax code or their receipt lottery code (Lotteria degli scontrini). The journal reaches our servers only when the till works with the real fiscal recorder.

    Why: To record sales, which is a legal obligation, and to enter the customer in the receipt lottery if they ask.

    How long: Ten years from the last entry. A local copy of the journal also stays on the tablet, and today it is never deleted, not even after our servers have confirmed it.

  • Card payments

    The authorisation code, the transaction number and the terminal that carried it out. The card scheme and the last four digits appear on the screen and on the terminal's receipt, but the till does not store them. The card number is never stored: the payment is carried out by the POS terminal, and the card data is handled by its provider.

    Why: To reconcile takings and print the receipt.

    How long: They follow the sales journal: ten years.

  • Shifts and attendance

    The till shows staff shifts and today's clock-ins and clock-outs, which staff record with Nexur Team. It only reads them from our servers: it does not change them or keep a copy.

    Why: To know who is on duty (Article 6(1)(b), for the employment contract).

    How long: See Nexur Team.

  • Who signs off hygiene checks (HACCP)

    The name of whoever carried out a cleaning task, typed in by hand, with date, product and an optional note, in the HACCP log on our servers.

    Why: To keep the log required by food hygiene rules (Regulation (EC) 852/2004; Article 6(1)(c)).

    How long: On our servers until someone undoes the entry. We have not set a retention period yet: the gelato shop decides it, as the controller of the log.

Device permissions: local network (to talk to the fiscal printer, the printer and the POS terminal), camera (QR codes, delivery notes, product photos) and notifications, for hygiene-check reminders. Photos already on the device are picked without giving access to the library. The till does not ask for location.

Nexur Make — the production lab

The production lab's app. Working data — production, recipes, stock, hygiene checks, settings — is kept on our servers, like the till's.

  • Who signs off cleaning tasks

    The name of whoever carried out a cleaning task, typed in by hand, with date, product used and an optional note; for a temperature out of range, the note on the corrective action. They go into the HACCP log on our servers.

    Why: To keep the hygiene log required by the rules (Regulation (EC) 852/2004; Article 6(1)(c)).

    How long: On our servers until someone undoes the entry. We have not set a retention period yet: the gelato shop decides it, as the controller of the log, and a hygiene log deleted too early removes the evidence an inspection asks for.

  • Who is on duty and who produces

    The app shows staff shifts and attendance, which come from Nexur Team, and only reads them. When a production batch is recorded, whoever made it is chosen from the staff present, and their name stays linked to the batch, with an optional note.

    Why: To know who is on duty and keep production traceable (Regulation (EC) 178/2002; Article 6(1)(b) and (c)).

    How long: Shifts and attendance: see Nexur Team. Production batches stay on our servers: we have not set a retention period yet.

  • Suppliers' delivery notes

    The photo or PDF of a delivery note, looked at while the booking lines are typed in by hand. If the supplier is a sole trader, it may contain data about a person. Only the booking data goes to our servers: supplier, document number and date, items, quantities, lots and expiry dates.

    Why: To record incoming goods (Article 6(1)(b) and (c)).

    How long: The photo or PDF only while the document is open on screen: they are not saved or sent. The booking follows the stock documents.

Device permissions: camera, to photograph delivery notes (on Android the phone's camera app is used), and notifications, for hygiene-check reminders. Photos already on the device are picked without giving access to the library.

Nexur Team — the staff app

The app staff use to clock in and out, see their shifts, swap them with colleagues and ask for holidays and leave; those given the task also use it to book in goods and make deliveries. The controller of this data is the gelato shop, that is, the employer.

  • Who you are

    Name, role, staff number and location. You sign in with an account handled by Amazon Cognito; an access token stays on the phone, in the device's protected storage.

    Why: To manage the employment relationship (Article 6(1)(b)).

    How long: The access token is valid for up to ten years, until you sign out of the app or the gelato shop deactivates you. When your employment ends, the gelato shop deactivates you from the Nexur Hub console, and deactivation is permanent: from then on you can no longer sign in to Nexur Team, your Amazon Cognito account is suspended and signed out on every device, the link to your phone is removed and the push notification codes are deleted. Your pending requests are closed and your future shifts are removed, except those that are part of a swap with a colleague, which the shop reassigns. If you go back to work there, a new account is created for you. Your profile (name and email) stays on our servers: the planned period is five years after deactivation, after which the name becomes «Former employee», the email is deleted and so is the Amazon Cognito account. This automatic deletion is ready but not switched on yet: until it is, the profile stays on afterwards too.

  • Your location when you clock in

    When you clock in or out, the app reads the phone's location and sends it to our servers with the clock-in, even when you are outside the area. The server uses it only to work out how far you are from the shop and whether you are inside the area, and stores the distance and the result: the coordinates are not stored, neither in the database nor in the technical logs. The coordinates of clock-ins made before 16 October 2026, when they were still stored, have been deleted from the database. It does not read your location at any other time: not during your shift, not during deliveries and not in the background.

    Why: To check that clocking in happens at the shop. In Italy, using the location of people at work requires the employer to comply with Article 4 of the Workers' Statute (Law 300/1970) — a union agreement or an authorisation from the Labour Inspectorate, before starting. This is the gelato shop's obligation, and its privacy notice must tell you the legal basis.

    How long: The coordinates are not kept: the server discards them as soon as it has worked out the distance. The distance and the result follow the clock-in (see below).

  • Clock-ins, shifts and hours

    Clock-ins and clock-outs, planned shifts, shift swaps with colleagues and the resulting hours.

    Why: To manage the employment relationship (Article 6(1)(b)) and the employer's attendance obligations (Article 6(1)(c)).

    How long: On the phone only while the app is open. On our servers for the whole employment; then the planned period is five years after deactivation, which is how long the law requires attendance records to be kept (the employment register) and how long employment claims can be made. Shifts swapped with a colleague remain afterwards, because they are part of the colleague's shifts, but without your name. The automatic deletion is ready but not switched on yet: until it is, they stay beyond the five years too.

  • The phone's code

    A code the app creates once on the phone, to tie your account to a single device. A copy is also kept on your account at Amazon Cognito.

    Why: To stop someone clocking in for you from another phone: a legitimate interest of the employer (Article 6(1)(f)).

    How long: It stays on the phone even when you sign out — on purpose, otherwise the link would be worthless — and goes away when you uninstall the app.

  • Notifications

    The notices that concern you (shifts, swaps, leave, announcements) and whether you have read them. The app downloads them from our servers and, if you allow it in your phone's settings, also sends them to you as push notifications: for this the phone gives us a notification code, and the title and text of the notice go through Google's Firebase Cloud Messaging, which on iPhones delivers them through Apple's notification service.

    Why: To keep you informed about your work (Article 6(1)(b)).

    How long: On the phone only while the app is open. On our servers they stay: «read» does not mean deleted. The planned period is 90 days after deactivation, but the automatic deletion is not switched on yet. The phone's notification code is deleted when the gelato shop deactivates you.

  • Holidays and leave

    The type of request, the dates and a note you write yourself. Do not write anything about your health in the note: the app is not built to hold it, and for a medical appointment it is enough to ask for leave.

    Why: To manage absences (Article 6(1)(b)).

    How long: On our servers like clock-ins: for the whole employment, then the planned period is five years after deactivation, with the automatic deletion ready but not switched on yet.

  • Goods and deliveries

    If the gelato shop gives you these tasks: goods booked into stock and, if you make deliveries, the rounds, the tubs and materials loaded and those delivered, with your name. Round operations stay on the phone until there is a connection to send them. Deliveries do not read your location.

    Why: To record goods coming in and going out, as food traceability (Regulation EC 178/2002) and business records require (Article 6(1)(b) and (c)).

    How long: On the phone only until they have been sent. On our servers they follow the stock and delivery documents they belong to; after deactivation they still carry your name, and the planned period before it is replaced with «Former employee» is five years, with the automatic deletion ready but not switched on yet.

  • Suppliers' delivery notes

    If the gelato shop has the DDT Module, «Read delivery note» lets you photograph the delivery note of incoming goods. The photos go to our servers and are read by Mistral AI, which extracts the supplier, items and quantities; after you check them, the goods are booked in under your name. If the supplier is a sole trader, the document may contain a person's details.

    Why: To record incoming goods (Article 6(1)(b) and (c)).

    How long: The photos are deleted automatically after 30 days. The extracted data needed for the booking remain, and follow the stock documents.

  • Which privacy notice you have seen

    When this page changes in substance, the app will show you at launch and let you carry on. Recording which version was shown, to whom and when, does not happen yet: when it does, it will be written here.

    Why: To be able to show what was communicated (Article 5(2) GDPR).

    How long: Not applicable yet.

Device permissions: location (only when clocking in or out), camera (to read the barcodes on goods, which are not saved, and to photograph delivery notes) and notifications.

Nexur Hub — the management console

The web console the shop manager uses to organise the work. On top of the sign-in and contract data described above, it handles staff shifts on behalf of the gelato shop and, if the shop allows it, what the lab that supplies it can see.

  • Staff shifts and requests

    The list of staff at each location (name, email, staff number, role, whether their phone is linked and whether they are active), their shifts — which can be created, moved and deleted from the console —, clock-ins with the «inside or outside the area» result (not the distance and not the coordinates), holiday and leave requests, which can be approved or refused, and who made a delivery and when. Shift swaps are decided between staff in Nexur Team; the shop still handles covering a shift when no colleague is named. From the console the shop creates staff accounts and deactivates those who stop working: what happens then is explained under Nexur Team, «Who you are». It is the same data staff see in Nexur Team. For support, Nexur staff also see the name, staff number and role of each client's active staff.

    Why: To organise the work (Article 6(1)(b), for the employment contract).

    How long: See Nexur Team.

  • The link with the lab

    If the gelato shop agrees to link up with the lab that supplies it, the lab sees in the console the consumption from the evening closings, the tubs put to temper and the ones left in the display case — only for the flavours that lab has delivered to the shop in the last 90 days. Never sales, receipts, prices, customers or staff. When the lab asks to link up, the shop's owner receives an email.

    Why: To plan the lab's production. The gelato shop decides, as the controller of this data: without its yes the lab sees nothing.

    How long: The lab keeps no copy: it reads the data live for as long as the link is active. The shop or the lab can revoke it, and from that moment reading stops. A record of the link remains: who asked for it and who accepted it, when, and any revocation.

Device permissions: none: it is a web page.

Where the data is kept, and who else sees it

What the apps do not do

Deleting data

We create the gelato shop and console accounts together with the shop, and close them when the shop or you ask: write to support@nexurgroup.com. Closing an account does not delete the documents the law requires us to keep.

If you work at a gelato shop, your Nexur Team account is created and closed by the shop from its console: when you stop working there it deactivates you, and access ends immediately and for good. What remains and for how long is explained under Nexur Team.

What cannot be deleted. Invoices and sales records: the law requires them to be kept for ten years, and an invoice already sent to the exchange system cannot be withdrawn.

The Nexur Sell customer address book has no command to remove a customer today: write to us and we will remove them. Removing a customer from the address book does not touch documents already issued with their details.

Clock-ins, shifts, holidays and notifications have no delete command in the apps: the request goes through the gelato shop, which is the controller, and then to us. Clock-in coordinates are not kept, so there is nothing to delete.

After a deletion, the data stays in the backups for up to about 7 days, then it disappears from there too.

Your rights

You can ask to see your data, correct it, delete it, restrict its use, receive it in a machine-readable format, and object to the processing. For data we are the controller of we answer ourselves, within one month: write to support@nexurgroup.com. For data we process on behalf of a gelato shop the request goes to the shop; if it reaches us, we pass it on.

If you think your data is being handled wrongly you can complain to the Italian data protection authority, the Garante per la protezione dei dati personali.

When this page changes

The page carries a version number and a date. When something changes in substance — new data, a new provider, a different retention period — the number goes up, and the date says when.