Sandtick
ItalianoPrivacy Policy
Last updated: 10 November 2026
1. Data controller
Sandtick is an online booking management service for restaurants and beach clubs, operated by 266 La Barraca SRL, registered office Lungomare delle Meduse 266, 00071 Pomezia (RM), Italy, VAT no. 16691711002, e-mail support@sandtick.com.
266 La Barraca SRL is the data controller for the data of the restaurant accounts using Sandtick (owners and staff).
The data of the restaurants' customers (bookings, names, contact details, any allergies and notes) is processed on behalf of each restaurant, which is its controller. For this data Sandtick acts as data processor under Article 28 of Regulation (EU) 2016/679 (GDPR) and uses it solely to provide the service to the restaurant. The privacy notice for customers is published by each restaurant on its booking page.
2. Data processed and purposes
- Account data: name, e-mail address, role, date of last access and password, stored only in hashed form; for the owner also the phone number given at sign-up, used only to contact them if needed. Processed to give access to and provide the service (Art. 6(1)(b) GDPR).
- Billing and payment data: company name or first and last name, VAT number, tax code, address, recipient code or certified e-mail (PEC), e-mail for receipts, chosen plan and payments made. Processed to manage the subscription and issue invoices (Art. 6(1)(b) and (c) GDPR). Card details are collected and stored by Stripe and never reach Sandtick, which only sees the card brand and the last four digits.
- Sign-up requests: the data entered to create the account and the IP address the request comes from (for an IPv6 address only its first half, the network part); the password is not part of the request, it is chosen afterwards, when opening the confirmation link. The IP address passes through Cloudflare for the anti-bot check (section 5); we use it only to limit repeated requests and delete it after one hour. A request not confirmed within 7 days is deleted; if Sandtick resent you the e-mail or removed the request, the e-mail address stays in the internal log of those actions for 30 days. A confirmed request is kept, without the IP address, for as long as the restaurant's data is kept (section 6).
- Staff accounts awaiting confirmation: when the owner creates an account for a member of their staff, until that person confirms the e-mail address with the link we send them we keep the name, e-mail address, role and password chosen by the owner (only in hashed form); the same, without the password, when the owner changes the e-mail address of an account. They are used to check that the address really belongs to that person (Art. 6(1)(b) and (f) GDPR). If it is not confirmed, we delete them, also from the change log, 30 days after the last link sent, or straight away if the owner deletes the account awaiting confirmation or cancels the new address.
- Login attempts: for attempts to sign in, to recover the password and to change it, the IP address they come from (for an IPv6 address only its first half, the network part), the e-mail address entered (even if it matches no account) or, for a password change, the account concerned, and the time of the attempt. They are used to block repeated attempts and are deleted after 24 hours. The legal basis is our legitimate interest in the security of the service (Art. 6(1)(f) GDPR).
- Change log: who made each change in the management area, what was changed and when, with the data before and after the change, including customers' data (for example name, phone number and allergies). It is used to reconstruct who changed what and is kept for 2 years. When a customer withdraws consent and the restaurant removes their allergies, they are also removed from the log. For account data the legal basis is our legitimate interest in the security of the service; the customers' data it contains is processed on behalf of the restaurant.
- Device data for notifications: for users of the Sandtick apps for Android, iPhone and iPad, whatever their role, the identifier assigned to the app on that device by Google's Firebase Cloud Messaging service (on Android) or by Apple's push notification service (on iPhone and iPad), the name and version of the app, the account and restaurant it is linked to, and the dates of registration and update; on iPhone also the identifier Apple assigns to the dinner panel of a service (see “Data that stays on devices”), with the service and the day. They are used only to deliver to the device the notifications the account has turned on in Account → Notifications and to update that panel: a new online booking, a cancellation or a reconfirmation made by the customer, a customer who has not yet reconfirmed three hours before the time, a guarantee card added by the customer, a booking cancelled because the card did not arrive. At first only accounts with the owner or manager role receive them, and only for new online bookings and cancellations; floor staff only if they turn them on, read-only accounts never (Art. 6(1)(b) GDPR). Each notification contains the type of notification, the customer's first and last name, the number of guests, the day, service and time of the booking, the time of the notification and an internal reference to open the booking; each panel update contains the covers of the service, the next arrival (time, first and last name, number of guests) and the line of the latest event. This is customers' data processed on behalf of the restaurant, which passes through Google or Apple only to be delivered (section 5); if the device cannot be reached, Google or Apple holds it for at most one hour. The panel identifier is deleted when the panel closes, together with what is needed to update it (a code of the figures sent and, for 5 minutes, the line of the latest event); the device identifier when the user signs out or access on that device is closed (for example by a password change), when the account or the restaurant is deleted, and when Google or Apple reports it as no longer valid, for example because the app was uninstalled. If the app is not used for 400 days, access expires: the identifier is no longer used and is deleted shortly afterwards.
- Data of the restaurants' customers: the data entered by the restaurant or by the customer when booking, processed only to manage the bookings of that restaurant. On the restaurant's behalf we also keep proof of the consents given by customers and of their withdrawal (the tick boxes of the online booking and of the guarantee card; the consent to the processing of allergies given verbally, which staff record when they write the allergies down, or sent by a program the restaurant connects to Sandtick), with the data of the booking or customer record they refer to. These records are kept beyond the 2 years of the change log, for as long as the restaurant's data is kept (section 6); those of a customer record are deleted if the restaurant deletes the record.
- Guarantee card of the restaurants' customers (cancellation policy): if the restaurant turns it on, the customer enters the card in Stripe's form, on the restaurant's own Stripe account connected to Sandtick (Stripe Connect). The card number never reaches Sandtick: on the restaurant's behalf we keep only Stripe's references, the card brand, the last four digits, the expiry date, the policy accepted by the customer and any charges and refunds, which are always decided by the restaurant. The card stays saved on Stripe until 30 days after the day of the booking, the period in which the restaurant can charge the fee; Sandtick then removes it from the restaurant's Stripe account, deletes the customer's record there too (name, e-mail and phone number) and deletes its references. Only a card that a fee was charged to is kept.
- Bug reports: text, optional photo (which may show customers' data), name of the sender, title and address of the page, type of device and browser, screen size, and the account and restaurant it comes from. They are used to fix errors in the service, on the basis of our legitimate interest in keeping it working (Art. 6(1)(f) GDPR). They also reach Sandtick by e-mail and are kept for as long as the restaurant's data is kept (section 6).
Data that stays on devices. The management area is used from the browser or from the Sandtick apps for Windows, Mac, iPhone, iPad and Android, which show it inside them. Devices are chosen and managed by the restaurant, which is responsible for protecting them (for example with a screen lock). For the service to work, the following stays on the device:
- sign-in, in a technical cookie valid for up to 400 days from the last use; a technical cookie, lasting 400 days, with a mark showing that someone has already signed in from that device with a given e-mail address (at most five; it is a signature from which the address cannot be read), used to let them in even while someone is trying many passwords; display preferences, in technical cookies lasting one year; how far the user has got in the guided tutorials;
- a copy of today's and tomorrow's bookings, with the customers' names, nicknames, phone numbers, allergies and notes, tables and requests, and the bookings and pages of the management area opened recently (up to 40 in all, for example the customer list or the change log). They are updated while there is a connection, so that they can be consulted when there is none, and stay until the user signs out;
- changes and bookings recorded while there is no connection, with the data entered, until they are sent when the connection returns or discarded by the user, even after signing out;
- in the apps, the notifications the account has turned on (for example new online bookings and cancellations), with the customer's first and last name, number of guests, day and time (for a booking added by other staff, also the name of their account), which stay in the notification centre until they are opened or removed; on the lock screen their content is shown according to the device settings;
- in the iPhone and Android apps, during service, a panel on the lock screen (on iPhone also in the Dynamic Island) with the covers and the next arrival (time, first and last name, number of guests) and, on iPhone, for a few minutes the latest event among the notifications the account has turned on (for example an online booking or a cancellation). The panel is shown even when the device hides the content of notifications. It closes when the user leaves the management area and can be swiped away. On iPhone Sandtick also updates it, with the app closed, when an event of that service arrives or its figures change (at most once a minute, and every 10 minutes without changes; the data passes through Apple's push notification service, section 5), and closes it at the end of service. If nothing updates it any more, it keeps the latest data: on Android it is removed automatically at the end of service or, at the latest, after 4 hours; on iPhone when the app is reopened or, at the latest, after a few hours;
- photos taken and files opened with the app, for as long as needed (in the Android app they are deleted the first time the app is reopened after one day). Files saved by the user, such as PDF prints or the customer list export, stay where they were saved.
The apps use the camera only on iPhone, iPad and Android and only when the user chooses to take a photo to attach, for example to a booking. Sandtick does not add advertising, analytics or crash-reporting tools to the apps (the Android app only contains Google's library for notifications) and the apps keep no logs with personal data; the operating system may send diagnostic data according to the device settings. While open, all the apps ask Sandtick's servers for news and prepare the notifications themselves (on the computer also with the window closed or hidden); the Android app also receives them through Google, as described above. On Android the service panel is prepared by the app on the device and does not go through third-party services; on iPhone Sandtick's updates go through Apple, as described above.
Signing out closes access and deletes from the device the copy of the bookings, the saved pages, the notifications, the service panel and, after a warning, the changes made without a connection and not yet sent. If access ends in another way (for example a disconnected device or a changed password) or the licence expires, those changes stay on the device and are sent only if the same account signs in again. After 7 days they are no longer sent and are deleted the next time the app is opened on that device. The copy and the saved pages are also deleted when a disconnected device reopens the management area with a connection. Uninstalling the app on Windows, iPhone, iPad or Android deletes all the app's data; in the browser it is deleted with the site data.
Data is not used for advertising or profiling and is not sold or transferred to third parties. The management area uses only technical cookies: sign-in, the mark of a device already used to sign in, display preferences, in the Android, iPhone and iPad apps and in the Mac App Store app for Mac one that says the page is open in the app (400 days) and, while a Gmail mailbox is being connected, a check cookie lasting 15 minutes. In the browser, the page for connecting WhatsApp loads Meta's connection tool, which receives the IP address and may use its own cookies (section 3).
The customers' booking page and the sign-up page use no cookies of their own. They load Cloudflare's Turnstile anti-bot check; the booking page, when the restaurant asks for a guarantee card, also loads Stripe's form. These services may use cookies or similar technologies, technical and for security, to detect abuse and fraud, as stated in their privacy policies.
3. WhatsApp integration
A restaurant can connect its WhatsApp Business number to Sandtick through Meta's WhatsApp Business Platform. The connection takes place in a window managed by Meta: Sandtick does not receive the Facebook password or the personal profile data of the person connecting.
Once connected, Sandtick receives from Meta the ID of the WhatsApp Business account and of the phone number, the number's display name and an access token for sending messages on behalf of the restaurant. This data is used only to:
- create the restaurant's message templates (booking confirmation, change, cancellation and reconfirmation, guarantee card request and review request) and submit them to Meta for approval;
- send the restaurant's customers messages about their booking, when the restaurant has requested it;
- receive from Meta the status of the messages sent (delivered, read, not delivered) and show it to the restaurant.
Sandtick does not send promotional messages on its own initiative (a review request is sent only when the restaurant asks for it for a single booking) and does not store the messages customers write to the restaurant, which remain on WhatsApp. The restaurant can revoke the connection at any time; the tokens received from Meta are then deleted.
4. Gmail integration
A restaurant can connect its Gmail mailbox to Sandtick, so that the e-mails to its customers (booking confirmation, change, cancellation and reconfirmation, guarantee card request and review request) are sent from its own address and stay in its sent mail. The connection takes place on Google's page: Sandtick never receives the account password.
Sandtick asks Google only for permission to send e-mails on behalf of the restaurant (gmail.send) and for the account's e-mail address. It does not read, modify or delete the e-mails in the mailbox. The token received from Google is stored in encrypted form and used only to send the restaurant's booking e-mails.
Sandtick's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. This data is not used for advertising, is not sold and is not read by humans, except at the restaurant's request, for security purposes or to comply with the law.
The restaurant can disconnect the mailbox at any time from the management area or from its Google account settings; the token is then deleted.
5. Service providers and transfers outside the EU
To provide the service we use the following providers, appointed as processors or sub-processors:
- Cloudflare, Inc. – hosting, database and file storage, with data stored in Western Europe (United Kingdom, a country covered by an adequacy decision of the European Commission), and the anti-bot check (Turnstile) of the booking page and of the sign-up page, which receives the IP address of whoever fills in the form;
- Meta Platforms Ireland Ltd – sending WhatsApp messages, if enabled by the restaurant, and, in the browser, the tool for connecting the WhatsApp number, which receives the IP address of whoever opens the messages page;
- Google LLC – sending e-mails from the restaurant's Gmail mailbox, if connected, and service messages to account holders (for example password recovery) from Sandtick's Gmail mailbox, which is also used to send bug reports to Sandtick; delivery of notifications to the Sandtick app for Android (Firebase Cloud Messaging), with the notification data described in section 2;
- Apple Inc. – delivery of notifications and dinner panel updates to the Sandtick apps for iPhone and iPad (Apple Push Notification service), with the data described in section 2;
- Stripe Payments Europe, Ltd. – card payment of the subscription, with the billing data (account holder, e-mail, address and restaurant name); connection of the restaurant to its own Stripe account, with the owner's e-mail and the restaurant name; for restaurants that turn it on, the guarantee card of their customers on their own Stripe account, with the customer's first and last name, e-mail, phone number and language.
The United Kingdom is covered by an adequacy decision of the European Commission (renewed on 19 December 2025): data stored there is protected as in the European Union. Any other transfer of data outside the European Union is based on the standard contractual clauses approved by the European Commission or on the EU-U.S. Data Privacy Framework.
6. Retention
Account and restaurant data, including its customers' data, is kept while the restaurant uses the service, unless the restaurant deletes it earlier. If the subscription ends, or the free trial expires without a subscription, it is kept for 6 months, so a restaurant that comes back finds everything as it was; after that it is deleted: for a restaurant with a lot of data the deletion may take a few weeks, and once it starts the account can no longer be opened. Before deletion the restaurant may ask for the data to be returned.
Invoices and payment data are kept for 10 years, as required by tax law. The billing data of anyone who never paid for a subscription is deleted together with the restaurant's data, along with the customer on Stripe. The periods stated in section 2 remain unaffected.
So that data can be recovered after a failure, a backup copy is made every night, kept for 30 days with the same provider (Cloudflare) and then deleted automatically: deleted data therefore also disappears from the backups within 30 days.
7. Security
All communication takes place over an encrypted connection (HTTPS). Passwords are stored in hashed form, each restaurant can access only its own data and each account only the functions allowed by its role.
8. Your rights
You may at any time request access to your data, rectification, erasure, restriction of processing or portability, or object to processing, by writing to support@sandtick.com. You may also lodge a complaint with the Italian Data Protection Authority (www.garanteprivacy.it).
Customers of the restaurants can contact the restaurant directly, as controller of their data. Requests about this data that reach us are forwarded to the restaurant concerned.
9. Data deletion
How to delete your account with Sandtick, the app by 266 La Barraca S.R.L., and its data.
- From the app or the browser: sign in at app.sandtick.com with your e-mail and password, open Account and tap «Elimina il mio account» (Delete my account), at the bottom of the page above «Esci» (Sign out); the page says what will be deleted and when. Enter your password and confirm. If the licence has expired, «Elimina il mio account» is on the «Licenza scaduta» (Licence expired) page. You receive a confirmation e-mail.
- What is deleted: for staff, and for an owner when the restaurant has another owner, their own account in all the restaurants they work in; the restaurant stays, with the bookings taken by that account and its name. When the last owner asks (or the last of the owners, if they all ask), the restaurant is also deleted with all its data (bookings, customer list, floor plans, settings, messages), together with the staff accounts that work only there and the WhatsApp and Gmail connections with the related tokens; the subscription is cancelled at once, with no further charges.
- When: 7 days after the request (requested on 15 October, deleted on 22 October). Until the day before, it can be cancelled with «Annulla l'eliminazione» (Cancel deletion), from the app or from the confirmation e-mail. From the day of deletion the account no longer opens and all devices are signed out; the data disappears completely within 30 days (a restaurant with a lot of data is deleted over several nights) and from the backups within a further 30 days.
- What remains: if a subscription was paid, invoices, billing data and payments, with the restaurant's name, for 10 years as required by tax law (section 6), and the subscription payments on Stripe; e-mails and WhatsApp messages already sent, in the recipients' mailboxes and in the sent mail. Bug reports that reached Sandtick by e-mail are kept for as long as the restaurant's data is kept (section 2): if the restaurant is deleted too, Sandtick deletes them within 30 days. The restaurant's Stripe account used for the guarantee card belongs to the restaurant and is closed from Stripe; guarantee cards still saved are removed before the data is deleted. The name, e-mail and phone number of the person who asked for the deletion are removed from the change log and bug reports (if the restaurant stays) and from Sandtick's internal log.
- If you cannot sign in to the app, you can ask for deletion by writing to support@sandtick.com from the account's e-mail address. The owner can also delete staff accounts and individual customer records straight away in the management area.
- WhatsApp connection: it can be revoked from the management area or from Meta Business Suite (Settings → Integrations). From that moment the tokens received from Meta are no longer valid and are deleted.
- Restaurants' customers: the request should be made to the restaurant, which can delete the record in the management area. Alternatively, write to support@sandtick.com stating the restaurant and the phone number used for the booking.
10. Changes
This policy may be updated; the date of the latest version is shown at the top.