Manual 05 · Trust & Safety

Clickade Technical & Safety Requirements

Clickade games run on users' devices and may interact with browser or platform capabilities. Because of that, technical behavior is part of platform safety.

These requirements apply to both free and paid games.

1. Do Not Harm the Player's Device

A Clickade game must not intentionally:

  • damage or delete user files;
  • install malware;
  • steal credentials or authentication tokens;
  • perform unauthorized crypto mining;
  • spy on unrelated user activity;
  • create unwanted persistence;
  • modify system settings without a legitimate, clearly disclosed reason;
  • exploit vulnerabilities in Clickade, the browser, or the operating system.

A game that performs malicious behavior may be removed immediately.

2. Network Access

Games may use network access when it is reasonably related to the game, such as:

  • multiplayer;
  • cloud saves;
  • leaderboards;
  • game APIs;
  • downloading legitimate game content.

Games should not secretly send unrelated personal data to third parties.

Where Clickade provides network restrictions or permissions, games must respect them.

External links should be relevant and should not intentionally deceive the player.

Games may not use redirects to:

  • bypass Clickade payment systems;
  • send players to malware;
  • collect credentials deceptively;
  • imitate Clickade login pages;
  • evade moderation.

Clickade may display warnings when a game opens an external destination.

4. Downloads

A browser game should not unexpectedly download unrelated files.

If downloading a file is a legitimate game feature, the action should be understandable to the player.

Executable or high-risk downloads may be restricted or require additional review.

5. Popups and Windows

Games should not create abusive popup loops, unwanted windows, or navigation behavior that makes the player unable to leave the game normally.

Opening a new window may be allowed for a legitimate feature, but it should occur because of a clear player action whenever possible.

6. Storage

Games may use platform-approved browser or local storage for legitimate purposes such as:

  • settings;
  • saves;
  • cached content.

Games should not intentionally consume unreasonable amounts of storage without a legitimate reason.

A game must not treat browser storage as permission to collect unrelated personal information.

7. Permissions

When a game needs a sensitive device or browser permission, such as microphone or camera access, the reason should be connected to a real game feature.

Do not request permissions merely because they are available.

Do not attempt to bypass browser permission prompts.

8. Authentication

Games must not impersonate Clickade authentication or collect Clickade passwords, session cookies, authentication tokens, or other credentials.

If Clickade provides an official authentication or account API, games should use the supported integration instead of building deceptive login flows.

9. Payments, Tokens, and Game Ownership

A game must not directly alter or fabricate Clickade Token balances, paid-session access, permanent game ownership, or creator revenue.

The Clickade backend is authoritative for:

  • Token balances;
  • game prices;
  • game access models;
  • paid session creation;
  • permanent game ownership;
  • purchase entitlements;
  • creator revenue.

Clients may request access or launch a game, but they may not declare that a purchase succeeded or that the current account owns a game.

Browser state such as cookies, JavaScript variables, or localStorage is not authoritative proof of ownership.

Games must not instruct players to bypass Clickade's Token system for a purchase that is represented as a Clickade-paid session or one-time Clickade purchase.

10. Performance and Resource Use

Games should not intentionally consume extreme CPU, GPU, memory, bandwidth, or storage without a legitimate gameplay reason.

Heavy games are not automatically prohibited. The issue is abusive, hidden, or unrelated resource consumption.

11. Obfuscated or Suspicious Builds

Code minification, bundling, or obfuscation is not automatically prohibited.

However, Clickade may require additional review when a build's behavior cannot be reasonably inspected or when it triggers security concerns.

Creators may be asked for:

  • source code;
  • a reproducible build;
  • dependency information;
  • an explanation of network behavior;
  • other technical evidence.

12. Vulnerabilities

Do not knowingly exploit vulnerabilities in Clickade or another user's device.

If you discover a Clickade security issue, report it through the platform's designated security contact rather than using it against users.

13. Updates

A previously safe game can become unsafe after an update.

Clickade may rescan, re-review, suspend, or remove a game after a significant build change.

A Verified badge does not permanently approve every future version of a game.

14. Security Review

Clickade may use automated and manual review methods to investigate technical behavior.

A security review may examine:

  • uploaded files;
  • dependencies;
  • network destinations;
  • browser capabilities;
  • suspicious runtime behavior;
  • creator-provided source or build evidence.

A game may be temporarily unavailable while Clickade investigates a credible security concern.

15. Quick Summary

A Clickade game should behave like a game.

It may render, save progress, communicate with legitimate servers, use approved browser features, and provide normal gameplay functionality.

It may not quietly become a credential stealer, crypto miner, browser hijacker, or operating-system side quest.