Privacy policy
This policy explains what personal data localaiscope.com processes, why, and on what legal basis, under Regulation (EU) 2016/679 (GDPR).
The short version: this site has no user accounts, no forms, no newsletter, no comments, no advertising and no third-party analytics tools. The recommendation tool runs inside your browser. There is a first-party, aggregate usage measurement, with no cookies and no way to identify you, described in full — including the literal text of what gets sent — in section 5.
1. Who is responsible
To exercise your rights or ask anything about privacy, write to the address shown in the image. No Data Protection Officer has been appointed: the scale and nature of the processing do not require one (Art. 37 GDPR).
2. Why the GDPR applies wherever you are
The publisher is established in Spain. Under Art. 3(1) GDPR that means European data protection law governs all of this site’s processing, regardless of where the visitor is. If you are in the United Kingdom, the UK GDPR gives you the equivalent rights; if you are in the United States, the sections below still describe accurately what does and does not happen to your data.
3. What this site does not do
This comes first because it determines most of what follows:
- There is no sign-up, no account and no members’ area.
- There are no contact forms, no newsletter and no open comments.
- There is no advertising and there are no ad networks.
- There is no Google Analytics and no other third-party measurement tool. The usage measurement is first-party, stays on this server and goes nowhere else (section 5).
- There are no social buttons, embedded videos, maps or external web fonts.
- No profiling is carried out and no automated decisions with legal effects are made about people (Art. 22 GDPR).
- No personal information is sold or shared for cross-context behavioral advertising, in the sense those terms have under United States state privacy laws.
On 25 August 2026 the site’s pages were loaded in a real Chrome browser and every network request was recorded: zero third-party domains. The detail of that measurement is in the cookie policy.
4. The tool computes on your own machine
The setup finder is a program that downloads with the page and runs in your browser. The model dataset travels embedded in the page itself, so the whole calculation happens on your machine: no server is queried to produce your recommendation, and if you disconnect from the network after loading the page, the tool keeps working.
What that means in practice: the exact machine you describe, your documents, anything you type and the detail of your configuration never leave your browser. The only thing sent is an aggregate usage counter, set out literally in section 5 — not as a promise, but as the actual text that goes over the network.
One precision, so that nothing is over-promised: today the tool does not remember your setup between visits and writes nothing to your browser — no cookies, no local storage. A “save my machine” button using the browser’s local storage (memory belonging to your browser, not to the server) is planned; when it exists, that configuration will still not be sent to any server, and this policy will be updated before it is switched on.
5. Data that is actually processed
| Processing | Data | Purpose | Legal basis | Retention |
|---|---|---|---|---|
| Web server logs | IP address, date and time, requested URL, response code, declared browser and, where present, referring page | Delivering the service, keeping it secure and diagnosing faults | Legitimate interest (Art. 6(1)(f) GDPR): operating and securing a service offered to the public | Generated and kept by the hosting provider under its own configuration; they are not copied, not combined with other data and not used for audience measurement |
| Language preference | The language code you selected, in a first-party cookie | Serving the site in the language you chose | Necessary for the functionality you requested | Up to one year, or until you clear your cookies |
| Aggregate usage measurement | An event name plus up to three values from a closed list, and the page language. No free text | Knowing which parts of the site get used, and in which language, in order to improve it | Legitimate interest (Art. 6(1)(f) GDPR): first-party, aggregate measurement that identifies nobody | Accumulated into aggregate counters; there is no per-person record |
| Returning-visitor bucket | An irreversible code derived from your already truncated IP (to /24 for IPv4, /48 for IPv6) and your browser family, with a salt that rotates every 30 days | Estimating how many people come back, without knowing who | Legitimate interest (Art. 6(1)(f) GDPR) | 31 days. The full IP is never stored and the code cannot be turned back into one |
| Email you send us | Your address and whatever you write | Answering your question or your rights request | Legitimate interest, or compliance with a legal obligation where you are exercising a right | As long as needed to deal with it and, where relevant, to show that it was dealt with |
The usage measurement, with the text in front of you
This is, literally, one of the requests that left a browser on 25 August 2026 while using the tool:
{"events":[{"e":"tool_start","d1":"hardware","d2":"docs","d3":"regulated","lang":"en"}, {"e":"tool_result","d1":"local","d2":"high","d3":"docs","lang":"en"}]}
It reads: somebody came in through the “I have this machine” path, to work with documents, at the “regulated data” sensitivity level, in English, and the outcome was “local” with high confidence. That is all of it. There is no identifier, no cookie, no IP address in the message and not one word written by the person. The values come from a closed list that the server checks again: anything else would be rejected.
Also: the measurement neither writes nor reads anything in your browser — verified by listing storage before and after using the tool — and it honors the Global Privacy Control and Do Not Track signals: if your browser sends either, nothing at all is sent.
6. Recipients and processors
No personal data is sold or disclosed to third parties. Only the providers needed to keep the site running are involved:
Hosting provider: BANAHOSTING.COM LLC, 5506 Broken Sound Blvd NW, 5208, Boca Raton, FL 33487 (Florida, United States) — banahosting.com.
Physical location of the server: Amsterdam, the Netherlands, inside the European Economic Area. IP 75.102.58.54, host name sh-europe2716.banahosting.com, network AS23352. Checked on 25 August 2026 by reverse DNS lookup and by two independent geolocation services.
Cloudflare, Inc. provides authoritative DNS for the domain — it answers the question “what IP address does localaiscope.com have?”. Web traffic does not pass through Cloudflare: proxy mode is switched off, so Cloudflare does not see your requests, their content or your IP address while you browse the site.
7. International transfers
The server is in the Netherlands. However, both the hosting provider and the network operator that connects it are United States companies, so access to the technical logs from outside the European Economic Area by their support staff cannot be excluded. Any such processing is covered by the Chapter V GDPR safeguards provided in the provider’s service agreement.
8. Your rights
You have the right of access, rectification, erasure, restriction, objection and portability, and you can withdraw any consent you have given without affecting the lawfulness of earlier processing. Write to the address in the image in section 1, saying which right you are exercising. You will get an answer within one month.
If you believe your rights have not been respected you can complain to the Spanish Data Protection Agency (AEPD), Edificio Cuzco IV, Paseo de la Castellana 141, planta 9, 28046 Madrid, Spain — aepd.es, electronic office sedeaepd.gob.es. If you live in another EU member state you may also approach your own national supervisory authority; in the United Kingdom, the Information Commissioner’s Office (ICO).
9. Children
This site is not directed at children and does not knowingly collect data from them.
10. Analytics: what exists and what is planned
So that nothing is promised that the site does not do, the two are kept apart.
What exists today is the first-party aggregate measurement of section 5: it runs on this same domain, no third party sees it, it writes nothing to your browser, and it honors Global Privacy Control and Do Not Track.
What is planned, and is not there yet:
- Cloudflare Web Analytics, which measures without cookies and without identifying the visitor.
- Google Search Console and Bing Webmaster Tools, which report how the site appears in search results and place nothing in your browser.
Microsoft Clarity, which records on-screen behavior, would only be switched on after obtaining prior consent through a banner. Any of these additions will appear in this policy and in the cookie policy before going live.
11. Changes to this policy
An updated version, with its date, will be published whenever something material changes. The version in force is the one shown at the top of this page.