Acceptable Use Policy

This Acceptable Use Policy applies to all access to and use of the PayeeProof website, API, integrations, documentation, and related services.

1. Purpose

PayeeProof is designed to support lawful operational verification in digital-asset payment workflows. You must use the Service responsibly and in a way that does not create legal, security, abuse, or reliability risk.

2. Prohibited uses

You may not use the Service to:

• violate any law, regulation, sanctions regime, court order, or third-party right;
• facilitate fraud, phishing, malware, credential abuse, social engineering, or deceptive practices;
• probe internal systems, test stolen credentials, enumerate IDs, or attempt unauthorized access;
• bypass rate limits, access controls, tenant boundaries, or other service restrictions;
• send excessive traffic, spam, malformed payloads, or abusive requests;
• misrepresent outputs, screenshots, reports, or verification records as guarantees or official certifications;
• submit categories of data the Service is not designed for, such as children’s data, biometric data, health data, or payment-card data;
• use the Service to build or market a directly competing service.

3. Security expectations

You must protect credentials, API keys, webhook secrets, and access tokens; validate your own downstream logic before using outputs operationally; respect published limits; and notify PayeeProof promptly of suspected abuse or security incidents.

4. Enforcement

PayeeProof may monitor use for security, abuse prevention, and service reliability. We may suspend, throttle, block, or terminate access immediately if we reasonably believe your use violates this policy, the Terms of Service, or applicable law.

5. Reporting

Security or abuse reports: hello@payeeproof.com

6. Changes

We may update this policy from time to time. The latest version posted on this page will apply when posted.