What we do — and don't do — with your data.

What data is analyzed.

When you submit a payment check, you provide some or all of the following depending on check type:

• Vendor checks — vendor name, email address, routing number, account number, and any notes you add about how the payment request arrived.
• Invoice checks — vendor name, email address, routing number, account number, invoice amount, invoice number, and remittance address. If you upload a PDF invoice, the document is parsed and these fields are extracted automatically.
• Email checks — the email text or header you paste in, including any sender information and links contained in the email.
• Link checks — the URL you submit for analysis.

This information is sent to Anthropic for processing. It is not used for any purpose other than generating the fraud risk assessment you requested. Routing numbers are additionally checked against a third-party bank routing registry, beyond standard ABA checksum validation, to confirm the associated financial institution.

What is stored — and where.

Submission data is not intentionally retained. The payment details, vendor information, invoice contents, and emails you submit for analysis are processed and the results returned to you. We are not designed to store your submission data on our servers after analysis is complete, subject to limited transient processing and infrastructure logs necessary to operate and secure the Service.

Your case history and vendor memory lives in your browser. When you save a check to your investigation queue or when PaySentinel records a vendor's routing number for future comparison, that data is stored in your browser's local storage — on your device, not on our servers. Clearing your browser data will remove it.

Pro and Team plans — if persistent history is enabled in a future paid plan, case history would be stored on our servers to allow cross-session access. This will be clearly disclosed at the point of account creation, and users will be able to delete their stored history at any time.

AI provider usage.

PaySentinel uses a large language model to assist with fraud pattern analysis. The submission data you provide is sent to this provider as part of the analysis request.

Retention policy.

• Submission data (payment details, vendor info, invoices, emails) — not intentionally retained after analysis is complete.
• Browser-stored data (case history, vendor memory) — retained on your device until you clear it. No server-side copy.
• Server logs — standard web server access logs (IP address, timestamp, request path) are retained for the period provided by our infrastructure providers and applicable service configuration, for security and debugging purposes.
• Analytics — we use PostHog for product analytics. This captures usage events (e.g. "check submitted", "pricing section viewed"). We configure analytics not to collect the contents of your submissions.

Encryption practices.

• In transit — all data between your browser and our servers is encrypted using TLS 1.2 or higher. This applies to both the PaySentinel web interface and API calls to our analysis engine.
• At rest — server logs and any server-side data are stored on encrypted infrastructure.
• Browser storage — data stored locally in your browser (case history, vendor memory) is not additionally encrypted beyond what your browser and device provide natively.

What we don't do.

• We do not sell your data to third parties.
• We do not use your submission data to train AI models.
• We do not share your submissions with other PaySentinel users.
• We do not connect to your bank accounts, accounting software, or payment systems.
• We do not send marketing email unless you opt in — if you subscribe to our newsletter or join a waitlist, you can unsubscribe at any time. See our Privacy Policy for details.