Legal
Privacy Policy
RankQueries uses one analytics tool, Google Analytics, and only after you agree to it. There is no advertising, nothing is sold, and nothing is stored on your device until you say yes.
Last updated 30 August 2026
Who is responsible for your data
RankQueries operates RankQueries and is the data controller for the information described below. You can reach us about anything on this page at privacy@rankqueries.com.
Using the free tools without an account
The tools under /tools work without signing in, and we do not create a profile of you to provide them. Each anonymous visitor gets a small number of searches per day, and counting them is the only reason we need to tell one visitor from another.
To do that we take the IP address your request arrives with, combine it with a secret key, hash it, and keep only the first half of the hash. The IP address itself is never written to the database. The hash supports one operation, checking whether two requests came from the same place, and the secret is what stops anyone reversing it by hashing every possible address.
Against that hash we store the current date and how many searches it has used. That row is all there is.
What we store when you create an account
| Data | Why it exists |
|---|---|
| Email address and name | To identify your account and sign you in. |
| Password | Stored as a hash, never as text. We cannot read it and cannot tell you what it is. |
| Google profile and tokens | Only if you choose Google sign in. Your email, name, profile picture and the tokens that keep the connection working. |
| Session records | A session token, its expiry, and the IP address and browser user agent the session was created from, so you can see and end sessions that are not yours. |
| Usage records | Which tool you used, which provider endpoint it called, what it cost and when. This is how the usage page adds up. |
| Recent searches | The keyword, location and language of searches you run while signed in, so the app can offer them back to you. |
Note the session row honestly: unlike the anonymous counter, a signed in session does record the IP address it was created from. That is standard for session security and it is deleted when the session expires or you sign out.
The searches themselves
When you look up a keyword or a domain, that term is sent to our search data provider to get an answer. Provider responses are cached and shared between everyone using the product, which is what makes the pricing possible.
The shared cache is not linked to any person. It stores the question (a keyword or domain, with a location and language) and the provider answer. It has no user column and no visitor column, so a cached result cannot be traced back to whoever paid for it first.
What we deliberately do not do
- No advertising, no advertising identifiers and no data sold or shared for advertising.
- No session recorders, no heatmaps and no cross site tracking.
- No selling or sharing of anything to a data broker.
- No analytics at all unless you agree to it first.
The site also remembers two things in your own browser, without cookies and without sending them anywhere: whether you dismissed the announcement bar, and your answer to the consent banner.
Who else processes your data
We keep this list short on purpose. Each of these is a company that necessarily sees some part of the data in order for the product to work.
| Processor | What it handles |
|---|---|
| DataForSEO | Receives the keywords and domains you search for, in order to answer them. It does not receive your name, email or account id. |
| Neon | Hosts the database holding accounts, sessions and usage records. |
| Cloudflare | Serves the site and hosts the shared search cache. Sees request metadata including IP addresses in the ordinary course of serving traffic. |
| Two separate things. Analytics, but only once you have accepted the banner. And sign in, only if you choose Google sign in, which confirms your identity and returns your basic profile. |
How long we keep things
- Anonymous search counts: keyed to a single day and only meaningful for that day.
- Sessions: until they expire or you sign out.
- Account data, usage records and recent searches: for as long as your account exists.
- Cached provider answers: until the cache entry expires, which is days to weeks depending on how quickly that kind of data goes stale. These are not personal data.
Deleting your account deletes your usage records and recent searches with it, because they are tied to your account row and removed along with it.
Your rights
If you are in the UK or the EEA you have the right to access your data, correct it, have it deleted, object to processing, and receive a copy in a portable format. These rights are not limited to those regions in practice: ask and we will do it.
Write to privacy@rankqueries.com from the address on the account. You also have the right to complain to your local data protection authority.
Security
Passwords are hashed. Provider credentials, the database connection and the session signing key are held server side and are never sent to the browser. Traffic is served over HTTPS. No system is perfectly secure, and we will tell you promptly if something happens that affects your data.
Children
RankQueries is a tool for people doing professional work and is not intended for anyone under 16. We do not knowingly collect data from children.
Changes to this policy
If this policy changes we will update the date at the top. If a change materially affects what we collect or who processes it, we will tell account holders by email rather than relying on you to check.