Acceptable Use Policy

This Acceptable Use Policy explains what is not allowed on Mock API Studio. It protects the service, our users, infrastructure providers, and the broader developer community.

Mock API Studio is for building and testing mock APIs. It must not be used to create, host, distribute, automate, or support harmful, illegal, deceptive, or abusive activity.

• Do not use Mock API Studio for anything illegal in your jurisdiction or the jurisdictions where the service operates.
• Do not create or distribute malware, spyware, ransomware, exploit kits, botnets, phishing kits, credential theft flows, or tools intended to compromise systems.
• Do not use the service to threaten, harass, exploit, dox, or harm others.

• No content that infringes intellectual property rights or violates takedown obligations.
• No content that is sexually exploitative, abusive, or harmful to minors.
• No content that promotes violence, terrorism, extremist recruitment, or targeted harassment.
• No content that contains real secrets, credentials, private keys, payment card data, health data, government identifiers, or production customer records unless we have explicitly agreed in writing that the service may process it.

• No crypto mining, resource mining, or similar compute abuse.
• No traffic generation, load amplification, denial-of-service activity, stress testing against third parties, or attempts to degrade other systems.
• No spam, unsolicited messaging, fake engagement, abusive scraping, credential stuffing, account checking, or automation designed to evade platform limits.
• No mirrors, userbots, torrent aggregation, piracy workflows, or services whose primary purpose is to bypass another platform's rules.

You may test your own projects and local runtimes in a responsible way. You may not test, scan, attack, or attempt to access Mock API Studio systems, other users' projects, accounts, tokens, or infrastructure unless we have given explicit written authorization.

If you discover a vulnerability, report it responsibly and do not access, modify, destroy, disclose, or exfiltrate data.

• Do not bypass authentication, authorization, email verification, usage limits, billing checks, plan restrictions, rate limits, storage limits, or security controls.
• Do not create multiple accounts to avoid limits, enforcement, or payment obligations.
• Do not interfere with logs, monitoring, abuse prevention, or service reliability.
• Do not reverse engineer private service APIs except where applicable law gives you a non-waivable right to do so.

Mock API Studio generates synthetic data for development and testing. You are responsible for reviewing generated data and for ensuring your schemas, examples, and mock responses do not include prohibited or sensitive information.

Do not use generated mock data to impersonate real people, mislead users into believing a fake service is real, or support fraudulent activity.

We may investigate suspected violations and take action when needed to protect the service, users, infrastructure, or legal compliance.

Actions may include warnings, rate limits, feature restrictions, token revocation, project deletion, account suspension, account termination, reporting to providers or authorities, and preserving information needed for investigation or legal compliance.

If you believe Mock API Studio is being used for abuse, contact us using the contact address published in the product or on our website. Include relevant URLs, account identifiers if known, timestamps, and a short explanation of the concern.

We may update this Acceptable Use Policy as new abuse patterns, legal requirements, infrastructure requirements, or product features emerge. Material changes may require renewed acceptance before continued use.