UAPgradeUAPgrade Italiano

Policy

Privacy notice

Version 1 · 2 November 2026

In short

  1. Who is responsible
  2. What data, why and on what legal basis
  3. When you read the site
  4. When you write to us or take part
  5. Automated moderation and human review
  6. Vega and artificial intelligence
  7. People mentioned in the archive
  8. Social media and donations
  9. Who receives the data
  10. Data outside Europe
  11. How long we keep data
  12. Your rights
  13. Complaints
  14. Minimum age
  15. Security
  16. Changes to this notice

Who is responsible

The data controller is Fabio Guzzon, an individual based in Italy. He decides why and how the data collected by UAPgrade (uapgrade.com) is used. On this page, “we” means him.

For privacy questions and anything else, write to redazione@uapgrade.com, in English or Italian.

The project also carries the Adattica brand, but Adattica is not a separate controller: the controller is Fabio Guzzon.

What data, why and on what legal basis

The law requires every use of personal data to rest on a legal basis: one of the grounds listed in Article 6 of the EU General Data Protection Regulation (GDPR). We rely on these:

The archive and the news deal with people and facts of public interest, so the rules on freedom of information also apply to them (Art. 85 GDPR and Articles 136-137 of the Italian Privacy Code).

What we doWhich dataWhy · legal basis
Show you the site and protect it from abuseYour IP address, used on the spot and kept for a few days in the server's access log; in the database, only if you send us something, a fingerprint that changes every day (for scenario votes, a fixed one: see Votes on scenarios)Running the site and stopping repeated submissions and attacks · legitimate interest (6(1)(f))
Keep statistics without cookiesSection viewed, language, domain you came from, device type; in bands: time on the page, scrolling, pages per visit; domains of external links opened; campaign tags in linksUnderstanding what readers find useful and improving the site · legitimate interest (6(1)(f)). We only store daily totals.
Count returning visitorsA random code that stays in your browser; the server only receives “new” or “returning”Knowing how many readers come back · consent (6(1)(a)), given in the cookie banner
Remember your preferencesLanguage, stopped animations, investigator name, cases already shown in the case boxRemembering your choices · a service you ask for (6(1)(b)). They stay in your browser.
Remember your cookie choiceChoices made in the banner, policy version, dateRespecting your choice and being able to prove it · legal obligation (6(1)(c)) and legitimate interest (6(1)(f))
Confirm submissions by emailEmail, the text of the pending submission, daily IP fingerprintChecking the address is yours before accepting the submission · a service you ask for (6(1)(b))
Answer messages from the Contact pageName, email, reason, textReplying to you · a service you ask for (6(1)(b)) or, if the message isn't about a service, our legitimate interest in replying (6(1)(f))
Handle reports of illegal content and send statements of reasons for our decisionsFrom the person reporting: name, email and the text of the report. From the author of the content: email, the content and the reason for the decisionComplying with the EU Digital Services Act (DSA) · legal obligation (6(1)(c))
Publish comments on the newsAlias and text (public); email (private); daily IP fingerprintPublishing the comment after moderation · a service you ask for (6(1)(b))
Publish scenario proposals and put them to the voteAlias, title, text, links and people named (public); email (private); the code in the osv_v cookie; for votes, an IP fingerprintPublishing the proposal and counting one vote per browser and per connection · a service you ask for (6(1)(b))
Assess contributions to the Investigations UnitInvestigator name (public on the roster and in the contribution log, with verdicts, points, rank and reliability), title, text, links; email (private)Checking the material, awarding points, keeping the investigators' roster · a service you ask for (6(1)(b))
Send the newsletterEmail, language, dates of subscription and confirmationSending you the daily news · consent (6(1)(a)), with double opt-in
Answer questions to VegaQuestion (400 characters at most), the page you are on, daily IP fingerprintAnswering you and counting the day's questions · a service you ask for (6(1)(b))
Update the archive and write the daily newsContributions and proposals, without emails; public sourcesKeeping the archive checked and informing the public · legitimate interest (6(1)(f)), under the freedom of information rules (Art. 85 GDPR)
Mention people in the archiveNames, roles, public statements, documented links, authority index, freely licensed portraits; for David Grusch and Luis Elizondo, in the comparison between the two, portraits created with artificial intelligence and labeled as suchInforming the public and checking claims of public interest · freedom of information (Art. 85 GDPR, Arts. 136-137 Italian Privacy Code)
Run the site from the Redazione, Fabio's private editorial areaThe editorial email address, fingerprints of login links and sessions, uapg_red cookie, action log (numbers, never emails)Running the site and keeping track of decisions · legitimate interest (6(1)(f))
Communicate on social mediaWhat you do on our profiles, such as comments and messages; platform statisticsMaking the site known and talking with our followers · legitimate interest (6(1)(f))

We don't use your data to profile you, we don't sell it and we don't use it for advertising.

When you read the site

IP address

To send you pages, the server has to use your device's IP address. We never store it in the database. When you send us something (a message, a comment, a proposal, a contribution, a newsletter sign-up or a question to Vega), we only store a “fingerprint”: a code computed from the date, the IP address and a secret key (with the SHA-256 algorithm), which can't be traced back to the address without the key. The fingerprint changes every day and is deleted within a few hours of the end of the day. It lets us set limits, for example on how many messages can arrive from the same connection in one day. If you only read, the fingerprint is used only in the server's memory, for the limits, and never goes into the database. Votes on scenarios use a different fingerprint: see Votes on scenarios.

The server's technical logs, such as error logs, rotate: at most 3 files of 10 MB, after which the oldest are overwritten. The program that routes requests to the sites hosted on the server (Traefik) also keeps an access log: IP address, date and time, page requested, the server's response and the browser used. It is for security and troubleshooting, on the basis of legitimate interest; it rotates the same way (3 files of 10 MB) and today covers a few days.

Statistics

We run our own statistics, on our server, without cookies and without anyone else's services (no Google Analytics or anything like it). After each page, your browser sends us a signal with a few details: the section you opened, the language and, on the first page only, the site you came from (just the domain, for example “google.com”). From the signal we can also tell whether you're on a phone or a computer. Then, in bands: how long you stay on the page, how far you scroll and how many pages you see during the visit. We also count the domain of the external links you open and, if you arrived through a link with a campaign tag (for example one of our posts), that tag.

Only daily totals go into the database, along the lines of “how many times the map was opened on Tuesday”. We don't store your IP address, a row for each visit or the exact name of your browser: the statistics can't be traced back to you.

To count the pages in a visit, your browser keeps a small note in the tab's memory (sessionStorage). It never leaves your browser and disappears when you close the tab: the server only receives the page's position in the visit (first, second, third…).

Returning visitors, only if you accept

If you accept it in the cookie banner, your browser keeps a random code (in localStorage) for up to 13 months. At most once a day it tells the server only “new” or “returning”: the code itself never leaves your browser. If you refuse, nothing is stored, and if you withdraw your consent the code is deleted.

The cookie banner

The banner follows the Garante's guidelines of 10 June 2021. “Accept” and “Refuse” are equally prominent; closing the banner with the X counts as refusing; with “Customize” you choose item by item, and no optional box is ticked in advance. Your choice is kept for 6 months in the technical cookie uapg_consenso, together with the policy version. You can change it at any time from the “Cookie preferences” link at the bottom of the site's pages.

Preferences and technical cookies

Your browser remembers some choices you make: your language, whether you stopped the animations, your investigator name and, until you close the tab, which cases we have already shown you in the box of cases without an official identification. They stay in your browser until you delete them. The technical cookie osv_v is only created if you propose or vote on a scenario: it recognizes your proposals and votes, and lasts one year.

No other services in our pages

Fonts and libraries, such as the ones for the map and the charts, come from our own server: opening the site doesn't make your browser contact anyone else's services.

To see how the site shows up in search results, we use Google Search Console. Google shows us aggregated search data, for example how many times a page appeared in the results, and is an independent controller of that data. There is no Google code on the site.

The names, purposes and durations of all cookies and browser storage are on the Cookies page.

When you write to us or take part

Your email: when we need it

You don't need an email address to read, vote on a scenario or ask Vega a question. We do ask for it for:

In these cases the email address is required: without it, the submission can't be sent. We need it to know the address is yours and that a person is behind the submission. We also use it to reply when you write to us, to tell you why if we don't publish a comment or scenario proposal of yours and, for the newsletter, to send you the news.

Confirmation

After you submit, you get an email with a link that is valid for 48 hours. Your submission only goes through when you open the link and press “Confirm”. Until then nobody reads or publishes it; if you don't confirm, it deletes itself.

What stays private and what becomes public

If you'd rather stay private, pick an alias that isn't your full name. And please don't put personal details about yourself or others in public texts.

Newsletter

You subscribe with double opt-in and get an email for each new daily news article, in your language. Every email has a link to unsubscribe in one click. The emails contain no tracking pixels: we don't know whether or when you open them. When you unsubscribe, your address is removed from the subscriber list. Two things remain, without your address: the sending log, for 24 months, and the code of the unsubscribe link you used, a fingerprint that lets us still reply “unsubscribed” if you open the link again.

Votes on scenarios

You don't need an email address to vote. To count only one vote per browser and per connection, we use the technical cookie osv_v and an IP fingerprint computed with the secret key, which in this case doesn't change every day. Votes, with the cookie code and the fingerprint, are kept while the proposal can still be voted on. After that they are deleted: 30 days after the proposal joins the site's scenarios, or 12 months after it is discarded.

Reports and decisions about content

If you report content you believe is illegal, we use your name, your email and the text of your report to examine it and reply to you, as the EU Digital Services Act (DSA) requires. We don't tell the author of the content who reported it, unless this is strictly necessary. If we don't publish or we remove a comment or scenario proposal of yours because it is illegal or breaks the rules, we email you the reason at the address you confirmed (except for spam); for a contribution, you can ask us for the reason.

What may be published is explained in the Terms and rules, which also explain how to report content and how to challenge a decision.

Automated moderation and human review

Comments and scenario proposals aren't published straight away. First they go through two automatic checks:

  1. Simple anti-spam rules, for example too many links, shortened links, typical spam words or text written all in capitals.
  2. A verdict from Anthropic's AI, which reads the text (for comments also the alias and the article's title and summary, for proposals also the links).

Messages from the Contact page don't go through the AI: Fabio reads them.

These decisions only concern whether a text appears on the site or how many points it gets: they have no legal or financial effect on you. You can still ask for a person to review them. Write to redazione@uapgrade.com saying which submission it is, for example the article and the day of your comment: Fabio will look at it himself and reply.

Vega and artificial intelligence

UAPgrade uses Claude, Anthropic's artificial intelligence, through Fabio's personal Claude subscription. We use it for:

What Anthropic receives

We never send Anthropic email addresses or IP addresses.

Anthropic's role

Because this is a personal subscription, governed by Anthropic's consumer terms, Anthropic processes this data as an independent controller, in the United States, under its own privacy policy. Fabio checks that the subscription setting that lets Anthropic use the data to train its models is switched off.

What we keep

Questions to Vega stay in our log for 40 days. The same log records each automated moderation, with the first 200 characters of the comment or the proposal's title: these entries are also kept for 40 days. The daily fingerprint that counts your questions for the day is deleted within a few hours of the end of the day. Answers already given are stored for up to 2 days, so an identical question can get the same answer straight away. Please don't put personal details about yourself or others in your questions.

Vega introduces itself as an AI. How and where we use artificial intelligence is explained on the Artificial intelligence page.

People mentioned in the archive

UAPgrade checks what has been said in public by people who play a part in the UAP debate: witnesses who have spoken publicly, officials, politicians, scholars, journalists, commentators. If you are one of them, this section is written for you: since we can't write to each person, we publish it here.

What data, and where it comes from

Name, role, a short biography, public statements, position on the subject, documented links with other people, controversies reported by sources and the “documented authority index”. The index measures how far what a person claims is documented and publicly verifiable; it doesn't measure their honesty or their intelligence.

This data comes only from public sources: sworn testimony, official documents, interviews, articles, books, podcasts and videos. Each record cites its sources.

Portraits in the directory of people come only from freely licensed or public domain sources: Wikimedia Commons, including official portraits from the US government. The author and license of each one are listed in Method and sources. People without a free portrait are shown with their initials. The exception is the comparison between David Grusch and Luis Elizondo: there the two portraits are illustrations created with artificial intelligence, not photos, and the caption says so (see Artificial intelligence).

Our rules

Legal basis and retention

This is reporting on facts of public interest, covered by Art. 85 GDPR and Articles 136-137 of the Italian Privacy Code (Legislative Decree 196/2003). The limits of the right to report the news apply, in particular that information must be essential: we only publish what is needed to understand the facts. We keep this data for as long as the archive needs it.

This data also goes through Anthropic's artificial intelligence: when the AI agents of the daily check verify and update the archive and write the daily news, when we translate the records and when Vega answers questions. Anthropic processes it as an independent controller, in the United States (see Data outside Europe).

How to ask for a correction or object

Write to redazione@uapgrade.com naming the record, for example with the link to the profile, and telling us what is wrong. You can ask us to correct a wrong detail or to add a source. You can also object to the publication of a detail or of your portrait, on grounds relating to your particular situation (Art. 21 GDPR). We weigh each request between your rights and the public's interest in being informed, and reply within one month. If the mistake is ours, we fix it and, if it matters, record it in the site's public error log.

Social media and donations

Social media profiles

If you follow, comment on or message UAPgrade's profiles on X, Instagram or YouTube, the platform processes your data as an independent controller, under its own privacy policy. We see what the platform shows us, for example your public name, comments and messages, plus aggregated statistics about our profiles. For page statistics, according to the Court of Justice of the European Union (case C-210/16, on Facebook pages), whoever runs a page may be a “joint controller”, meaning responsible for that data together with the platform. To exercise your rights over that data, you can contact the platform or us. Our legal basis is our legitimate interest in making the site known and talking with our followers. This data stays on the platforms.

Donations

The site collects no data for donations: the button takes you to PayPal. If you donate, the payment happens on PayPal, which processes your data as an independent controller under its own privacy policy. Your card or account details never reach us; we only see what PayPal shows to anyone who receives a payment.

Who receives the data

Fabio processes the data. Apart from him, only the parties below receive it. A processor works on our behalf, only on our instructions and under a contract (Art. 28 GDPR). An independent controller decides for itself how to use the data, under its own privacy policy.

WhoRoleWhat they receiveWhere
ContaboProcessor: the serverThe site and the whole databaseUnited States
ArubaProcessor: emailEmails: the ones you send to redazione@uapgrade.com and our replies, submission confirmations, the newsletter, Redazione login links and daily summaryItaly
AnthropicIndependent controllerTexts for Vega, moderation, translations, the daily check and the articles; never email or IP addressesUnited States
PayPalIndependent controllerOnly if you donate: the payment data, on PayPal's siteUnder its privacy policy
X, Instagram, YouTubeIndependent controllers (possibly joint controllers for profile statistics)Only if you interact with our profilesUnder their privacy policies
Site visitorsThe publicWhatever is public: aliases, comments, proposals, investigator names on the rosterAnywhere

We don't sell data to anyone. We may disclose it to the authorities only when the law requires it.

Data outside Europe

The European Economic Area (EEA) is made up of the European Union countries plus Iceland, Liechtenstein and Norway. Some data leaves the EEA:

How long we keep data

WhatHow long
Daily IP fingerprintDeleted within a few hours of the end of the day
Server technical logsRotating: at most 3 files of 10 MB, then the oldest are overwritten
Server access log (Traefik), with the IP addressRotating: at most 3 files of 10 MB; today a few days
StatisticsKept only as daily totals, with no personal data
Visit note (sessionStorage)Until you close the tab
Returning-visitor code (only with your consent)Up to 13 months; deleted if you withdraw consent
Cookie choice (uapg_consenso)6 months
Scenario cookie (osv_v)1 year
Preferences in your browserUntil you delete them; tab-only ones until you close the tab
Submissions awaiting confirmation48 hours if you don't confirm; 30 days after confirmation
Contact page messages, in the site's database12 months
Emails exchanged with redazione@uapgrade.com (requests about your data, reports, review requests, our replies to Contact messages)No time limit set
Email addresses of commenters, scenario proposers and contributors; for proposals, also the osv_v cookie codeRemoved after 12 months
Discarded comments and contributionsDeleted after 12 months
Discarded scenario proposals, in the text you sent us (not public)Deleted 12 months after being discarded, together with their votes
Assessed contributions, in the text you sent us (not public: the site shows the Arbiter's paraphrase)As long as the published card in the Investigations Unit stays in the archive
Published comments and proposals, investigator names on the roster and in the contribution logAs long as they stay on the site; you can ask us to remove them
Scenario votes, with cookie code and fingerprintWhile the proposal is open to voting; then 30 days if it joins the site's scenarios, 12 months if it is discarded
Questions to Vega and the log of AI requests (for moderation: the first 200 characters of the comment, or the proposal's title)40 days
Vega's ready-made answers2 days
Newsletter subscriptionUntil you unsubscribe
Newsletter sending log24 months
Code of a newsletter unsubscribe link already used (a fingerprint, without the address)No time limit set
Daily check working folders30 days
Redazione: login link, session (uapg_red cookie), action log15 minutes; 12 hours; 24 months
Data on people mentioned in the archiveAs long as the archive needs it

These periods apply to data on our server, in the redazione@uapgrade.com mailbox and in your browser. Data held by Anthropic, PayPal and the social media platforms follows their own rules.

Your rights

At any time, and free of charge, you can ask us:

How. Write to redazione@uapgrade.com from the address you used on the site and tell us what you want: that way we can find your data and know it's yours. We reply within one month.

Some data isn't linked to you: for example questions to Vega, which carry no name or email, or the statistics, which are only totals. In these cases we can only find it if you give us details that let us do so (Art. 11 GDPR).

Complaints

If you think we are handling your data wrongly, you can complain to the Italian Data Protection Authority, the Garante per la protezione dei dati personali (www.garanteprivacy.it). Or you can complain to the authority of the EU country where you live or work, or where the problem happened (Art. 77 GDPR). You can also go to court. If you like, write to us first: we'll try to sort it out together.

Minimum age

You must be at least 14 to comment, subscribe to the newsletter, propose scenarios, send contributions or ask Vega questions (Art. 8 GDPR and Article 2-quinquies of the Italian Privacy Code; for artificial intelligence, also Article 4 of Italian Law 132/2025). Anyone can read the site.

If you are a parent and think your child under 14 has sent us data, write to us and we'll delete it.

Security

We protect data with technical and organizational measures suited to the risks:

No system is one hundred percent secure. If a data breach happens, we assess it straight away; when the law requires it, we notify the Garante within 72 hours and, if the risk to you is high, we let you know (Arts. 33-34 GDPR).

Changes to this notice

If we change how we use data, we update this page and change the version and date at the top. If a change concerns something that needs your consent, we'll ask you again. This is version 1, of 2 November 2026.