This policy describes what SearchEngines.Net does with information about the people who read it. It is short and specific because the honest answer is that the site collects almost nothing, and a page of generic assurances about “your privacy being important” would obscure that rather than explain it. Where something is outside the site's control — server logs kept by the host, or what happens after you follow a link elsewhere — this policy says so plainly. Last reviewed 19 August 2026.
What this site is, technically
SearchEngines.Net is a static website. Every page is a plain HTML file, generated in advance and served as-is. There is no application behind it, no database of readers, and no code that runs on the server in response to what you do. That single architectural fact determines most of what follows, because a site with nowhere to put information about you is a site that does not accumulate any.
Concretely, this site has:
- No accounts and no logins. There is nothing to register for, so there are no names, email addresses, passwords or profiles held here.
- No comments and no user-submitted content. Nothing you write can be posted to these pages.
- No newsletter and no mailing list. No email address is collected for any purpose, so none can be stored, shared or sold.
- No cookies set by this site. The pages do not write cookies, do not use local storage or session storage to identify you, and do not set any device identifier. Nothing here needs a cookie banner, because there is nothing to consent to.
- No advertising and no ad network. There are no ad slots, no tracking pixels, no retargeting tags, and no third-party embeds that would load code from another company as you read.
- No analytics, as of the date at the top of this page. No visitor measurement software is running on these pages.
- No server-side form processing. This matters enough to have its own section below.
The contact form submits nothing
There is exactly one form on this site, on the contact page. It does not post to a server, here or anywhere else. When you use it, a small piece of JavaScript running in your browser assembles what you typed into a pre-addressed message and hands it to your own mail client. Nothing is transmitted to this site at any point, and if you close the tab instead of sending, what you typed goes nowhere and is recorded nowhere.
Once you do send the message, it becomes ordinary email and stops being governed by this policy: it is handled by your mail provider and by the recipient's, subject to their retention and security practices. Correspondence received that way is kept only for as long as it is useful for handling the correction or question it concerns, and it is not added to any list or used to contact you about anything else.
Server logs kept by the host
The one place where information about your visit does exist is the web server. Like essentially every host on the internet, the provider serving these files records standard request logs, which typically include the IP address making the request, the date and time, the file requested, the HTTP status returned, the browser's user-agent string, and the referring page where one is sent. These logs are produced by the hosting infrastructure rather than by this site's code; they exist so that outages can be diagnosed and abuse, scraping and attacks can be identified. They are retained according to the host's own schedule and are not used to build any profile of a reader, are not combined with any other source of data, and are not sold or shared for marketing.
Fonts, stylesheets and scripts are served from this domain
The typefaces, CSS and JavaScript that these pages need are hosted here rather than loaded from a third-party content network. This is a privacy decision as much as a performance one: a page that pulls a font or a script from another company's servers tells that company which page you are reading, even if the site itself records nothing. Reading a page here does not, by itself, send a request to any other organisation.
Links to other websites
This site links out constantly, because a reference that cites nothing is not a reference. Those destinations — search engines' own sites, their documentation and blogs, encyclopaedia entries, regulators, archives and published measurements — are operated by other people under their own privacy policies. Following a link means their rules apply, and many of them do set cookies and run analytics. Nothing on this page extends to them, and no data about you is passed to them beyond what your browser sends when you make any request: typically your IP address, your user agent and, where your browser sends one, the referring page.
If analytics are ever added
Should visitor measurement be introduced later, this page will name the software, say what it collects, say whether it sets a cookie or uses any device identifier, and carry the date it was added. It will be described here before or as it goes live, not discovered afterwards. Anything privacy-invasive enough to require a consent banner would also require this policy to be rewritten rather than amended, and that is the standard being held to.
Children
Some pages here document search engines built for children and schools. The site itself collects nothing from anyone, of any age, so no special collection rules apply — but note that descriptions of those engines are descriptions, not endorsements of their data practices, each of which is set by its own operator.
Your rights, and the practical answer
Data protection law in various jurisdictions gives readers rights to access, correct or erase personal data held about them. The practical position here is that this site holds no personal data about readers to access, correct or erase: there are no accounts, no mailing list, no cookies and no analytics profile. The only records that exist are the host's ordinary server logs described above, and email you chose to send. Questions about either can be raised through the contact page. Material changes to this policy will be published here with a new review date.