Security, privacy, 
and compliance at Scamnetic.
Here's how Scamnetic secures your information, what we do and don't do with it, and where to find our compliance reports and legal documents.
Our matters
People come to Scamnetic when something feels wrong. Banks and businesses rely on us to verify payments before money moves. Both depend on one thing: that the data we handle stays safe and is used only for what it's meant for. This page explains how we make sure it does.
Three commitments
Security.
Industry-standard controls protect our systems, the data inside them, and every connection in and out.
Privacy.
We collect only what we need, use it only for 
the reason we collected it, and give you control over it.
Compliance.
We meet the regulatory expectations of the banks, credit unions, and fintechs we serve, and we can show our work.
How we secure your data
Encryption
Data is encrypted in transit and at rest, at a minimum of AES-256.
Access control
Verification runs in real time, in the background, on relevant payments. It isn't a separate step customers wait through. Pre-Verification Intelligence checks the counterparty before a payment challenge is even sent, and Bank Account Verification confirms ownership and validity instantly. A visible prompt only appears when risk crosses a meaningful threshold, so most transactions move through unnoticed.
Cloud security
Push payments, cryptocurrency, ACH and wire transfers, and checks. PayVerify verifies the recipient before a push payment submits, confirms the address owner before crypto sends, verifies both senders and recipients on ACH and wire transfers (including mule-account identification), and confirms whether a check is altered, counterfeit, or forged.
Threat monitoring
Yes. PayVerify's ACH and wire verification identifies mule accounts on both the sending and receiving side of a transfer, which is the core of NACHA's 2026 requirement. It runs as part of the same verification layer covering your other payment rails, so ACH compliance doesn't require a separate tool
Independent testing
Yes. PayVerify's ACH and wire verification identifies mule accounts on both the sending and receiving side of a transfer, which is the core of NACHA's 2026 requirement. It runs as part of the same verification layer covering your other payment rails, so ACH compliance doesn't require a separate tool
Compliance and reports
Scamnetic is SOC 2 compliant. Our live compliance status and security documentation are available through our Trust portal, powered by Vanta.
How we handle your privacy
We build privacy into our products from the start, not as an afterthought. We follow U.S., European (GDPR and the EU AI Act), and other international privacy standards.
Your rights
You can ask to see, correct, or delete your personal data.
Only what we need
We minimize the data we collect and anonymize it wherever we can.
Clear use
We tell you plainly what we use your data for. [Confirm: "We never sell your personal data."]
Accountability
We take responsibility for how data is handled, including by the vendors we work with.
Responsible AI
Scamnetic uses AI to spot scams and verify payments. Our Responsible AI Policy explains how we build, test, and oversee these models so they're accurate, fair, and explainable.
Found a security issue?
We welcome reports from security researchers. If you find a vulnerability, email [security contact]. We'll confirm we received it, keep you updated, and won't take legal action against good-faith research that follows our Vulnerability Disclosure Policy.
Policies and agreements
Privacy Notice
Privacy Collection Notice (Australia)
Terms of Service (Consumers)
Terms of Service (Organizations)
Data Processing Agreement
List of Subprocessors
Responsible AI Policy
Data Protection and Privacy Impact Assessments (DPIA/PIA)
Vulnerability Disclosure Policy
Questions?
For privacy questions, email [privacy contact]. For security questions, email [security contact].