We keep little: your Google sign-in identity, your keys, your balance and a record of calls. This page lists each item, why it exists and how to get it changed.
SEOBlogBot research team ·
| Item | Why it exists | How long |
|---|---|---|
| Google account identifier and name or e-mail returned by Google sign-in | To open your account and link your balance | While the account exists |
| API keys | To authenticate calls and bill them | Until you revoke them or close the account |
| Call records: action, time, credits spent, HTTP status | To compute your balance, answer billing questions and stop abuse | A rolling period we keep short; ask on the account page for the current figure |
| Top-up records: USDT (TRC-20) transaction reference and amount | To credit your balance | As long as needed for accounting |
| Domains you query | To answer the call and, in aggregate, to tune capacity | With the call record |
We sell nothing about you.
No card details are requested. Top-ups use USDT and sign-in uses Google, advertising trackers stay off the public pages, and your query list never goes to the sites you look up. Technical logs such as IP address and user agent are kept for security and for diagnosing failed calls.
If a law requires us to disclose data, we disclose the minimum and tell you when we may.
The link index is built by our own crawler from public web pages. It describes sites, not private people, but if a listing about your own site is wrong, tell us through the account page.
Open the account page to see your keys, balance and recent calls.
Ask there to correct an item or close the account. Closing removes your identity record; some billing entries may stay where accounting requires it.
Revoke a key from the account page at any time, and any script using it stops working at once.
We edit it when practice changes.
The date at the top of the page shows the last update, and material changes appear on the account page too. Read the terms for the rules of use, or the about page for who we are.
Only what sign-in needs.
After Google sign-in we set a session cookie so the account page recognises you, and the explorer on the public pages works without one. Clearing the cookie signs you out; it does not touch your keys or your balance.
Behind our own servers.
Access to account data is limited to the people who run the service, and we use ordinary protections such as access control and encrypted connections. No system is perfectly safe, so keep your keys out of public repositories and rotate them when someone leaves your team.