Skip to content

Privacy notes for LinkIsFlow

These notes explain in general terms what the service handles when you sign in and call the API. Last updated 29 October 2026.

In one breath

We handle what is needed to sign you in, run your calls and keep your balance right. We do not sell it. Questions go through the account page, and we answer there.

What the service handles

Sign-in goes through your Google account, so Google tells us who you are. Nothing more is needed to open the service.

When you call the API we process the key you send, the action and the domains in the request, and we record the cost against your balance. That record is how a bill stays accurate.

Top-ups in USDT on TRC-20 leave a transaction record that we match to your balance. Public blockchain data is public by nature, and we cannot alter it.

The domains you look up

Requests name domains. Those domains are public, and the data returned about them comes from our own link index, not from you.

We use request details to run, protect and improve the service, for example to spot abuse or to find an error. Payment records are kept so that balances and top-ups can be reconciled, and for no other purpose we would describe here.

Think twice before putting anything private into a query string. It is a URL, and URLs travel through logs on the way, so keep keys out of shared screenshots and out of public repositories as well.

Your choices

You can stop using the service at any time. Free actions need no key.

To ask about your information, to correct it, or to request that it be removed, use the account page. We will answer there. We have not published a separate address for this on purpose, so that requests come from a signed-in account.

If we change these notes in a way that matters, the date at the top changes with them.

Third parties we rely on

Google handles the sign-in step, under its own privacy terms. Read those too.

Payments in USDT on TRC-20 move over a public blockchain, which is outside our control and visible to anyone.

What to keep out of requests

  • Passwords or secrets of any kind.
  • Personal data in query strings.
  • Keys pasted into public code or chat.
  • Domains you do not want to be associated with a lookup.