Help

Privacy and your data

Your requests, results, and secrets stay on your computer. Here is where they live, how secrets are protected, and the little the app ever sends.

Everything stays on your computer

Requests are sent from your computer straight to the API you test — that's what lets the app reach internal and VPN-only APIs. There is no APITestCenter server in between, and nothing about your requests, answers, or results is uploaded. Signing in is optional and carries only your plan, never your work.

Where your files are

Saved requests, environments, collection run orders, history, and copies of the files you upload (in files) are plain files in one folder:

SystemFolder
Windows (installer or portable)%APPDATA%\ApiTestCenter
Windows (Microsoft Store version)Documents\APITestCenter
macOS~/Library/Application Support/ApiTestCenter
Linux~/.local/share/apitestcenter

About → Open folder opens it. You can back it up, copy it to another computer, or keep saved requests in a Git repository for CI.

To use another folder, set the ATC_DATA_DIR environment variable to it before starting the app. The command line reads it too, and --data <folder> picks a folder for one command.

Only one copy of the app runs at a time. Opening it again brings the open window to the front.

Secrets

Tokens, passwords, API keys, OAuth client secrets and the private keys of client certificates — in saved requests, folder settings, secret environment variables and certificates.json — are never written into those files. OAuth tokens the app gets for you, and cookies APIs set (the cookie jar), are kept there too, until they run out. They are encrypted in a separate file, secrets.enc, with a key your operating system protects (Windows DPAPI, macOS Keychain, Linux keyring), so another user of the computer cannot read them. The key stays on this computer: if you copy the folder to another computer, type the secrets again there. Exports never contain them either; auth appears as a type only. Earlier answers of saved requests (the last 20 of each) are kept in the responses folder, with values that look like secrets replaced by <hidden> before they are written; Forget these answers deletes them. What Request sent shows after a Send — headers with their real values, behind Show secrets — stays in the app's memory for that answer and is never written to History or any file.

Without a keyring there is no safe place for the key, so secrets are kept in memory only and are gone when the app closes. This happens:

  • on Linux without a keyring (no GNOME Keyring, KWallet, or similar);
  • in npx apitestcenter ui, the app in your browser — secrets last until you stop it.

Manage environments then says “Secret values are never written to disk. In this browser setup they are kept by the engine until it restarts; the desktop app encrypts them.” For tests you keep, write {{token}} and pass the value with --var on the command line.

Values saved from answers (Save values) are kept in memory until you close the app.

Finding servers on your computer

The Base URL picker lists web servers running on your computer. To find them, the app asks your operating system for its list of open ports and the program behind each, then sends one request to each port on your own computer to see which answer like a web server. That list is never stored and never sent anywhere. See Choosing a base URL.

What the app sends — the complete list

  1. Your requests, to the APIs you choose to test.
  2. An update check — see below. Nothing about you or your tests is sent.
  3. Usage counts — anonymous, and off with one switch. See below.
  4. Only if you sign in or add a license key: your email and this computer's name to sign in, then about twice a day the plan check (your sign-in or your key, to see whether the plan is still paid). See Signing in and your plan.

Update check

The desktop app downloads a small file from GitHub describing the latest version: about 15 seconds after it starts, then every 6 hours. Only stable releases count.

Your copyWhen a new version is out
Windows installer, Linux AppImageNothing downloads until you say so. x.y.z available appears in the status bar; it opens what the new version brings, with Download and install or Not now. The download shows its progress, then Restart now or Restart later — later, it installs the next time the app quits.
Windows portable, macOS, Linux .debIt can't replace itself: the same x.y.z available shows what's new, with Open the download page.
Microsoft StoreNo check — the Store keeps it up to date.

Check for updates in About does the same at once: if there's a new version, its dialog opens.

Important updates — a fix you shouldn't wait for — also ask when the app finds them: “Important update: APITestCenter x.y.z” with the reason, and Download and install or Later (or Download for a copy that can't replace itself). Later asks again the next time the app starts. Other updates never interrupt you.

What's new. After an update, the app opens a card with what changed since the version you had; open it again any time from About → What's new in this version or Settings → Updates and about. The notes ship with the app and with the update file, so nothing extra is downloaded.

To turn the check off, set the environment variable ATC_NO_UPDATE=1 before starting the app. About then says the check is turned off. npx apitestcenter ui never checks. See Troubleshooting → Updates.

Usage counts

On unless you turn them off — and nothing is sent before you've been told. Once you've used the app (sent a request, say), a small card says Anonymous usage counts are on, with See exactly what's sent, OK and Turn off. Change it any time in Settings → Privacy. If you had already said no, it stays off. An organisation can turn it off for every user with the environment variable ATC_NO_USAGE=1.

When it's on, once a day the app sends: how many requests, performance tests, compares, and imports you ran on each finished day, the app version, the operating system and processor type, and a random install number. Never URLs, results, names, or anything you type.

Before you answer, the counts are kept on your computer only, so a yes has something to send. Say no and the kept counts are deleted, nothing more is counted, and the install number is replaced with a new one — so if you turn it on later, old and new counts can't be linked.

Change your mind any time in Help → Share anonymous usage counts; Show exactly what would be sent shows the next send. Only the desktop app sends counts — the command line and npx apitestcenter ui never do.

Details, and the exact data: apitestcenter.com/privacy.

Something unclear or missing? Write to support@apitestcenter.com — the guide improves with every question.