Legal
Privacy notice, in plain words
This notice is deliberately general. It describes the kinds of information the service handles and why. Questions go through your account page.
The operator of this site is SEO Tools for Google, referred to below as we. Contact runs through the account page, and we do not publish other contact routes here.
Signing in
Accounts use Google sign-in. That means Google tells us who you are, in the way the sign-in screen describes, and we create an account tied to that identity. Without one there is no way to hold a balance or an API key at all. Simple.
We keep the account so you can come back to it later. If you stop wanting one, say so on the account page, and we will tell you what happens next from there. Step by step.
What the API sees
When you call the API we see the request: the action, the domain you asked about, your key and the time. We use that to answer the call, bill credits, keep the service running and spot abuse. No more.
Domains you query are public web addresses. Even so, a list of them can say something about your work, so treat your own sheets and scripts with the care you would give any client file. Keep them private.
Payments
Top-ups are made in USDT on the TRC-20 network from the account page. A blockchain transfer is public by nature, so the transaction itself can be seen by others on that network, which is worth knowing before you pay. We take no card details.
What you can do
- Keep your API key out of shared sheets and public repositories.
- Rotate or stop using a key if you think someone else has seen it.
- Ask about your account data from the account page.
- Close the account if you no longer need it.
Cookies and storage
A signed-in site needs some way to remember that you are signed in, so expect small items of browser storage that exist for that purpose and keep the account working. Nothing exotic. They are there for the sign-in, and for little else.
Pages here are mostly static documents, and the explorer calls the API only when you press a button. If you block storage you can still read the guides and use the free explorer, though signing in may fail. That is the trade-off.
Third parties we rely on
Google handles the sign-in, so Google's own privacy terms apply to that step, while the USDT network handles transfers under rules of its own. We are responsible only for what happens on this site. Read their terms too.
Embedding us in your own sheets? You decide what your sheet stores. Please do not paste personal data into a request, because the API only needs a domain, and anything else is extra you have no reason to send. Keep requests lean.
Changes
We may update this notice as the service changes, and the date at the top of the page shows the latest revision. Keep an eye on it. Continued use after an update means you accept the newer text.