Keep the current clean
Acceptable Use
Last updated: [Date]
Most zaps are ordinary: work, photos, builds, exports, the file that would not fit in chat. This policy covers the opposite: files or behavior that harm people, break the law, or turn the service into someone else’s problem. It forms part of our Terms.
The line
Do not use zappp to harm people, break the law, deceive recipients, or attack the service. The examples below are specific, not exhaustive. Clearly abusive conduct is not allowed just because we did not predict its exact wording.
What never rides a zap
You may not use zappp to send, request, or distribute:
- Illegal material, including content that exploits or endangers minors. We apply zero tolerance and report qualifying material to the appropriate authorities.
- Malware or hostile code, including ransomware, spyware, viruses, credential stealers, or software built to damage, hijack, or secretly monitor systems.
- Phishing, scams, or fraud tools, including fake invoices, impersonation assets, credential traps, and material meant to steal money, data, or access.
- Content you do not have the right to share, including pirated software, media, and other infringing work. See our DMCA & Copyright page.
- Threats, harassment, or doxxing, including stalking material, intimidation, or private information published to expose or endanger a person.
- Unauthorized confidential or personal data, including records, credentials, or private information you are not permitted to distribute.
Behavior that gets cut off
You also may not:
- Probe, scan, exploit, or bypass zappp’s security, rate limits, file limits, expiration, or access controls.
- Use zappp to send spam or support unsolicited bulk messaging.
- Disrupt the service or its providers, including denial-of-service activity, abusive automation, or resource exhaustion.
- Resell, mirror, frame, or repackage zappp as your own service without written permission.
- Misrepresent who sent a zap, who requested a file, or what a link contains in order to deceive someone.
How we cut abuse off
We use reports, automated safeguards, and service-health monitoring. When we reasonably believe this policy has been violated, we may inspect relevant activity, disable or delete zaps, block uploads or links, restrict access, preserve evidence, and cooperate with law enforcement where required or appropriate.
Context matters. A mistake is not treated like an organized phishing campaign. Protecting recipients and keeping zappp usable comes first.
Bad zap?
Send us an abuse report. The link and a little context give us what we need to act quickly.