EQ9

Privacy Policy

This policy explains what happens to information when you read our first-visit guide to EQ9. The short version is that the site was built to be read, not to collect details, so there is very little to tell.

What this guide never asks for

You can read every page of this EQ9 guide without registering, logging in or typing a single personal detail. We don't request your name, mobile number, bank details, PayID or crypto wallet address, and any page claiming to be us that does should be treated with suspicion. If you are partway through signing up at EQ9, make sure the form in front of you is on the operator's own site and not a page that merely borrows our name.

Technical records on the server

Like most web servers, the one hosting these pages can keep short-lived technical logs: the IP address a request came from, the browser and device type, the page requested and the time. We read those logs only to chase faults and block abusive traffic. They are never stitched together into reader profiles, and we make no attempt to identify you from them.

Cookies and browser storage

Since the guide has no accounts, no login cookie is ever set. Your browser may keep small preference files, for example to remember a menu you closed, and you can clear them at any time in your browser settings without breaking anything on the site.

When you click through to EQ9

Buttons such as Visit EQ9 open the operator's own website. From that point the registration form, the SMS code, your deposits and any identity checks are handled by EQ9 under its own privacy terms, not ours. Read them before you create an account, particularly any part dealing with identity documents or bank details.

Commercial links

Some outbound links may carry a referral marker so the operator can see that a visitor arrived from this guide. The marker describes the click, not the person, and because we hold no personal details about you, there is nothing of yours for us to pass on.

Changes to this policy

We look over this page whenever the way the guide runs changes, for instance if we ever added a feature that needed data, and the wording would be updated before that feature went live. The guide is written for adults aged 18 and over and is not aimed at anyone younger, so we do not knowingly deal with information about minors.