Data Privacy and Storage

Data, Privacy and Storage

Getman is local-first. There are no accounts, no cloud sync, and no telemetry — nothing you do is uploaded anywhere.

The privacy model

• No account / login. You just open the app.
• No cloud. All data stays on your device.
• No telemetry / analytics. Getman doesn't phone home.
• Sharing is explicit — only via Postman export or the git workspace mirror, both of which you trigger. See Import Export and Git Workspace.

The only network traffic Getman makes is the HTTP/WebSocket/SSE requests you send.

What's stored locally

Everything persists in a fast embedded database (Hive). Roughly:

Data	Notes
Settings	All your Settings preferences
Tabs	Open request tabs (including the last response), restored on launch
History	Sent requests — History
Collections	Saved folders/requests + [[Collections
Environments	Variable sets — Environments and Variables
Cookies	The persistent [[Cookies
Request rules	Per-request [[Tests and Chaining

When things save

• Settings, collections, environments: immediately on change.
• Cookies / rules: on change.
• Tabs: a few seconds after you stop editing, and on close (so a crash loses at most the last few seconds).
• History: on each send.

Where the data lives

Getman stores its database in the per-application data directory your OS manages — you don't configure it. Broadly:

• macOS: under the app's Application Support / container directory.
• Windows: under your user AppData.
• Linux: under your XDG data home (e.g. ~/.local/share/…).
• Web: in the browser's storage (IndexedDB), scoped to the site origin.

Secrets

Environments and Variables are masked in the UI and on Postman export, but note they're stored in the local database like other values (the masking is about not shoehorning them into shared exports / shoulder-surfing, not at-rest encryption). The mTLS key passphrase in Settings is likewise stored as plain text locally. Treat your machine's user account as the security boundary.

Moving / backing up

Because it's all local, you can:

• Use the git workspace to version-control collections.
• Use Postman export to move collections/environments between installs.

(There's no single "export everything" button — history, cookies, and rules are intentionally machine-local.)

Web build caveats

The hosted web demo stores data per-browser (IndexedDB) and is subject to browser limits (CORS, no custom WebSocket headers). See FAQ and Troubleshooting.