Skip to content
CantiereGO

Privacy notice

Version 2026-10-22 · Effective from 22 October 2026

The Italian text is the binding one. This page translates it as a courtesy: the original is the Informativa sulla privacy.

This notice explains how A176lab S.r.l. processes personal data when you visit this site and when you use the CantiereGo app (app.cantierego.it), under Articles 13 and 14 of Regulation (EU) 2016/679 (GDPR). The cookies and the data the app keeps in the browser are described on the Cookies and local data page.

1. Controller and processor

The data controller (titolare del trattamento) for the site and for the app’s account data (name, email address, phone number, language, sessions, billing details: section 3) is A176lab S.r.l., Via Madonna dell’Altomare 23, 91011 Alcamo (TP), VAT no. 02812750814. For any question about this notice, or to exercise your rights, write to info@cantierego.it.

The data about workers that a client company records in its own workspace (section 4) is the company’s instead: the client is its controller, and A176lab processes it on the client’s behalf as a processor (responsabile del trattamento) under Article 28 GDPR, as Article 6 of the Terms of service provides.

2. The site

This site sets no cookie, stores nothing in your browser, has no form, runs no script and uses no analytics or advertising tool. Fonts and images come from the site itself: to show you its pages, the browser contacts no other address. Like any site, it receives your device’s IP address in order to deliver the pages, through AWS’s content delivery network (CloudFront); it keeps no access log and counts only the total number of requests, without addresses.

The info@cantierego.it link opens your own mail program: if you write to us, we use the message to reply and keep it for as long as the request needs. Links to other sites, such as the sources on the Regulations page, take you to third parties, which have their own privacy notices.

3. Account data

What we collect. When you register a workspace: your first and last name, email address, password, your company’s registered name and the page’s language. When you accept an invitation: your first and last name and the email address or phone number the invitation reached, which the person who invited you gave us, plus a password if the invitation came by email; with an invitation by text message you sign in with a code sent to your phone. The password is kept only as a cryptographic hash (argon2), never in clear. For every account we then record:

  • the account’s language, which decides the language of the screens, the emails and the text messages;
  • the active sessions, with the time each began and was last used, the IP address and the device type, which you can see and close from your profile;
  • the second authentication factor, if you turn it on, whose secret is stored encrypted, and the one-time codes sent by email or by text message, valid for ten minutes;
  • the account’s activity log: sign-ins, failed attempts, sign-outs, changes of password, of the second factor and of the language, each with the time, the IP address and the device type.

The consents. When you register, and when you accept an invitation that creates your account, we record your acceptance of the Terms of service and of this notice and your choice about marketing messages, each with the version of the text, the time, the IP address and the device type.

Billing. If a workspace’s owner activates a paid plan (Article 4 of the Terms of service), we process the workspace’s billing details — registered name, VAT number, tax code, address, SDI recipient code and certified email, which for a sole trader or a professional are personal data — and the email address the receipts reach, and we receive from Stripe the type and the last four digits of the payment method. The card number and the IBAN are entered on Stripe’s pages and never reach A176lab. Every invoice and credit note keeps a copy of the billing details as they were at the payment. We process this data to perform the contract (point b) and to meet our tax and accounting obligations (point c).

Why, and on what basis. We process this data to provide the app and manage your access, because it is necessary for the performance of the contract (Article 6(1)(b) GDPR); to protect the service from abuse and know who did what, in our legitimate interest (point f); and to meet our legal obligations (point c). Marketing messages need your consent (point a), which is optional and which you can withdraw at any time by writing to info@cantierego.it.

The session. A browser session lasts ninety days at most, twenty-four hours for a platform administrator, and ends sooner if it stays idle beyond a window that is renewed every time you use it; signing out ends it at once. The cookie that holds it is described on the Cookies and local data page.

The messages. The app writes to you by email or text message only for the service: for instance confirming your address, recovering your password, sign-in codes, invitations, the copy of the timesheets sent to the consultant. Every message is in your account’s language. If one of our emails bounces or you mark it as spam, your address joins the mail service’s suppression list and receives no further messages.

Protection from abuse. To stop repeated attempts we briefly count requests per IP address and per account; these counters expire after one hour at the latest.

4. Workers’ data, processed for the client

A client company records in its own workspace the data of the people who work on its sites. The client is the controller of that data: it gives the workers its own privacy notice and decides how long to keep the data; A176lab processes it only to provide the app and on the client’s instructions. It is:

  • personal details and employment: first and last name, tax code, date and place of birth, nationality, address, phone, email, job title, employer, hire and end dates, the office’s notes;
  • compliance facts: for training courses and for the medical fitness judgement, the dates, a reference and any note from the office, with no health records; of the employer’s patente a crediti and DURC, the status and the dates;
  • photo, re-encoded by the app and shown only through the app or the verification page, never through a public link to the file store;
  • sites: the assignments, with their dates, the role and the accreditation;
  • badge: the QR code and the history of the state the compliance engine computes, with the suspensions, blocks, revocations and overrides the office decided and their reasons. The public verification page, which scanning the QR code opens, shows the verdict with its reasons and warnings and their dates (an expired fitness judgement, for instance), the photo, the name, the employer and the hire date, and never the tax code or the birth details;
  • attendance: for every punch, the time, whether it is an entry or an exit, the channel (the gate, a delegated kiosk, the worker’s wallet, an office entry), the site, who recorded it, the badge’s verdict at that moment, the IP address and the device type; when the device sent a position, the distance from the site and the accuracy of the fix; when the punch was recorded without the badge or by hand, the reason and the document the worker was identified with; any note from the office. An office correction never deletes a punch: it voids it, with the reason, who voided it and when. The coordinates are never kept, neither on the server nor on the phone: the position is used to compare with the site’s perimeter and is discarded at once;
  • geolocation notice: the wallet shows it before the first punch with a position and records its acceptance with the version of the text, as proof that the worker was informed;
  • timesheets: the monthly package of attendance hours, per worker, day and site with the detail of the punches, which the app emails to the payroll consultant the client names, without distance, accuracy, IP address or device.

The badge’s state is computed automatically from the facts the office records, but no decision with legal effects on a worker is taken by automated means alone: the office can suspend, block, revoke or grant an override, and a punch the phone refused can always be recorded at the gate. Whoever uses the wallet has an account like any other user (section 3), while their punches and their badge’s data remain the client’s.

5. How long

  • Account: for as long as the account exists; expired sessions are deleted automatically. When the account is deleted, its consents and sessions are deleted with it, while its entries in the activity log stay with the data they recorded: the account’s identifier, the IP address and the browser of each action and, for the registration and for failed sign-in attempts, the email address. Those entries have no automatic deletion term today: you can ask for their deletion at info@cantierego.it, and A176lab carries it out unless the law or the service’s security requires keeping them.
  • A workspace’s activity log: its entries are the client’s data and are deleted with the workspace, within forty days of its closure; for at least thirty days after the closure the owners can still reopen it or export its data (Articles 6.9 and 11.1 of the Terms of service).
  • Attendance: a deactivated worker’s punches are kept for the period the client sets, five to ten years (five if it does not choose), counted from the end of the employment or, when no end is recorded, from the deactivation; the punches of a worker who is not deactivated are never deleted. The deletion is automatic, once a month, and the client can suspend it with the legal hold while a dispute or an inspection is open. The timesheets sent to the consultant follow the same term, counted from the month they cover.
  • Personal details, compliance facts and photos: for as long as the client keeps them in its workspace. A replaced or deleted photo stays for thirty days as a previous version in the file store, then it is deleted. At the end of the contract, the return and deletion that Articles 6.9 and 11.1 of the Terms of service provide apply.
  • Imports: the uploaded file is deleted as soon as it has been read, and within eight days in any case; the import’s report after ninety days.
  • Technical logs: thirty days, with the last part of every IP address zeroed.
  • Billing: the invoices and credit notes, with the copy of the billing details, for ten years from the document’s date (Article 2220 of the Italian Civil Code), after the workspace’s closure too; the subscription and the reference to the customer registered at Stripe for as long as the workspace exists, and the customer at Stripe is deleted with the workspace; an uncompleted purchase session ninety days; the payment events received from Stripe thirty days, one not yet applied up to a year. Stripe keeps the payment data for its own legal obligations.
  • Backups, in the same AWS region of Milan, each on its own cycle: full copies of the database, with the log of its changes, for fourteen daily runs; daily database exports for thirty-five days; snapshots of the data disk for seven days. The backup store keeps every deleted copy for a further thirty-five days as a previous version: deleted data leaves the backups after about seventy days.
  • Error reports: sent to Sentry without the content of the requests, without cookies and without the parameters of the addresses, with the secret codes in paths masked; they stay at Sentry for the retention period of its service.

6. Recipients and sub-processors

The data is accessed by A176lab’s authorised staff and by the providers below, each bound by a data processing agreement:

  • Amazon Web Services (AWS), in the Milan region (eu-south-1): the server (EC2), the store of files and backups (S3), sending emails (SES) and text messages (SNS), and the CloudFront content delivery network, which serves the pages from points of presence in Europe, Israel, Turkey, the United States, Mexico and Canada (section 7);
  • Sentry, with the data in its European Union region, for error reports;
  • Zoho Mail, in its European data centre, for the info@cantierego.it mailbox;
  • Stripe (Stripe Payments Europe, Ltd., Dublin), for the plans’ payments: it receives the client’s registered name, VAT number, address and billing email and collects the payment method on its own pages. For the payment Stripe processes the data as an independent controller, under its own notice; the card number and the IBAN do not reach A176lab.

The payroll consultant the client names receives the monthly package of attendance hours as an independent controller. The data is disclosed to the authorities when the law requires it. No data is sold or used for advertising or profiling.

7. Transfers outside the European Union

By design the data is stored in the European Union: the server, the file stores and the backups are in the AWS region of Milan, and Sentry and Zoho Mail keep it in the Union. To deliver the pages, CloudFront uses the points of presence of the chosen price class, which covers Europe, Israel, Turkey, the United States, Mexico and Canada, and AWS notes: “From time to time, your content may be served from an edge location that is not included in your price class.” A point of presence only terminates the encrypted connection and does not keep the app’s responses that carry personal data; that passage is covered by AWS’s data processing addendum and by the standard contractual clauses the European Commission approved. Stripe processes the data in Ireland and may transfer it to the companies of its group in the United States: the transfer is covered by the adequacy decision for the EU-US Data Privacy Framework, which Stripe, Inc. adheres to, and by the standard contractual clauses.

8. Your rights

You can ask for access to your data, its rectification, its erasure, the restriction of its processing and its portability, and object to processing based on legitimate interest (Articles 15 to 22 GDPR); you can withdraw a consent at any time, without affecting what happened before. Write to info@cantierego.it: we reply within one month. You also have the right to lodge a complaint with the Italian supervisory authority, the Garante per la protezione dei dati personali (www.garanteprivacy.it).

If you are a worker, for the data the company keeps about you (section 4) turn to the company, which is its controller; if you write to us, we forward the request to the company and help it answer. In the wallet you can see your punches and download them in a file.

9. Security

Connections are encrypted from your browser to the server, and the disks and file stores are encrypted. Each client’s data is kept apart in the database by row-level security rules, and every user sees only what their role allows. Passwords are stored as argon2 hashes, access can be protected with a second factor and repeated attempts are stopped. The activity log traces sign-ins and changes. Backups are continuous, and every quarter a restore test checks that they work. To report a vulnerability, write to info@cantierego.it, the contact published in the site’s security.txt file.

10. Changes

When it changes, this notice gets a new version, with the date from which it applies, shown at the top of the page. Every acceptance is recorded with the version accepted. If a change is material, we tell registered users by email.