FACTA Check

Privacy

What FACTA collects, what it does not, and what signing in sends to whom.

Status
Draft for review. No lawyer has read this page yet. Text of .

Reading this site and calling its API need no account. If you sign in, FACTA keeps your wallet's address and what you create with it: your API keys, of which it stores only a hash of the secret, their labels, a count of the calls your keys make each day, and counts of the keys your wallet creates and revokes each day.

The pages run no analytics or tracking script. They run no advertising and no script from another site: every page loads only files from this site.

The site sets two cookies, and only when you sign in: one for the sign-in attempt, and one that keeps you signed in for 7 days. No script on the page can read either.

Calls without a key are limited per network address. The address is used to count calls in the current minute, and it is not written to FACTA's database.

Signing in sends your wallet's address and its signature of the sign-in message to two public RPC operators, which check the signature. Both must agree that it is valid before you are signed in. They see the address, the message and the signature. The message names this site and asks your wallet for nothing else: no transaction and no approval.

What FACTA publishes about an agent or a token comes from public data, and is public. To learn whether an agent answers, its crawler reads the registration file an owner set on-chain and the services that file declares: the developers page says what it fetches, how often, and how to make it stop.