Privacy

Your developer data stays on your machine

MyDevTools Desktop has no account system and no backend. Tool input, notes, snippets and credentials are processed and stored on your device, in a database encrypted with a key from your OS keychain. This page describes exactly what that means — including the connections that do leave your machine, and why.

Where your data actually lives

There is no MyDevTools server in this diagram, because there is no MyDevTools server.

Your computer

Everything below runs and stays inside the app on your machine.

  • Developer tools (formatting, encoding, hashing, parsing)
  • API client — collections, environments, history
  • SQL · MongoDB · Redis · S3 clients
  • Notes, snippets, tasks, bookmarks
  • Encrypted vault — passwords, API keys, .env sets
  • SQLCipher database, keyed from your OS keychain

What leaves, and why

Only what a tool was pointed at — going straight from your machine to that destination, never through us.

  • API client requestsThe hosts you type into the request bar
  • Database & storage connectionsYour PostgreSQL, MySQL, MongoDB, Redis or S3 endpoint
  • DNS and WHOIS lookupsPublic DNS resolvers and RDAP/WHOIS registries
  • Update checkGitHub releases, to see whether a newer version exists
  • Anonymous usage events (opt-in, off by default)Aptabase — a rotating session id, app version and locale. Nothing else.

Every claim here is checkable — the telemetry module is about a hundred lines, and the rest of the app is open source under the AGPL-3.0.

Local processing and local storage

The tools run inside the desktop app on your machine. There is no MyDevTools server to send anything to, which is a property of the architecture rather than a promise about our conduct.

  • Formatting, encoding, hashing and parsing happen on your device.
  • App data lives in a local SQLCipher database, encrypted with a key held in your OS keychain.
  • Credentials, API keys and password vault entries get a second layer of encryption using a master password only you know.

Connections you initiate

The app itself needs no network. Some tools exist precisely to reach somewhere, and those connect to the destination you configure — not through us.

  • The API client sends the requests you write, to the hosts you choose.
  • The SQL, MongoDB, Redis and S3 clients connect straight from your machine to your database or bucket.
  • DNS and WHOIS lookups query public registries, and the updater checks GitHub for new releases.

No account, no sync, no telemetry by default

There is nothing to sign up for and nothing that quietly phones home. Usage analytics are off until you turn them on.

  • No sign-up, no sign-in, no activation and no license key.
  • No cloud sync and no shared storage — the account layer was removed from the project entirely.
  • Optional anonymous usage events (a rotating session id, app version and locale) only if you enable them. No device id, no file paths, nothing typed into a tool.

This website is not the app

mydevtools.tech documents the tools and hosts the download. The tools do not run here, and this site has ordinary website properties — it is a normal web page, with standard web analytics.

  • No web app, no login and no dashboard — there is nothing here to store your data in.
  • The privacy properties described above belong to the desktop app on your machine.
  • Both are open source under the AGPL-3.0, so either claim can be checked against the code.