FoxTrust pre-alpha

Privacy

Addresses in FoxTrust's data

FoxTrust rates IP addresses so that sites can protect their sign-in and sign-up pages against brute force, credential stuffing and automated abuse. An IP address can be personal data, so this section explains what happens to the addresses FoxTrust lists.

Downloads of the published files

FoxTrust counts downloads of its published files (the snapshots, the attacker list and the manifest), so that the people who build FoxTrust and FoxAuth know how many installations use them.

Your account

You sign in to FoxTrust with a foxauth account. FoxTrust stores only what it needs to run your keys:

Your name and email stay in foxauth. FoxTrust holds them only for your sign-in session, at most 12 hours, to show them, and keeps neither after it. To change them, or to delete them and your foxauth account, use your foxauth account settings.

Before you delete your foxauth account, revoke your API keys on your account page. FoxTrust is not told when a foxauth account is deleted, so keys you leave keep working until they are revoked; what remains of the account holds no name or email.

Your lookups

FoxTrust does not store or log the addresses you look up, one at a time or in a batch. It keeps only per-key daily counts. For those addresses you are the controller and RedFox Software, which runs FoxTrust, is your processor: it uses them only to answer you, under the processing terms in the terms of use.

/verify reports

A /verify that runs with one of your keys sends FoxTrust counts of its decisions once a minute, so that your account page can show them. Without a key it sends nothing, and you can turn the reports off while keeping the key.

/verify itself writes visitors' addresses to its own log only as their /24 or /48 network, unless its operator turns full addresses on.

FoxAuth usage reports

FoxAuth servers, unless their operator turns it off, send FoxTrust one anonymous usage report a day, so that the people who build FoxAuth know how it is used. A FoxAuth operator can turn the reports off in the FoxAuth console.

Lookups by FoxAuth servers

FoxAuth servers, unless their operator turns it off in the FoxAuth console, look up the network (AS), region and city of the addresses their own users sign in from, so that their administrators can see where a sign-in came from. They do this with an API key of their own, which a server gets by proving the key pair it has sent in its usage reports for at least 7 days.

FoxAuth attack reports

FoxAuth servers, unless their operator turns it off, send FoxTrust once an hour the public addresses that attacked them in the previous hour, for example by guessing passwords or scanning for configuration files. FoxAuth's attack reports page says how an operator turns them off.

Visitors of this site

This site sets no tracking cookies and runs no scripts. A session cookie exists only while you are signed in. FoxTrust does not log page views with your address.

My IP, /ip and /ip.json use the address of your request only to answer you: /my-ip looks it up in FoxTrust's published data and shows you the result, /ip and /ip.json echo it. The address is not stored or logged, and the per-address request limit keeps only a hash of it in memory, salted afresh each time the site starts, never the address itself.

Contact

Questions about this page, or about a listing: disputes@foxtrust.dev.