Privacy, in plain English

Last updated 3 July 2026 · netmap is in private beta

netmap is a desktop app built and run by one person. This page says exactly what data netmap touches, why, and how to turn things off. There is no long legalese version hiding behind it — this is the policy.

01Account & licensing

What's stored: your email address, an optional name and @handle, your license keys, device IDs (an identifier for each computer you activate) and activation records (which machine activated, when). Why: it's how licensing works — issuing keys, counting seats, and letting you deactivate an old laptop yourself from the account page. It lives on netmap's license server and isn't shared with anyone else beyond the services that run netmap (hosting and email delivery).

02What the app reports (telemetry)

When the app checks in with the license server (periodically, when online), it includes the app version and platform (macOS or Windows) so I know which builds are actually in the field.

The app also keeps feature-usage counters — plain counts like "exports run: 14" — so I know which features earn their keep. Counters carry no show content.

If the app crashes, it sends a crash report: the stack trace, app version and platform. Never your show data.

Telemetry is on by default, and the switch to turn it off is in the app under Settings. License check-ins themselves are part of how paid licenses function and stay on while a license is active.

03Your device library & the community library

Device definitions you create in your library (make, model, rack units, ports, power, optional faceplate image) sync to netmap. Two reasons: they're the raw material the community equipment library grows from, and they tell me what gear people actually build with.

The boundaries, clearly:

• Synced items are visible to netmap (the operator) only. No other user sees them.
• Nothing is published to the community library unless you explicitly click "Submit to netmap library."
• Every submission is reviewed by a human before it's published.
• Credit by your @handle ("added by @you") is optional.
• You can turn library syncing off entirely in Settings.

04Published shows

Publishing only happens when you hit Publish. It puts a read-only copy of the paperwork you selected at a public link — optionally gated behind a PIN you set. Links expire after 14 days by default and you can extend them from the app. netmap counts views and last-opened time for each published show and shows those numbers back to you. You can take a published show down at any time.

05This website

The beta signup form collects your name, email and whatever you type into the optional fields, and it's used to contact you about the beta — that's it. It's stored with our email provider and on netmap's own signup list. Visits are counted with Cloudflare's cookieless analytics; beyond that the site loads no third-party scripts and no trackers.

06Payments

When paid plans go live, checkout runs through our payment partner — a merchant of record that acts as the seller for the transaction and handles cards, tax and invoices. netmap receives your email and what you bought. netmap never sees your card number.

07Your data, your exports

Shows are local .json files on your machine — export them, back them up, or walk away with them at any time. Want your account data deleted? Email [email protected] and it's gone (your licenses go with it).

08Who actually touches the data

netmap runs on a small, boring stack, and these vendors process data only to run the service: Railway (application hosting, US), Cloudflare (DNS, edge network, site hosting, cookieless visit counting), and Resend (transactional email). When paid plans go live, a merchant-of-record payment partner is added for checkout. That's the whole list — netmap doesn't sell or rent data to anyone, ever.

09How long things are kept

• Account & license records: while your account exists, plus a short wind-down after deletion requests.
• Crash reports: a rolling window — old reports are automatically overwritten by new ones.
• Published shows: until their link expires or you delete them, whichever comes first.
• Library sync reports: kept while they're useful for growing the catalog; never published.
• Beta signups: until you're invited, ask off the list, or the beta ends.

10Security

Everything moves over TLS. Admin surfaces sit behind two-factor access controls plus passwords. License checks are signed cryptographically. One person (the operator) has access to production data. If a breach ever affects your data, you'll hear about it directly and promptly.

11Cookies & local storage

The site runs no third-party trackers and sets no analytics cookies. Visits are counted with Cloudflare's cookieless Web Analytics — no cookies, no fingerprinting, no cross-site tracking. The account page keeps your sign-in token in your browser's local storage; PIN-protected publish links set one cookie so you don't retype the PIN per page. That's the complete list.

12Where data lives & who netmap is for

netmap's servers are hosted in the United States; using netmap means your account data is processed there. netmap is a professional tool for working crew and designers — it isn't directed at children, and you shouldn't use it if you're under 16.

13If the law comes knocking

Data gets disclosed only if legally required — and if that ever happens, you'll be told unless the law forbids it.

14Changes & contact

This policy will evolve with the beta. Changes get posted here with a fresh date at the top; material changes get flagged on the site. Questions, complaints, deletion requests: [email protected].