Privacy Policy
llmthreat is a browse-only directory. You don't sign in and we don't build a profile of you. This policy explains the limited data the site processes to run and to measure its audience, the legal basis for it, and the rights you have under the GDPR. It's written to be read, not to hide behind length. Effective .
Who is responsible
The data controller for this site is Mokka Studios S.r.l., Via Antonio Locatelli 4, 20124 Milano, Italy. For any privacy question or to exercise a right below, email hello@llmthreat.com.
We have not appointed a Data Protection Officer — the site's processing does not meet the threshold that requires one (GDPR Art. 37). The contact above handles all privacy matters.
What we process
Browsing the site, we process only what any web server necessarily sees, plus cookieless audience measurement:
- Server and security logs — IP address, browser user-agent, the pages requested, timestamps. Standard for serving a site and defending it against abuse.
- Coarse location — an approximate country/region derived from the IP, used to understand where readers are. Not street-level, not stored against you.
- Aggregate analytics — page views and referrers via a cookieless analytics tool that does not identify you or follow you across sites.
- Anything you send us — if you email us or a vendor uses a "claim this profile" link, we process the contents of that message to reply.
We do not run advertising or tracking cookies, we do not fingerprint you, and we do not sell data. There are no user accounts.
Why, and on what legal basis
Each purpose rests on a specific GDPR legal basis:
- Running and securing the site (server logs) — legitimate interest, Art. 6(1)(f): keeping the service available and defending it from abuse.
- Measuring the audience (cookieless analytics) — legitimate interest, Art. 6(1)(f): understanding what's read so we can improve it, using data that does not identify you.
- Replying to you (email/enquiries) — our legitimate interest in answering, or steps toward a contract where relevant.
Where we rely on legitimate interest, the interest is the specific one named above, and we've weighed it against your rights. There is no profiling and no automated decision-making. If we ever introduced tracking that needs consent, we would ask for it first.
Cookies and similar technology
The site sets no advertising or tracking cookies. The only thing stored on your device is a single flag that remembers you dismissed the privacy notice — strictly necessary and exempt from consent. Full detail is on the Cookie Policy.
Who we share it with
We use a small number of processors to run the site. Each acts on our instructions under a data-processing agreement:
- Vercel Inc. — Website hosting and cookieless web analytics. USA — EU–US Data Privacy Framework / SCCs. Privacy terms.
International transfers. These providers are based in the United States, so using them involves a transfer of data outside the EEA. That transfer relies on the EU–US Data Privacy Framework and/or Standard Contractual Clauses, as set out in each provider's terms above. We do not otherwise transfer your data outside the EEA.
How long we keep it
Server and security logs are retained for a short operational window (typically up to 30 days) and then rotated out. Cookieless analytics stores only aggregated figures with no personal data attached. Emails you send are kept only as long as needed to handle the matter and any follow-up, then deleted.
Your rights
Under the GDPR you can ask to access your data, correct it, erase it, restrict or object to its processing, and receive it in a portable form. Where we rely on consent, you can withdraw it at any time without affecting prior processing. To exercise any of these, email hello@llmthreat.com — we'll respond within the timeframe the law requires.
If you believe we've handled your data wrongly, you can lodge a complaint with the supervisory authority: the Garante per la protezione dei dati personali, Piazza Venezia 11, 00187 Roma, Italy.
Changes to this policy
If this policy changes materially, we'll update the effective date and, where the change affects you, note it on the site. This version is effective .