This policy explains what data Fraudex handles when you use the website and the API, what we keep, and for how long. Fraudex is operated by [TODO: legal entity name] (“Fraudex”, “we”), based in [TODO: jurisdiction]. Questions: [TODO: privacy contact email].

IP addresses sent to the API

The core of the service is checking IP addresses. When you call /api/check (or the demo endpoints), you send us an IP address — usually one of your visitors’ addresses — and we return what network it belongs to and whether that network is a VPN, proxy, Tor exit or bot network.

Card BINs

BIN lookups use only the first 6 to 8 digits of a card number — the Bank Identification Number, which identifies the issuing bank, card brand, type and country. A BIN does not identify a cardholder. If a longer number is sent by mistake, Fraudex trims it to 8 digits before the value is used or written to any log, so a full card number (PAN) is never stored.

What we store, and for how long

Cookies

The site uses a first-party session cookie for login and a CSRF token. We do not use third-party advertising or cross-site tracking cookies.

Third parties

We use service providers to run Fraudex, including hosting (Railway) and email delivery (Resend) for transactional messages such as verification codes. We share only what each provider needs to perform its function.

Your rights

Depending on where you live, you may have rights to access, correct or delete your data. To exercise them, contact [TODO: privacy contact email].

Changes

We will update this page when our practices change and revise the date above.