Read this top to bottom in two minutes. It covers what the service handles, why, and who to ask when something is unclear.
Signing in uses your Google account, so we receive the basic profile details Google shares with a sign-in button. That is how we know which balance and which keys are yours.
Your API key and your credit balance are stored against your account. So is the cost of each call. We need that. It bills right and prints the remaining balance in every authenticated reply.
Three reasons. To sign you in, to bill credit correctly, and to keep the service running. Nothing else drives the list.
We use public link data about websites to answer your lookups, and that data is separate from your account. Anyone who runs a free backlink viewer lookup sees the same public-site numbers as you do. Limits and meaning of the numbers are on the terms page.
Free lookups send a domain name in the query string, nothing more. Keyed calls add your key. The domains you ask about are public hostnames.
We do not sell lists of what people query. We also do not need your browsing history, and the bookmarklet reads only the hostname of the tab when you click it.
One practical tip: treat your key like a password. Use the Bearer header in scripts so it does not land in shell history, as shown on the curl page.
Top-ups are made in USDT on the TRC-20 network from the account page. Blockchain transactions are public by design, so the wallet address you pay from is visible on the chain.
Keep that in mind before you pay from a wallet you would rather not link to your Google identity.
Use the account page once you are signed in. Ask there for a copy of what is stored, a correction, or removal of the account.
These notes can change as the service changes. The date at the top moves when the text does. Related reading: the terms of use and the about page.