Legal

Privacy Policy

What we collect, why, and how long we keep it

Last updated November 1, 2026
On this page
  1. Who we are
  2. The short version
  3. This website
  4. The Microbot client
  5. Bug reports
  6. Microbot Cloud accounts
  7. Linked clients and launchers
  8. What we never collect
  9. Why we may use your data
  10. Service providers
  11. How long we keep data
  12. Your rights
  13. Community plugins
  14. Children
  15. Security
  16. Changes to this policy
  17. Contact

Who we are

Microbot is a free, open-source client for Old School RuneScape, based on RuneLite. It is run by the Microbot project ("Microbot", "we", "us"). This policy covers:

  • this website, themicrobot.com;
  • the Microbot client and the Microbot launcher;
  • Microbot Cloud, the dashboard at microbot.cloud, and the API behind it.

We are responsible for the personal data described here. You can reach us at aintaro@proton.me.

Microbot is not affiliated with Jagex Ltd. Jagex handles your RuneScape account under its own privacy policy, not this one.

The short version

  • You don't need an account to use Microbot. Without one, the client only sends anonymous technical data, and you can turn most of it off.
  • Google Analytics only runs on this website if you click Accept on the cookie banner.
  • Bug reports are only sent when you send one, and you choose what goes in them.
  • If you create a Microbot Cloud account and link a client, we store your email address and the in-game status your client reports, so the dashboard can show it to you.
  • We never receive your Jagex or RuneScape password, bank PIN or authenticator codes.
  • We don't sell your data and we don't use it for advertising.

This website

Analytics cookies

When you first visit, a banner asks whether you accept analytics cookies. If you click Accept, we load Google Analytics, which sets cookies and sends Google details such as the pages you view, how long you stay, your browser and device type, and your approximate location from your IP address. We use this to see which pages people use and what to improve. If you click Decline, or don't answer, Google Analytics is not loaded.

Your choice is saved in your browser's local storage under cookies-consent. To change it, clear this site's data in your browser and choose again. You can also use Google's opt-out browser add-on.

Live counters and the plugin list

Pages on this site show live numbers, such as players online, the latest client version and plugin install counts. To get them, your browser contacts microbot.cloud (our API) and chsami.github.io (where the plugin list is hosted, on GitHub Pages). Like any web server, those servers receive your IP address and browser details with each request. We don't use these requests to identify you.

Hosting

This website is hosted on Microsoft Azure Static Web Apps. Microsoft processes standard request data, such as your IP address, to serve the pages and protect the service.

The Microbot client

The client runs on your computer. It sends the following to microbot.cloud even if you don't have a Microbot Cloud account:

  • Update check and tip of the day. The client asks which version is current and fetches a random tip for the loading screen.
  • Session ping. Each time you start the client, it gets a random session ID that isn't linked to you. Every 10 minutes it sends that ID, your client version and whether you are logged in to the game. We use this for the "players online" counter. Sessions are deleted once the client stops sending pings.
  • Error reports. When a script or plugin throws an error, the client sends the plugin name and version, the client version, the error message and the stack trace. Character names are removed before sending. We group identical errors so we know which ones affect the most players.
  • Freeze logs. If the client freezes, it sends the last part of your client.log file, with character names removed, at most once every 10 minutes.
  • Plugin install counts. When you install a plugin from the Plugin Hub, the client tells us its name and version so we can show install counts. This contains no identifier.

To count how many different players hit the same error without storing who they are, the server makes a short code from a shortened version of your IP address and the current date. Because the date is part of it, the code changes every day and can't be traced back to your IP address.

Turning it off. Turn on Disable telemetry in the Microbot settings, or start the client with -Dmicrobot.disableTelemetry=true. This stops the update check, the tip of the day, session pings, error reports, freeze logs, bug reports and Microbot Cloud linking. Plugin install counts are still sent, because the Plugin Hub's install numbers depend on them. Some changes take effect after you restart the client.

Bug reports

When you send a bug report from the client, it contains your description plus the parts you leave ticked:

  • Diagnostics: client, RuneLite and launcher versions, Java version, operating system, and some Microbot and walker settings.
  • Plugin settings for the plugin you are reporting.
  • Game state: for example your world, location, skill levels and inventory.
  • Recent errors and the end of your client log.
  • A screenshot of the game window.

Character names are removed from the text parts before sending. A screenshot shows whatever is on your game screen, so check it before you send it.

You get a report code so you can see when we've answered or fixed the report, and you can reply to our questions. If your client is linked to Microbot Cloud, the report is also linked to your account so it appears in your dashboard.

Microbot Cloud accounts

Microbot Cloud accounts are optional. When you create one, we store:

  • your email address and, if you give one, a display name;
  • your password, stored only as a one-way hash, which means we can't read it;
  • whether your email is verified, when you joined and when you last signed in;
  • your sign-in sessions, so you stay signed in for up to 30 days.

We use your email address to verify your account, reset your password and, if you turn them on, send you alerts. We don't send marketing emails.

To block automated sign-ups, the sign-up, sign-in and password reset forms use Cloudflare Turnstile. Turnstile checks your browser and sends Cloudflare your IP address.

The dashboard counts which pages and features are used. To do this, it records the event name and page, a code made from a shortened version of your IP address, your browser and the date (which changes daily), and a one-way hash of your account ID if you are signed in. If your browser sends a Do Not Track or Global Privacy Control signal, the dashboard doesn't record these events. The dashboard stores your sign-in in cookies and some display preferences, such as dismissed tips, in your browser.

Linked clients and launchers

You can link a Microbot client or launcher to your Microbot Cloud account. A link is only made when you approve it on microbot.cloud, and you can remove it at any time from the dashboard.

A linked client sends:

  • which scripts are running, and alerts such as a script stopping, an error, a logout, death, low hitpoints or a disabled account;
  • in-game status: world, combat level, hitpoints, prayer, run energy, special attack, location, skill levels and experience gained, and inventory items;
  • progress samples (experience gained and time played), which we use to draw the progress charts.

Screenshots and remote control (such as stopping scripts or logging out from the dashboard) only work when you allow them in the client. Screenshots are taken only when you ask for one in the dashboard, and are deleted after 15 minutes.

A linked launcher sends its name, its version, which linked clients it can start, and the proxies you saved in it. For each proxy it sends the name you gave it, its host and port, and a code made from the full proxy address, which the dashboard uses to tell proxies apart. Proxy usernames and passwords are never sent.

You can have alerts sent by email or to a Discord webhook that you add. If you add a webhook, we send alert messages to Discord, where Discord's privacy policy applies.

What we never collect

  • Your Jagex or RuneScape password, bank PIN or authenticator codes. Accounts you save in the client or launcher stay on your computer.
  • Your proxy usernames and passwords.

If you are in the European Economic Area or the United Kingdom, the GDPR requires a legal reason for each use of your data. Ours are:

  • Your consent: Google Analytics on this website. You can withdraw consent at any time.
  • Providing a service you asked for: your Microbot Cloud account, linked clients and launchers, alerts, and bug reports you send.
  • Legitimate interests: anonymous client data (update checks, session pings, error reports, freeze logs and install counts), dashboard usage counts and server logs. We use these to fix bugs, keep the service running and protect it from abuse, and we've designed them to collect as little as possible.

Service providers

We use these providers to run Microbot. They only process data on our behalf.

  • Hetzner Online GmbH (Germany): hosts microbot.cloud, our API and our database, in Falkenstein, Germany.
  • Microsoft (Azure Static Web Apps): hosts this website.
  • GitHub: hosts our source code, client downloads and the Plugin Hub list.
  • Google (Google Analytics): website analytics, only if you accept.
  • Cloudflare (Turnstile): bot protection on Microbot Cloud sign-up and sign-in.
  • Resend: sends account and alert emails.
  • Discord: delivers alerts to a webhook, only if you add one.

Some of these providers process data outside the European Economic Area, mainly in the United States. When they do, they rely on safeguards recognised under the GDPR, such as the EU-U.S. Data Privacy Framework or the European Commission's Standard Contractual Clauses.

How long we keep data

  • Session pings: deleted once the client stops pinging.
  • Error reports: deleted 180 days after the error was last seen, or after 30 days if only one player reported it. The daily codes used to count players are deleted after a day.
  • Freeze logs: 14 days.
  • Bug reports: screenshots, logs, game state, plugin settings and diagnostics are deleted after 30 days. The description, status and our replies are kept for 180 days.
  • Progress samples: 31 days.
  • Alert history: 30 days.
  • Dashboard screenshots and remote commands: 15 minutes. Launcher start requests: 1 hour.
  • Dashboard usage counts: 90 days.
  • Web server access logs (IP address, time, requested address and browser): 14 days.
  • Your Microbot Cloud account and linked devices: until you ask us to delete them.
  • Google Analytics data: kept according to the retention setting in our Google Analytics account.

Your rights

Depending on where you live, and in all cases under the GDPR, you can ask us to:

  • show you the personal data we hold about you and give you a copy;
  • correct it;
  • delete it, including your whole Microbot Cloud account;
  • limit how we use it, or stop using it where we rely on legitimate interests;
  • send it to you in a format you can reuse.

Email aintaro@proton.me from the address on your Microbot Cloud account, so we can check the request is yours. We reply within one month. Most client data is anonymous, so we usually can't link it to you. If you want a specific bug report removed, include its report code.

If you think we've handled your data wrongly, please tell us first. You also have the right to complain to the data protection authority in your country.

Community plugins

Plugins on the Plugin Hub are written by community developers and run on your computer. Some contact other services, for example price lookups on the OSRS Wiki. This policy doesn't cover data that a plugin or another service collects. Check a plugin's description and source code if you're unsure.

Children

Microbot is not meant for children under 16, and we don't knowingly collect data from them. If you believe a child has created a Microbot Cloud account, contact us and we'll delete it.

Security

All traffic to microbot.cloud is encrypted with HTTPS. We store passwords and device link tokens only as one-way hashes, and our database can't be reached from the internet. No system is perfectly secure, but if a breach affects your data we'll tell you and the relevant authorities as the law requires.

Changes to this policy

We'll update this policy when what we collect changes. The date at the top shows the latest version. If a change matters, we'll also announce it on our Discord and, where appropriate, by email to Microbot Cloud account holders.

Contact

For privacy questions or requests, email aintaro@proton.me. For everything else, join our Discord.