Acceptable Use Policy

1. Scope

This policy is part of our Terms of Service. It applies to everything you create, upload, preview or share on RunSnip, to shared pages and the people who visit them, and to use of the API, the MCP server and any agent acting with your access token.

2. Prohibited content

Do not create, upload, share or link to content that:

• is illegal, or promotes or facilitates illegal activity;
• sexually exploits or endangers children — we remove it immediately, close the account and report it to the authorities;
• is malware, spyware, ransomware or any code designed to damage, disrupt or gain unauthorised access to devices, data or systems;
• is phishing or impersonation: fake sign-in pages, pages that imitate another person, company or service, or that collect passwords, payment details or other credentials under false pretences;
• is fraudulent or deceptive, such as scams, fake giveaways, fake stores or misleading financial offers;
• harasses, threatens, bullies or incites hatred or violence against people or groups;
• promotes terrorism or violent extremism;
• shares intimate images of someone without their consent;
• exposes other people’s personal information without their consent, including doxxing;
• infringes copyright, trademarks or other intellectual property rights;
• is spam, or exists mainly to redirect visitors elsewhere or to manipulate search rankings.

3. Prohibited activities

Do not:

• probe, scan or test the vulnerability of the Service, or bypass its authentication, sandboxing or security, except as described in section 4;
• access, or try to access, other users’ accounts, projects, tokens or data;
• use previews or shared pages to attack others — for example to mine cryptocurrency, send traffic or requests to third-party systems, or exploit visitors’ browsers;
• overload the Service, including by automated mass creation of accounts, projects, files or requests;
• use the Service mainly as file hosting or a content delivery network for material unrelated to a project;
• get around plan limits, bans or other enforcement, for example with multiple accounts or by recreating a banned project;
• publish access tokens, or share an account or token with people it was not created for;
• remove, hide or alter the RunSnip badge on shared pages by technical means unless your plan allows it;
• use the Service in a way that breaks the terms of the third-party services it relies on.

4. Security research

We welcome good-faith security research. If you find a vulnerability, email [email protected] with “Security” in the subject and enough detail to reproduce it. Test only against your own account and projects, do not access, change or delete other people’s data, do not disrupt the Service, and give us reasonable time to fix the issue before disclosing it. We will not take action against research that follows these rules.

5. Enforcement

When we find or are told about a violation, we may — depending on its severity and without prior notice where necessary — do one or more of the following:

• stop a project from being shared or remove specific content;
• ban a project, so that it can no longer be opened, edited, previewed or shared, with the reason shown to its owner;
• revoke access tokens;
• suspend or close the account;
• report the matter to the authorities where the law requires it or people are at risk.

Banning a project takes it out of use without deleting it: its files are kept, so a project restricted by mistake can be restored as it was.

If you believe an action was taken in error, contact us at [email protected] and we will review it.

6. Reporting abuse

To report a project or shared page that breaks this policy, email [email protected] with the page’s address, what is wrong with it, and any evidence that helps us act. For content that puts someone in immediate danger, please also contact your local authorities.

If a project misuses your trademark or brand — in its address, its content, its images or anything else — tell us and we may hide or ban it straight away, in good faith. You then have 24 hours to send the right you rely on (a registration number, the jurisdiction and the owner) and evidence that you hold it or act for whoever does; without it, the project is restored. RunSnip does not verify or decide who owns a name; see section 6 of the Terms. Impersonation, phishing and court or authority orders need no proof of a right: we act on them immediately, and keep the project so it can be restored if we were wrong.

7. Changes

We may update this policy as new kinds of abuse appear. The date at the top shows the latest version.