Acceptable Use Policy

Not allowed

• Sexual content involving minors of any kind.
• Malware: building ransomware, keyloggers, info-stealers, botnets, or tooling to evade antivirus for attacks.
• Credential or data theft: stealing passwords, cookies, tokens, cards or personal data from other people.
• Attacking systems you don’t own: hacking, DDoS, brute-forcing or breaking into accounts, networks or services without authorization.
• Fraud: phishing, scams, fake documents, impersonation or money laundering.
• Harassment and extremism: doxxing, stalking, threats, swatting, terrorism or violent extremist content.
• Cloning SaaSWish: using SaaSWish to copy the service itself or extract its source code, prompts or internals.

Allowed security work

Ordinary security engineering is welcome: testing and hardening your own applications, fixing vulnerabilities, writing tests and detection rules, authorized penetration tests and bug bounties, CTFs, fraud detection, content-moderation tooling and phishing-awareness training for your own staff.

Enforcement

Requests are checked by automated rules and a classifier. A request that clearly violates this policy is blocked and recorded with redacted evidence (secrets are never stored). The most serious categories suspend the account immediately; others produce a warning first and a suspension if they repeat. A suspended account cannot start or continue work, its API keys are refused and no further Dev Units are charged. Organizations can be suspended when an owner is responsible.

Appeals

If your account is suspended, sign in to see the reason and submit one appeal explaining what happened. The SaaSWish founders review every appeal and either restore access or keep the suspension with a final note. You receive the decision by email and on the suspension page.