Acceptable Use and Anti-Spam Policy — Pratick Auth

Last updated: 20 July 2026

This policy is issued by PRATICK and forms part of the Pratick Auth Terms of Service. It exists to protect message recipients, our clients, carrier and channel relationships, and the integrity of the platform. Violations may result in traffic filtering, suspension, or termination without refund of consumed credits, and, where warranted, reporting to authorities.

1. Consent is mandatory

You may only send messages to recipients who have requested or consented to receive them. For authentication messages (OTP), consent is inherent in the recipient's action (e.g., requesting a login code); you must not trigger OTP messages to numbers that have not initiated a corresponding action in your application. You must maintain records demonstrating the basis for messaging and honor opt-out requests without delay.

2. Prohibited uses

You must not use the Services to send or facilitate:

• Unsolicited bulk or promotional messaging (spam) of any kind;
• Fraud, phishing, impersonation of brands, persons, or institutions, or messages designed to deceive;
• Content that is unlawful in the destination country, including unlicensed gambling, unlawful financial schemes, or controlled goods;
• Harassment, threats, hate speech, or content harmful to minors;
• Malware, malicious links, or attempts to compromise devices or accounts;
• Artificially inflated traffic (AIT/SMS pumping), traffic designed to exploit carrier billing, or any scheme generating messages without genuine user actions;
• Circumvention of our routing, rate limits, filtering, or security controls, or use of the platform to probe or attack third parties;
• Messaging on behalf of third parties who have not themselves passed our verification, or resale of raw platform access without written agreement.

3. Sender identity and content rules

Message content must accurately identify the sending business or application. You must not use sender identities you are not authorized to use. Message categories must match their approved purpose (e.g., authentication templates used only for authentication). Where destination-country rules impose registration, sender-ID, or content requirements, you are responsible for compliance and we may enforce these rules on traffic through the platform.

4. Security obligations

You must keep API keys confidential, use live keys only from server-side systems, rotate keys upon suspected compromise, and notify us promptly of any suspected unauthorized use of your account. You must not test the platform's security without our prior written authorization.

5. Enforcement

We monitor traffic patterns, delivery quality, and complaint signals. We may, at our discretion and without prior notice where risk is immediate: filter or block specific messages, destinations, or senders; apply additional rate limits; suspend API keys; or terminate accounts. We apply enforcement proportionately and will communicate reasons where doing so does not compromise security or legal obligations.

6. Reporting abuse

To report abuse or suspected fraudulent messages sent via our platform, contact management@pratick.net. We investigate all reports.