7:46 AM
unreliablecode
Developer Feed Blogs Shorts Videos Git Repositories Gists Price Articles
Select Language
๐Ÿ‡บ๐Ÿ‡ธ English English ๐Ÿ‡ท๐Ÿ‡บ ะ ัƒััะบะธะน Russian ๐Ÿ‡ฐ๐Ÿ‡ฟ าšะฐะทะฐา›ัˆะฐ Kazakh ๐Ÿ‡ง๐Ÿ‡พ ะ‘ะตะปะฐั€ัƒัะบะฐั Belarusian ๐Ÿ‡ต๐Ÿ‡ฑ Polski Polish ๐Ÿ‡ญ๐Ÿ‡ท Hrvatski Croatian ๐Ÿ‡ฏ๐Ÿ‡ต ๆ—ฅๆœฌ่ชž Japanese ๐Ÿ‡ฐ๐Ÿ‡ท ํ•œ๊ตญ์–ด Korean ๐Ÿ‡ธ๐Ÿ‡ฆ ุงู„ุนุฑุจูŠุฉ Arabic ๐Ÿ‡น๐Ÿ‡ท Tรผrkรงe Turkish ๐Ÿ‡ฉ๐Ÿ‡ช Deutsch German ๐Ÿ‡ณ๐Ÿ‡ฑ Nederlands / Vlaams Dutch / Belgian ๐Ÿ‡ฎ๐Ÿ‡ฉ Bahasa Indonesia Indonesian
Sign In
Developer Feed Blogs Shorts Videos Git Repositories Gists Price Articles
Create Account Sign In
Pick an emoji
unreliablecode Legal

Acceptable Use Policy

This policy sets the boundaries for everything you run, host, upload or publish on unreliablecode โ€” posts and comments, blogs and videos, repositories and gists, Drive files, submitted apps, server listings, and workloads on Cloud VPS, web hosting and lab environments. It forms part of the Terms of Service, and breaking it is grounds for content removal, suspension or termination.

Effective 22 August 2026 unreliablecode.net Platform v5.2.9
Legal centre
Terms of Service License Agreement Acceptable Use Policy Privacy Policy Billing & Refund Policy
On this page
1. The underlying principle 2. Illegal content and activity 3. Malware, exploitation and abuse of systems 4. Protecting the platform 5. Community conduct 6. Other people's work 7. Servers, hosting and networks 8. Reporting a violation 9. How we enforce this

1. The underlying principle

The platform is shared. Your repository sits on the same disks as someone else's, your VPS shares a node with other people's servers, and your posts appear in the same feed as everyone else's. This policy exists so that one account cannot make the platform unusable, unsafe or illegal for the rest.

Two questions cover most cases: is it legal where you are and where the servers are? and would it harm another user, another network, or the platform itself? If either answer is uncomfortable, it does not belong here.

This policy is not exhaustive. We may act on conduct that clearly violates its spirit even where no specific line below names it.

2. Illegal content and activity

You must not use unreliablecode to store, transmit, publish, host or facilitate anything unlawful. That includes, without limitation:

  • Child sexual abuse material, or any content that sexualises a minor, in any medium, including drawn, generated or synthetic material. This is a zero-tolerance category: the account is terminated immediately, the material is preserved as evidence, and the matter is reported to the authorities.
  • Content that incites, praises or facilitates terrorism, mass violence or genocide.
  • Trafficking in people, weapons, controlled substances, stolen goods, stolen data or stolen credentials.
  • Fraud in any form โ€” phishing, false invoices, fake shops, advance-fee schemes, romance scams, investment or crypto scams, and "free key" or account-generator pages.
  • Money laundering, sanctions evasion, or the use of the wallet, affiliate or reseller systems to move the proceeds of crime.
  • Content that unlawfully defames a person, or that breaches someone's privacy or data-protection rights.

3. Malware, exploitation and abuse of systems

You must not upload, host, distribute or run:

  • viruses, worms, ransomware, rootkits, keyloggers, credential stealers, remote-access trojans, botnet clients, droppers, loaders or web shells;
  • software whose purpose is to compromise systems, accounts or data belonging to other people;
  • phishing kits, cloned sign-in pages, or infrastructure supporting a phishing campaign;
  • cryptocurrency miners of any kind on VPS, web hosting or lab environments โ€” including "idle" mining, browser miners served to visitors, and mining hidden inside another workload.

You must not use the platform to attack anything, whether ours or a third party's: denial-of-service traffic, port scanning, vulnerability scanning without authorisation, brute-force or credential-stuffing runs, spoofed traffic, spam relays, or open proxies and open resolvers left exposed.

Security research and CTF work are welcome โ€” inside the boundaries you are entitled to test. Analysing a sample in an isolated lab, publishing a write-up, or hosting a deliberately vulnerable target you own is fine. Pointing any of it at systems you do not have written permission to test is not, and "it was only a test" is not a defence.

Uploads are scanned automatically, and the platform runs intrusion detection across requests. Attempting to evade, disable or poison those systems is itself a violation.

4. Protecting the platform

You must not:

  • circumvent quotas, storage limits, rate limits, paywalls, feature gates or licence checks;
  • register multiple accounts to multiply free allowances, farm points or rewards, inflate rankings, or evade a suspension;
  • manipulate votes, reactions, views, referrals, affiliate clicks or leaderboard standings, whether by script, by coordination, or by paying for engagement;
  • scrape the platform at a rate that burdens it, or bypass the API and its authentication to do in bulk what the interface does one page at a time;
  • probe, load-test or stress the platform's own infrastructure without written permission;
  • run workloads engineered to consume a node's shared CPU, I/O or network capacity to the detriment of other customers.

Automation is not banned โ€” bots, CI jobs and scheduled scripts are legitimate. Keep them authenticated, rate-limited and identifiable, and stop them if we ask.

5. Community conduct

Across the feed, forums, chat, groups, comments and direct messages:

  • No harassment, targeted abuse, stalking, or coordinated pile-ons.
  • No hate speech or dehumanising content directed at people on the basis of race, ethnicity, national origin, religion, disability, gender, gender identity, sexual orientation, age or serious illness.
  • No threats of violence, and no encouraging self-harm or suicide.
  • No doxxing โ€” publishing someone's private information (home address, phone number, identity documents, workplace, private accounts) without their consent.
  • No impersonation of another person, of staff, or of an organisation, including through a misleading display name, avatar or verified-looking badge.
  • No unsolicited advertising, referral spam, mass DMs or repetitive promotional posting.
  • No sexually explicit material in public areas โ€” feed, forums, gallery, videos, shorts, stories, profiles, group listings โ€” and none at all involving people who have not consented to its publication.
  • No gore, shock content or animal cruelty posted for its own sake.

Disagreement is fine and technical argument is expected. Contempt for the person on the other side of it is not.

6. Other people's work

Do not upload, host or publish material you do not have the rights to. In practice this means:

  • no pirated software, cracks, keygens, licence bypasses or leaked paid content;
  • no reuploading someone else's video, article, artwork, code or course material as your own;
  • no using a trade mark or brand in a way that suggests an affiliation you do not have;
  • respect the licence of every open-source component you redistribute, including its attribution requirements;
  • if you submit an app to the App Store, you must have the right to distribute it and to grant the licence you attach to it.

Rights holders can report infringement through the takedown process in section 13 of the Terms of Service. Repeat infringers lose their accounts.

7. Servers, hosting and networks

In addition to everything above, for Cloud VPS, web hosting, port forwarding and lab environments:

  • Keep your server patched and its credentials strong. A compromised server that starts attacking others is treated as an abusive server, whether or not you knew.
  • Do not run open mail relays, or send bulk email without verified opt-in consent and working unsubscribe handling.
  • Do not run Tor exit nodes, open proxies or anonymising relays that emit third-party traffic under our IP addresses.
  • Do not host content whose purpose is to attract abuse complaints or blocklisting of our address space.
  • Do not resell your VPS as shared hosting to third parties unless your package permits it.
  • Use only the ports and forwards allocated to you, and do not attempt to reach other tenants, the hypervisor, the management network or the storage backend.

We may access, isolate, throttle or power off a service immediately where it is compromised, under attack, attacking others, or destabilising a node โ€” see section 8 of the Terms of Service.

8. Reporting a violation

If you find something that breaks this policy, report it. Use the in-page report control where one exists, and open a support ticket for anything serious, with the exact URL and enough detail for someone to verify it.

Reports about ongoing harm โ€” active phishing, malware distribution, an attack in progress, or child sexual abuse material โ€” are handled ahead of everything else. Do not attempt to investigate or retaliate yourself; collecting "evidence" by attacking the offending service is its own violation.

We do not disclose the outcome of a report to the reporter in most cases, and we do not reveal who reported what.

9. How we enforce this

Enforcement is proportionate to the harm, the intent, and the account's history. Depending on the case we may:

  • remove, hide or de-index the content;
  • issue a warning and require a fix within a stated time;
  • rate-limit, restrict or remove access to a specific feature;
  • suspend, isolate or power off a server or lab environment;
  • revoke a licence, forfeit rewards, points or affiliate earnings obtained through the violation;
  • suspend or permanently terminate the account;
  • preserve evidence and report the matter to law enforcement.

For minor, first-time and clearly accidental breaches we normally warn first. For fraud, attacks on infrastructure, malware distribution and child sexual abuse material, action is immediate and permanent, and no refund is due.

If you believe an enforcement decision was wrong, appeal through a support ticket with your account name and what you think happened. Appeals are read by a human. Creating a new account to get around a suspension forfeits the appeal.

Questions about this document

Anything specific to your account, an invoice or a takedown request should go through a support ticket so it is on the record and reaches someone who can act on it. General questions are fine in the community channels.

Open a support ticket noreply@unreliablecode.net
unreliablecode v5.2.9
Home Price
Terms of Service License Agreement Acceptable Use Policy Privacy Policy Billing & Refund Policy

© 2026 unreliablecode. All rights reserved.

All Systems Operational
Performance notice

This site renders an animated background and a real-time glass interface. On mobile hardware this is demanding and may cause reduced frame rates, heat or faster battery drain. A device with a Snapdragon 888-class chipset or newer (or an equivalent from another vendor) is recommended for the full experience.

On lower-powered devices, switch the background to None (flat) โ€” this disables the animation and the glass effects for a noticeably lighter interface. You can change it at any time from the background button in the lower-left corner of the screen.