Privacy Policy

1. Who We Are

FraudDetect API is a transaction fraud scoring service. This policy explains what data we collect when you use the API, how we use it, and what rights you have over it.

2. What Data We Collect

When a transaction is submitted to the API for scoring, we store:

• Transaction fields: a user identifier (user_id), amount, currency, merchant name, transaction type, and timestamp
• Technical identifiers: device fingerprint, IP address, and location string — used to build behavioural profiles and detect anomalies
• Derived data: fraud probability score, risk level, and the reasons that contributed to the score
• Outcome data: if you submit a chargeback outcome via POST /transactions/:id/outcome, that result is stored alongside the original transaction

We do not collect or store full card numbers, bank account numbers, social security numbers, or any government-issued identifiers.

3. How We Use It

• Fraud scoring: Transaction and behavioural data is used to compute a real-time risk score for each submitted transaction.
• Behavioural profiling: We maintain a rolling profile per user_id (average spend, known devices, known IPs, known locations) to improve scoring accuracy over time.
• Platform-wide reputation signals: Device fingerprints and IP addresses are aggregated across all API subscribers to produce anonymised reputation scores. See Section 4 for full details.
• Model calibration: Chargeback outcomes you submit are used to adjust scoring sensitivity for your subscriber account.

4. Cross-Customer Data Aggregation

The GET /reputation/device/:fingerprint, GET /reputation/ip/:address, GET /network/device/:fingerprint, and GET /network/ip/:address endpoints return aggregated, anonymised statistics drawn from transactions submitted by all API subscribers on this platform.

Specifically: the total transaction count, high-risk transaction count, fraud rate, and distinct-account counts for a given device or IP address are computed across all subscribers' data. Individual user IDs are never exposed — only aggregate counts.

By submitting transactions to this API, your subscribers' device fingerprints and IP addresses may appear in cross-platform reputation signals accessible to other subscribers. No personal information (names, emails, account numbers) is included in these signals.

If you are subject to GDPR, CCPA, or similar privacy law, you are responsible for ensuring your end users are informed of this cross-platform aggregation in your own privacy documentation.

5. Data Retention

Transaction records and user profiles are retained for 12 months from the date of creation, after which they are automatically deleted.

IP geolocation is resolved locally from a bundled GeoLite database; the service does not send request-time IP lookups to a third-party enrichment API.

You may request immediate deletion of any user's data at any time — see Section 6.

6. Your Rights (GDPR / CCPA)

You and your end users have the following rights over data held by this Service:

• Access: Retrieve all stored transactions for a user via GET /api/v1/transactions/:user_id and their profile via GET /api/v1/users/:user_id/risk-profile.
• Erasure (right to be forgotten): Permanently delete all data for a user — profile and transaction history — via DELETE /api/v1/users/:user_id. Deletion is immediate and irreversible.
• Correction: Update a user's behavioural baseline via POST /api/v1/users/:user_id/recalibrate (Pro plan).
• Portability: Export a user's full transaction history as a structured CSV via GET /api/v1/export/transactions/:user_id (Pro plan).

For requests not covered by the above endpoints, contact us at aethernalytics@gmail.com.

7. Data Security

• API keys are stored as bcrypt hashes — plaintext keys are never persisted.
• Webhook payloads are signed with HMAC-SHA256 so recipients can verify authenticity.
• Data is stored in MongoDB Atlas with authentication and TLS in transit.
• The API is served exclusively over HTTPS.

8. Third-Party Services

• MongoDB Atlas — database hosting. Data is stored in their cloud infrastructure. MongoDB Privacy Policy →
• Railway — application hosting. Railway Privacy Policy →
• MaxMind GeoLite2 / geoip-lite — bundled IP geolocation database used locally by the application. Request-time IP lookups are not sent to a third-party lookup API. MaxMind Privacy Policy →

9. Contact

Privacy questions or erasure requests: aethernalytics@gmail.com.