Acceptable use policy

Last updated: 24 October 2026

This policy is part of our terms of service. It applies to everything you do with Swastik Codes, including requests, collection runs, load tests, monitors, flows, webhooks, mock servers, comments and published documentation.

Only test what you are allowed to test

You may send requests, run load tests and schedule monitors only against systems that you own, or that you have permission to test, and only within the limits that permission allows. Calling a public API within its published terms and rate limits is fine. Load testing someone else's API, website or infrastructure without written permission is not.

You must not

• Attack or probe systems. No denial-of-service attacks, flooding, vulnerability scanning, port scanning, brute-forcing credentials, credential stuffing or exploiting security flaws in systems you are not authorised to test.
• Get around our safeguards. No attempts to reach private, internal or cloud-metadata addresses through the service (for example with DNS rebinding or redirects), to bypass rate limits, usage caps or the limits on load tests, or to use the service as an open proxy or anonymiser.
• Break into the service. No attempts to access other users' accounts, workspaces or data, or to probe, scan or test the vulnerability of Swastik Codes itself, except as described in our responsible disclosure policy.
• Overload the service. No automated use that places an unreasonable load on our infrastructure, such as monitors or flows designed to run continuously to keep connections open, or creating many accounts to multiply limits.
• Send spam or abuse. No unsolicited bulk messages through webhooks, monitor alerts, team invitations, comments or the contact form.
• Host harmful content. No malware, phishing pages, or content that is illegal, infringes intellectual property or privacy rights, or harasses, threatens or exploits others, whether in mock server responses, published documentation, public workspaces or comments.
• Expose other people's data. Do not publish personal data, credentials or secrets that belong to others.
• Break the law. No use that violates applicable laws, including export controls and sanctions.

Load tests and monitors

Load tests send many requests in a short time. Keep them to systems you control, start small, and stop if you see unintended impact. The hosted service caps virtual users, duration and concurrent runs, and these limits may change. Monitors run on a schedule until you turn them off; disable monitors you no longer need.

Mock servers and published docs

Mock server URLs and published documentation are public by default. Use them for API examples, not for hosting files or content unrelated to an API. Private mocks require an API key.

Enforcement

If we believe this policy has been broken, we may remove content, disable mocks, monitors, flows or webhooks, rate-limit or block requests, suspend or close accounts, and report illegal activity to the authorities. Where reasonable, we will tell you what happened and why.

Reporting abuse

To report abuse of Swastik Codes, for example traffic you believe comes from our service, email support@swastik.codes with the time, the target and any request details you have. Requests our servers send carry our IP addresses; outgoing webhook and monitor alert requests identify themselves with the user agent SwastikCodes-Webhook.