Privacy policy
Last updated 28 October 2026. Effective the same day.
netamp is made by Netamp, Inc. This policy says what we collect when you use the netamp app, the netamp.io site and the services behind them, why we collect it, where it is kept, and what you can do about it.
The short version
- Your device logins, host keys, watchers, checks and playbooks are sealed on your computer with keys made from your password. On Pro we store sealed copies so they follow you between computers. We hold no key that opens them.
- Device output, the commands you type, captures, run results and monitor readings stay on your computer. The app does not send them to us. The one exception is what you choose to put in a bug report.
- We keep what an account needs to work: your name, your email, a sign-in key derived from your password, your subscription status, and the name of each computer you sign in from.
- No ads, no tracking, no selling of data. The app has no analytics, and the site sets no cookies of its own.
- You can delete your account from inside the app. Your synced vault is deleted from our servers at once.
1. Who we are
Netamp, Inc. is a Delaware corporation with its office at 800 Third Avenue FRNT A #1361, New York, NY 10022, United States. We are the data controller for the personal data described here. For data that belongs to a team, such as its seats, its work vaults and what its company login sends us, the controller is the company that pays for the team, and we process that data for them under our data processing agreement, which a company can ask for at support@netamp.io. You can reach us at support@netamp.io.
2. What this policy covers
This policy covers:
- the netamp app for macOS and Windows,
- the netamp.io site, including the documentation at netamp.io/docs,
- the services the app talks to: sign-in, vault sync, the terminal sharing relay, billing, bug reports and update checks.
It does not cover the devices and networks you connect to with netamp. Those belong to you or your employer. It also does not cover other companies' services that you choose to use alongside netamp, such as the AI service behind your own coding agent (see section 5) or the webhook endpoints you point a playbook at.
3. What we collect, and why
Below is every kind of data that reaches us, grouped by what you were doing when it did. For each one we say why we need it and, for readers in the EEA, the United Kingdom and Switzerland, the legal basis we rely on.
3.1 Your account
When you create an account we store:
- Your name and email address. The name shows on your account and to people you share a terminal with. The email is your sign-in and where we send the confirmation link.
- A sign-in key. The app derives it from your password on your computer with a slow, one-way key derivation. The app does not send your password itself, and the derivation is designed so that what we hold cannot be turned back into it.
- Your vault's account record. A random salt, the key-derivation settings, your account's public key, and your account's private key sealed twice: once under a key made from your password, and once under a key made from your recovery code. We hold no key that opens either copy.
- Whether you confirmed your email, and the time of your last sign-in.
Your recovery code is shown once, on your computer, and the app does not send it to us. Nobody at netamp can reset your password or your vault.
If you put other people's details into netamp, for example a colleague's email when you share a terminal, or credentials your organisation issued to you, you are responsible for having the right to do so.
Why: to run your account and keep your vault yours. Basis: performance of our contract with you.
3.2 The computers you sign in from
Each time you sign in, and in the background while the app runs, it records the computer it is running on: the computer's hostname as set in your operating system, a one-way hash of a hardware identifier, and the time it was last seen. We use this to tie your account to the computers that hold a copy of your vault and to spot misuse. On Pro, we also use it to keep Pro to two computers at a time. When a new computer signs in, we email a 6 digit code to your account address and record when the computer was confirmed. We keep only a one-way hash of the code, and it stops working after a short time. Deleting your account removes these records.
Why: to run your account and protect it. Basis: performance of our contract with you, and our legitimate interest in keeping the service secure.
3.3 Vault sync (Pro)
On a Pro plan, your vault syncs between the computers you sign in on. What syncs is sealed on your computer before it is uploaded, with keys that only your password can unlock. The sealed records hold your devices, your SSH profiles and their passwords, keys and one-time-code secrets, your known host keys, your watchers, checks and aliases, your playbooks, your saved check runs, your scripts, your sidebar folders and your workspace list. We store these sealed records so that your other computers can download them. The design gives us no key to open them.
When you delete a device, folder, check or playbook, we keep its sealed record for 14 days so you can restore it from Settings › Vault › Deleted items. After 14 days it is removed.
Some things about a synced vault are visible to us in the clear:
- The identifier of each record. Identifiers are built from the kind of record and its id. For some kinds that id carries meaning: a host key's identifier is the device address and port it belongs to, a folder's identifier is the folder's name, and a playbook's identifier is the playbook's name. Device records carry an opaque id.
- Sizes, content hashes, sequence numbers and timestamps for each record, whether it was deleted, and which of your computers deleted it.
- The total size of your synced vault. We cap the size of a synced vault, and the app tells you when it is full.
We use record identifiers only to run sync. They exist so that the app can tell which records changed. If the names of your folders or the addresses of your devices are themselves sensitive, keep that workspace local to one computer and it will not sync.
Why: to deliver sync, which you bought. Basis: performance of our contract with you.
3.4 Your subscription
Payments are handled by Stripe. When you upgrade, the app opens Stripe Checkout in your browser. You enter your card and billing details there. They go to Stripe and never pass through netamp. Stripe acts as the merchant of record for netamp Pro, so Stripe's own privacy policy applies to what you give it at checkout and on its billing page.
What we store about your subscription is:
- your Stripe customer id and subscription id,
- your plan, its status, the start and end of the current billing period, and whether you asked to cancel at the end of it.
When you open Settings › Plan, the app asks Stripe for your card's brand and last four digits so it can show them. We do not store them. We send Stripe your account id and your email so it can match the payment to you.
Why: to know what your account is entitled to, and to keep the records tax law requires. Basis: performance of our contract with you, and our legal obligations.
3.5 Terminal sharing (Pro)
When you share a terminal, your computer and your guests' computers connect to our relay. Everything you share is encrypted on your computer with a key that lives only in the invite link, after the #. The relay forwards sealed frames. It is designed so that neither the relay nor anyone at netamp holds the key to open them.
What the relay and our database do see:
- the account id and email of the host and of each guest,
- the invite code, when it expires (24 hours), and how many people it admits (up to 5),
- who asked to join, when, and whether the host approved,
- the kind of each message (typing, a request to type, a request to resync, the end of the session), with no content,
- how much traffic passed and when.
The relay is designed not to store what you share. It keeps the list of who is in a room only while the room is open. The invite and join-request rows stay in our database until you delete your account.
Why: to deliver sharing, which you bought. Basis: performance of our contract with you.
3.6 Bug reports
Nothing is sent unless you press Send on the Report a bug page. A report contains what you type (a title and a description), the kind of report, your app version and build, a line describing your operating system, processor and memory, the name of the screen you were on, how many devices your workspace holds, the most recent part of the app's log, and your account id and email. You can attach a few pictures. After a crash you can also attach a crash dump, and the switch for it is on by default when a dump exists.
The app tries to remove passwords, keys and other secrets from each line before it is written to the log, and again before the log is sent. It does this by recognising patterns, so it can miss a secret that does not look like one, and it does not remove device names, addresses or the paths of files on your computer. Treat the log as something we will read, and look at it before you send it. Pictures and crash dumps are sent exactly as they are, and a crash dump can contain whatever was in the app's memory at the time, including device output. Crop pictures, and turn the dump off, if they would show something you do not want us to see. By pressing Send you confirm that you have checked the report and are allowed to send us what it contains.
If a secret does reach us in a report, write to us at once. We will delete the report and we will not use the secret. You should also change that secret, since it has left your control.
Bug reports are deleted 90 days after they arrive, along with their files. Deleting your account does not shorten that. Write to us if you want a report removed sooner.
Why: to fix the problem you reported. Basis: your consent, which you give by pressing Send and can withdraw by asking us to delete the report.
3.7 Update checks
Five seconds after it starts, and when you click Check now in Settings, the app asks our update feed whether a newer version exists. That request carries the version you have, your operating system, and a random identifier that the updater created when netamp was installed. It carries nothing about your account. The feed is served by Cloudflare, which keeps short-lived request logs (see 3.10). There is no setting to turn the check off.
Why: to keep you on a current, supported build. Basis: our legitimate interest in shipping fixes, including security fixes.
3.8 Email
We send one email when you create an account: the confirmation link, from no-reply@netamp.io. Its images are served from assets.netamp.io, so when your mail client loads them Cloudflare sees that request. Stripe sends its own receipts, renewal notices and failed-payment notices for your subscription.
When you write to support@netamp.io we keep the conversation for as long as we need it to help you, and for up to two years after, so we can pick it up again if the same thing comes back. Our mail runs on Google Workspace.
Why: to confirm your address, and to answer you. Basis: performance of our contract with you, and our legitimate interest in giving support.
3.9 The website
netamp.io has no analytics, no advertising, no tracking pixels and no third-party scripts. We set no cookies. The documentation page remembers your light or dark choice in your browser's local storage, which never leaves your browser. Fonts are served from our own site.
The site is served by Cloudflare. Cloudflare keeps short-lived logs of each request (your IP address, the page you asked for, your browser's user agent, and timing) to run and protect the site, and may set a cookie needed for security. While the site is in preview it asks for a password; your browser sends that password with each request and we do not store it.
Why: to serve the site and keep it up. Basis: our legitimate interest in running a website.
3.10 Service logs
Our services run on Cloudflare Workers. Cloudflare records each request's URL, status, timing and any error message our code prints, and keeps those records for a short period, currently up to seven days. Our code does not log request bodies. One request made before you sign in carries your email address in its URL and so appears in those logs.
Company sign-ins (see 3.13) are logged with only the provider, the email domain and the outcome. Calls from a company's provider for automatic removal are logged with only the team, the action and the outcome. We do not log a sign-in's contents, a token, an email address or a request body for either.
Your IP address is used briefly to limit how often an address can try to create an account. It is not stored for that. Our sign-in provider, Supabase, keeps its own security log of sign-in events, which includes the IP address of each attempt.
Why: to run the services, find faults and stop abuse. Basis: our legitimate interest in a reliable, secure service.
3.11 Operators
A small number of people at netamp can open an internal operations page. It shows each account's email, plan, status, how many computers it signs in from, when it signed up and last signed in, and its bug reports. Access needs a named operator sign-in. Changes an operator makes are written to an append-only audit log with the operator's email. Operators have no key to your vault or your shared terminals, and no access to your computer.
3.12 Teams and work vaults
When a company buys a team plan, each engineer with a seat gets a work vault. A work vault holds the same kinds of sealed records as a synced vault (see 3.3). It belongs to the company. For a team we also store its name, its seats, and each member's email and whether they are an admin.
The app gives a team admin no way to open, look at or take over an engineer's work vault. The key to each work vault is also sealed to a team key that the team's admins hold. The team key exists so an admin can reset an engineer's forgotten vault password. During a reset, the admin's app handles that vault's key. Each time an admin resets a vault password, the engineer and every admin get an email.
When an engineer's seat is removed, the app deletes their work vault from their computers the next time they are online. The synced copy stays with the team, under its admins, and we delete it 30 days after the team's plan ends.
We hold no key that opens any vault, a work vault or your own. The team key is made on an admin's computer. We store its public half, and copies of its private half sealed to each admin, which we cannot open.
Sessions, captures, terminal logs and run results never go into a vault. They stay on the engineer's computer, as section 4 describes, and neither the company nor netamp receives them.
Why: to run the team plan the company bought. For this data the company is the controller (see section 1).
3.13 Teams and company login
A team can connect its own identity provider, such as Okta, Microsoft Entra ID or Google Workspace, so that its engineers sign in with their company login. Each time an engineer signs in this way, the company's provider sends us their email address, their name, the provider's own id for them, and the time they signed in. We never see their company password.
A company that uses Okta or Microsoft can also turn on automatic removal (SCIM). The provider then tells us whether each engineer is still active. When it marks someone inactive or deletes them, we remove their seat, sign them out of netamp, and their work vault stays with the team, as 3.12 describes.
To run company login we store:
- the provider's public signing certificate, its sign-in address and its Entity ID,
- the email domains the company proved it owns with a DNS record,
- which provider each engineer signs in with, and the provider's id for them,
- for automatic removal, a one-way hash of the token the provider uses, and when it last used it,
- for a test sign-in an admin runs, the email address it signed in with.
A company login only signs the engineer in. Their vault still opens with a separate vault password that stays on their computer, so neither the company's provider nor we can open it.
Why: to run the team plan the company bought. For this data the company is the controller (see section 1).
4. What never leaves your computer
netamp is a desktop app, and most of what it handles stays in the workspace folder on your disk. The app does not send any of the following to us, unless you put it in a bug report yourself:
- the output of your devices, and the commands you type,
- terminal captures and recordings,
- watcher tables, check results and saved run records, including every device's output from a run,
- monitor readings, ping samples and ARP or MAC imports,
- playbook versions and run history,
- anything in a shell on your own computer.
SSH, Telnet and serial traffic goes straight from your computer to your devices. It passes through netamp's servers only when you share a terminal, and then only sealed.
Two things about your disk are worth knowing. The app stores device passwords, keys and secrets encrypted, but it stores captures, run output and watcher tables in plain files in your workspace folder. And terminal logging is on by default in a new workspace, so whatever is printed in a session to a device, including anything you typed at a prompt, is written to a capture file. Protect your disk the way you would protect any file with network data on it, and turn logging off in Settings › Terminal if you do not want captures.
5. Agents over MCP
On Pro, you can let your own coding agent (Claude Code, Codex, Cursor or another MCP client) drive netamp on your computer. The agent connects over a local socket that only your user account can open. It is off by default, each agent must be approved by you when it asks to connect, and you choose which devices it may reach.
What that agent reads from netamp, including device names, addresses, and device output, goes to the agent and from there to whichever AI service the agent uses. The app tries to remove secrets from what it hands the agent, by the same pattern matching described in 3.6, and can miss one. None of it goes to netamp. That company's privacy policy and terms apply to it. We cannot see, store or delete it, and we are not responsible for what that service does with it.
The netamp app we ship has no AI feature of its own and sends nothing to any AI service. If we ever add one, we will update this policy before it sends a byte, and say exactly what goes where.
6. Who we share data with
We do not sell personal data, and we do not share it for advertising. We share it only with the companies that run parts of the service for us, each under a contract that limits what they may do with it.
| Company | What it does for us | What it holds |
|---|---|---|
| Cloudflare, Inc. | Runs our services, stores sealed vault records and bug-report files, relays shared terminals, serves the site and the update feed, sends the confirmation email. | Everything in transit, sealed vault records, bug reports, request logs. |
| Supabase, Inc. | Our database and sign-in provider. | Account, machine, subscription, sharing and bug-report records; sign-in logs. |
| Stripe, Inc. | Payments, invoices, tax and refunds, as merchant of record for netamp Pro. | Your card and billing details, your email, your account id, your invoices. |
| Google LLC | Google Workspace, for the support@netamp.io mailbox. | Emails you send us. |
We may also disclose personal data:
- when the law requires it, for example to answer a valid court order, after telling you where we are allowed to,
- to protect netamp, our users or the public from fraud, abuse or harm,
- to a buyer or successor if netamp is sold, merged or reorganised, in which case this policy continues to apply to the data transferred and we will tell you where we can before any change to it.
When a team admin invites you, they give us your email address (see 3.12). If your team uses company login, your company's identity provider also sends us the details in 3.13. That is the only personal data about you we receive from anyone else. We make no automated decisions about you that have legal or similarly significant effects, and we do no profiling.
7. Where your data is kept
We are a United States company and your data is processed and stored in the United States. Cloudflare stores and serves data from its global network.
If you are in the EEA, the United Kingdom or Switzerland, this means your data leaves your region. Where the law requires a transfer mechanism, we rely on the standard contractual clauses approved by the European Commission, with the UK addendum where it applies, or on another mechanism the law recognises, through the data processing terms of the companies above. The strongest protection, though, is that the data that matters most, your device credentials and your network's configuration, is sealed before it leaves your computer and is not designed to be readable anywhere it is stored. We have not appointed an EU or UK representative or a data protection officer; write to the address in section 13.
8. How long we keep it
| Data | Kept until |
|---|---|
| Account, name, email, sign-in key, vault account record | You delete your account. |
| Synced vault records | You delete the synced vault in Settings › Vault, or delete your account. If your Pro subscription ends, sync stops and the sealed copy stays readable to you. We may remove a synced vault that has been unpaid for 30 days, and we will say so in the app first. |
| Deleted vault records | 14 days after you delete them, then removed. Deleting your synced vault or your account removes them at once. |
| A removed seat's synced vault, on a team without work vaults | 30 days after the seat is removed, then deleted. |
| A removed seat's synced work vault | Kept by the team, under its admins, until 30 days after the team's plan ends, then deleted. |
| A team's synced work vaults | 30 days after the team's plan ends, then deleted. |
| The identity provider's id for an engineer, and which provider they sign in with | 30 days after their seat is removed, or when the team is deleted. |
| A company login's provider record (its kind, Entity ID and certificate) | Kept, marked removed once the company removes it, so the engineers who signed in with it can still move their vault to a password account. |
| The email domains a team proved | The team is deleted. |
| Automatic removal tokens (a one-way hash, and when each was last used) | The team is deleted. A replaced or revoked token stops working at once. |
| The email address of a test sign-in | 30 days after the test ran out, then deleted. |
| The record of a vault moved to company login (the account ids it moved between) | Kept. A move that was started and not finished is deleted after a day. |
| Logs of automatic removal calls (team, action and outcome only) | Up to seven days, in Cloudflare's request logs. |
| Records of the computers you sign in from | You delete your account. |
| Subscription record | You delete your account. Stripe keeps invoices and payment records for as long as tax law requires. |
| Sharing invites and join requests | You delete your account. Invites expire after 24 hours and cannot be used after that. |
| Bug reports and their files | 90 days after they arrive, then deleted automatically. Ask us to delete one sooner. |
| Service counters (request counts, bytes, with no content and no name or email) | May be kept after account deletion, keyed only by an account id, for accounting. |
| Operator audit log entries that mention your account | Kept, as an append-only record of what operators did. |
| Cloudflare request logs | Up to seven days. |
| Support email | Up to two years after the conversation ends. |
Deleting your account takes effect at once and cannot be undone. The app cancels any Pro subscription, deletes your synced vault, deletes your sign-in, and the database removes your account, machine, subscription and sharing records with it. Copies in backups and logs are removed when those age out, within the periods above. Your workspaces stay on your computer.
We may keep data longer than the table says where the law requires it, for example for tax records or to answer a legal demand, or where we need it to establish or defend a legal claim.
9. Security
How we protect what we hold:
- Your password stays on your computer. The app derives two keys from it. One signs you in. The other unlocks your vault and is designed never to leave the app's memory.
- Vault records are sealed with authenticated encryption under keys that descend from your password through your account's keypair. We hold only sealed copies and a public key.
- Shared terminals are sealed end to end. The key is in the invite link and is designed never to be uploaded.
- Every connection uses TLS. Your sign-in tokens are stored on your computer encrypted, with the key in your operating system's keychain or credential manager.
- Our services check your identity on every request, and deleting your account needs a fresh sign-in.
The limits, stated plainly:
- No system is perfectly secure. We cannot promise that our services, our providers or your copy of the app will never be breached, and we cannot promise that a bug will never do something this policy says the app does not do. If we learn of a breach that affects your data, we will tell you and any authority the law requires, without undue delay.
- Record identifiers in a synced vault are not sealed (see 3.3).
- Your own disk is not encrypted by netamp, except for stored secrets (see section 4). What happens on your computer, including malware, a shared login or a lost laptop, is outside our control.
- The secret removal in bug reports and agent replies works by pattern and can miss a secret.
- Nobody can reset your password. If you lose it and your recovery code, your synced vault cannot be opened by anyone, including us.
If you believe you have found a security problem in netamp, write to support@netamp.io. We will answer. We will not take legal action against someone who reports in good faith, keeps to their own accounts and data, does not disrupt the service, and gives us reasonable time to fix the problem before telling anyone else.
10. Your rights and choices
In the app
- Change your name in Settings › Account.
- Delete your account in Settings › Account. It takes effect at once.
- Delete your synced vault without deleting your account, in Settings › Vault.
- Cancel Pro from Settings › Plan › Manage plan, which opens Stripe's billing page.
- Choose what goes in a bug report before you send it, including whether a crash dump goes with it.
- Keep a workspace on one computer so that nothing in it syncs, and turn off terminal logging in Settings › Terminal.
- End a shared session or remove a guest at any time from the Sharing pill.
By writing to us
Wherever you live, you can ask us for a copy of the personal data we hold about you, ask us to correct it, ask us to delete it, ask us to restrict or stop a particular use of it, object to processing based on our legitimate interests, withdraw consent you gave, or ask for your data in a portable form. Write to support@netamp.io. We will confirm who you are, usually by asking you to write from the email on your account, and answer within the time the law where you live allows, which is usually 30 to 45 days. We may refuse or limit a request where the law allows, for example where we cannot verify who you are, and we will say why. We will not treat you differently for exercising a right.
Note that most of what netamp holds about you is already on your computer or sealed with a key only you hold. A copy of your sealed vault is of no use outside the app, and your workspace folder is yours to copy as you like.
If you are in the EEA, the United Kingdom or Switzerland
The rights above are the ones the GDPR and the UK GDPR give you. You also have the right to complain to your data protection authority. We would rather hear from you first, but you do not have to.
If you are in California or another US state with a privacy law
You have the right to know what we collect, to delete it, to correct it, and not to be discriminated against for asking. We do not sell personal data, do not share it for cross-context behavioural advertising, and do not use it for profiling with legal or similarly significant effects, so there is nothing to opt out of. Your sign-in details count as sensitive personal information under California law; we use them only to sign you in and never to infer anything about you. You can use an authorised agent to make a request; we will ask the agent for proof that you authorised it. We treat a Global Privacy Control signal from your browser as an opt-out of sale and sharing, and since we do neither, nothing changes. In the last 12 months we collected the categories of personal information listed in section 3, for the purposes given there, and disclosed them only to the providers in section 6.
11. Children
netamp is a tool for working network engineers. It is not for anyone under 18, and we do not knowingly collect data from anyone under 18. If you think a child has created an account, write to us and we will delete it.
12. Changes to this policy
When we change this policy we post the new version here with a new date at the top. If a change matters, for example a new kind of data we collect or a new company we share it with, we will also tell you in the app's What's New or by email before it takes effect. The version on this page is the one in force. This policy describes the app as we ship it; a feature that is switched off in the shipped app collects nothing.
13. Contact
Netamp, Inc.
800 Third Avenue FRNT A #1361
New York, NY 10022
United States
support@netamp.io