Skip to content

Privacy policy

Last updated: 19 October 2026

This page explains which personal data the ailligence.it website collects, why, for how long and what your rights are. It describes how the site actually works: if anything is unclear, write to me.

Data controller

Giovanni Tempesta, owner of the Ailligence brand
Via Piscina Nuova 1, 70010 Adelfia (BA), Italy · VAT no. IT08708320729
Email: giovanni.tempesta@ailligence.it · Phone: +39 327 174 2214

You can use these contact details for any request about your data. No data protection officer (DPO) has been appointed, as it is not required for this activity.

What data I collect and why

1. Requests sent through the forms

The site has a few forms. I collect the data you write:

  • Contact: name, email, phone, company and subject (optional) and message.
  • Quote request: name, email, phone, company (optional), type of service, budget, timing and project description.
  • Product information: name, email, company and message (optional) and the product you are interested in.
  • Free first AI consultation: name, email and/or phone, company (optional) and what you would like to improve.
  • AI Code Check-up: name, email, phone and company (optional), whether to invoice the company, the description of the app, what it was built with, where the code is, whether it is online, whether it has users, whether it handles sensitive data, your concerns and the package you are interested in.
  • Why: to answer your request, prepare a quote or a proposal, and arrange the consultation or the Check-up.
  • Legal basis: pre-contractual steps taken at your request (Art. 6(1)(b) GDPR). The «I have read the privacy policy» box only confirms that you have read this page: it is not consent.
  • How long: requests are deleted automatically 24 months after the last contact (the last update of the request). If the request becomes an assignment, the data is kept for the duration of the relationship and then for the period required by law for accounting and tax records (10 years).
  • Required fields: fields marked as required are needed to answer you; without them I cannot follow up on the request.

For the consultation and the Check-up I also store the language of the page, the time you confirmed you had read this policy and, if present in the address, the campaign parameters you arrived with (utm_source, utm_medium, utm_campaign, utm_term, utm_content), to know which channels bring requests. For the consultation I only store whether there was a Google Ads click code (gclid, gbraid or wbraid), yes or no, without the code; for the Check-up, point 2 applies.

I do not store your IP address or your browser with the requests.

When a request arrives I receive an email notice that contains only the type and number of the request (with the date, page and campaign it came from), without any of your personal data. I read the request only in the site's admin panel. Contact, quote and product information requests also appear as a notification in the panel, which is deleted together with the request. For the Check-up you also receive an automatic confirmation email.

2. Measuring Check-up requests that come from Google Ads

If you reach the AI Code Check-up page from a Google Ads ad, the address contains a click code (gclid). Only if you allow it with the optional box in the form, I store that code with the request and make it available to Google Ads, to know whether the ad brought a request. Every day Google downloads, from a password-protected address of the site, only this data:

  • the click code;
  • the name of the conversion (for example «Richiesta check-up»);
  • date and time of the request, with the time zone;
  • the indication that the data may be used to measure the ad but not for personalised ads.

Google does not receive your name, your email or the text of your request.

  • Legal basis: consent (Art. 6(1)(a) GDPR), optional and withdrawable at any time by writing to me, with no effect on your request. If you withdraw it, I delete the code at once and the request is no longer made available to Google; data Google has already downloaded remains subject to its own terms.
  • How long: the code is deleted 90 days after the request; only the date of the consent remains, as proof that it was given.
  • Recipient: Google Ireland Limited (Ireland), independent controller for the Google Ads service; Google may transfer data to the United States under the EU-US Data Privacy Framework.

3. Visit statistics, cookie-free

To know how many people visit the pages and where they come from, I use my own statistics system, hosted on the site, with no cookies and no third-party services. It records:

  • the page viewed and the language;
  • whether the device is a phone;
  • the domain of the site you come from (not the full address);
  • the campaign parameters utm_source, utm_medium, utm_campaign and utm_content;
  • the source of the visit in categories (for example Google Ads, Google search, LinkedIn, direct), derived also from the presence of a Google Ads click code, which is not stored;
  • the time spent on the page in ranges (under 10 seconds, 10-30, 30-60, over 60);
  • clicks on the contact buttons (WhatsApp, quote, consultation);
  • on the Check-up page, whether you reach the prices and the form, start filling it in and send it.

Each page load has a random code that ties together the events of that visit: it only lives in the page and is not stored in the browser. The time of day is stored to the hour only.

To count the unique visitors of a day, an irreversible fingerprint is computed from the IP address and the browser, with a random key that changes every day and is deleted the next day. The IP address is not stored; once the day's key is deleted, the fingerprint can no longer be traced back to a visitor, nor linked to the fingerprints of other days. I only view the data in aggregate form, I do not combine it with other information and I do not share it with third parties.

  • Legal basis: legitimate interest in knowing how the site is used, in aggregate form (Art. 6(1)(f) GDPR). You can object by writing to me; you can also block the statistics by disabling JavaScript.
  • How long: individual events 90 days, daily totals 25 months.

4. Browsing, security and spam protection

Like any website, the hosting provider's server records some connection data in its technical logs (IP address, date and time, page requested, browser). They are needed for the site to work securely and are kept for the period set by the hosting provider.

The site stores the browsing session in its own database, with IP address and browser: it is needed for the forms to work (technical cookies, see the cookie policy) and is deleted within a few hours of the last page visited.

To protect the forms from spam I use:

  • a hidden field that only automated programs fill in;
  • a limit on the number of submissions per IP address, stored in hashed form only for a few minutes or an hour;
  • for the contact, quote and product information forms, a limit of one submission every few minutes for the same email.

I do not use third-party services such as reCAPTCHA.

The site's errors go to a log that only I can access, kept for 14 days.

  • Legal basis: legitimate interest in the security of the site (Art. 6(1)(f) GDPR).

5. Direct contact: email, phone and WhatsApp

If you email me, call me or message me on WhatsApp through the site's links, I use the data you send only to reply to you, under the same rules as point 1. The links to WhatsApp, LinkedIn and GitHub lead to external services, which process data under their own privacy policies (for WhatsApp: WhatsApp Ireland Limited, Meta group).

6. Clients and reserved area

The data of clients using the reserved area (management of projects, tasks and hours) is processed to perform the contract and for the related legal obligations; they receive a specific notice when the assignment starts.

7. Legal claims and requests from authorities

If it is needed to defend a right in court or to answer a lawful request from an authority, I may use and disclose the necessary data, even beyond the periods above, only for as long as needed (Art. 6(1)(c) and 6(1)(f) GDPR).

Who processes the data

The data is processed by me, with IT tools and appropriate security measures (encrypted connection, protected access to the admin panel). I do not sell or share data with third parties for marketing. The following technical service providers may process it on my behalf, as data processors:

  • Hostinger, which hosts the site, the database and the mailboxes on servers in the European Union;
  • MailerSend, which sends the site's emails (request notifications and the Check-up confirmation).

The up-to-date list of processors is available on request. Apart from what is described in point 2 for Google Ads, the email sending service may use sub-processors outside the European Union, with appropriate safeguards (European Commission standard contractual clauses or the EU-US Data Privacy Framework).

Your rights

Under Articles 15-22 GDPR you can ask at any time to:

  • know which of your data I process and get a copy (access);
  • correct or update it (rectification);
  • delete it (erasure), unless I must keep it by law;
  • restrict its processing;
  • receive it in a machine-readable format (portability);
  • object to processing based on legitimate interest;
  • withdraw the consent you gave (point 2), without affecting processing already carried out.

If I correct or delete your data, or restrict its processing, I also tell whoever received it (for example Google Ads, point 2), unless this is impossible or involves disproportionate effort.

Write to giovanni.tempesta@ailligence.it: the request is free and I reply within one month. You also have the right to lodge a complaint with the Italian Data Protection Authority (garanteprivacy.it) or with the authority of the EU country where you live or work.

Cookies

The site only uses technical cookies. Details are in the cookie policy.

Changes to this notice

If I change the way the site processes data, I update this page and the date at the top. If a change requires your consent, I will ask for it again.