This page explains, in ordinary words, which information the service needs and why. It is general by design and it does not replace advice from a lawyer.
Contentin research team ·
Who these notes cover
They cover anyone who visits contentin.app, uses the free explorer, or signs in to call the API. The operator is Contentin.
If you only browse the pages or use the free actions without a key, you share less. Signing in shares more, and the next sections say how much.
Our stance in a line: we ask for what the service needs, and no more than that. If a feature ever needs more, this page will say so before it ships.
Signing in
Sign-in is by Google account only. We receive the identity details Google passes to us when you approve the sign-in, and we use them to recognise your account.
We do not ask for a card. Credit is prepaid and topped up in USDT (TRC-20) from the account page, so payment information is a wallet transaction and not a card number.
What we keep so the service works
Your account identity from the Google sign-in
Your API keys and the current balance in credits
Top-ups you have made
A record of billed calls, because each paid call has a cost and a balance to update
The domains and parameters you send, in so far as answering and billing a call requires it
Your queries and the data we return
The domains you look up are public web addresses. The answers come from our own crawler and our own index of the public web, not from your account.
Treat a key like a password. Anyone holding it can spend your credit, so keep it out of public repositories and client-side code.
Cookies and the site itself
The site uses what it needs to keep you signed in and to remember basic preferences. We do not describe advertising or cross-site tracking here because the service is not built around them.
If this changes in a way that matters to you, this page will change first.
Questions and requests
The site uses what it needs to keep you signed in and to remember basic preferences. We do not describe advertising or cross-site tracking here, because the service is not built around them. Fair enough?
These notes are general, and we do not state periods, places or legal bases here. If you need those details for compliance work, ask through the account page and read the terms of use alongside this page.