This policy describes what NetBase collects, why, and how it's stored. It's written in plain English because a privacy policy should be read, not skimmed. If something isn't covered here and you want it to be, [email protected] is the fastest way to ask.
What we collect
NetBase only collects what it needs to run the product. Broadly, this is three kinds of data:
- Account info. When you sign in, we store your name and email as provided by the identity provider (OIDC or email-and-password). We never ask for payment details — NetBase is free.
- Project data you type in. Everything you put into the editors — hostnames, interface IPs, VLAN names, routing configs, custom commands — lives in your project. Other members of the same project can read and edit it; nobody outside the project can.
- Device access credentials. If you connect a live device through a NetBase connector, the SSH username, password / private key, enable secret, and host-key fingerprint you enter are stored as part of the project and used only by that project's connectors to reach the device.
The connector also uploads per-device show running-config snapshots, interface counters,
and reachability state so the Fabric, Inventory, Device history, and Deploy review views can show
meaningful information.
While you're editing a project, NetBase also keeps a short-lived presence record (your display name, an anonymous client id, the tab / field you're currently focused on) so other members can see who's editing what. Presence data isn't retained after you disconnect.
What we don't collect
- No advertising trackers, no analytics pixels, no fingerprinting.
- No payment or billing data — NetBase is free.
- No access to devices behind a connector other than via the credentials you explicitly enter.
- No visibility into what you type into the editors while you're offline / not signed in (that never leaves your browser).
How we use it
Strictly to run the product: sign you in, sync your projects across devices, let teammates collaborate in real time, execute the deploys you ask for, and show you activity / history. We don't use any of it for marketing or profiling, and we don't sell it. If we ever add product analytics, it'll be opt-in and documented here.
Where it lives
The backend is Appwrite, which we self-host on infrastructure we control — not on Appwrite Cloud. The instance runs in Denmark (EU), so data is processed inside the EEA and subject to the GDPR. Everything above (account info, project data, device credentials, running-config snapshots, activity log) is stored in Appwrite tables with row-level permissions scoped to project members.
The NetBase console and this marketing site are served through Cloudflare. Like any CDN, Cloudflare sees request metadata (IP, user-agent, path) for delivery and DDoS protection; it never sees your project data, which flows directly between your browser and the self-hosted backend over TLS.
If you self-host NetBase, all of the above lives wherever you host it — this policy
only speaks for the hosted instance at console.netbaseapp.com.
Who we share it with
Only with the sub-processors that are needed to run the product. Today that's:
- Cloudflare — CDN and DDoS protection in front of the console and marketing site.
- The self-hosted Appwrite backend — operated by the NetBase team; holds auth, project data, realtime updates.
NetBase does not use advertising networks, analytics pixels, or data brokers. If the list above ever needs to change we'll update this page before the change takes effect.
We will disclose data if legally compelled (a valid subpoena or equivalent). We'll notify you unless the order prohibits us from doing so.
Retention
- Projects and their contents are kept for as long as the project exists. Delete the project (or ask us to) and everything in it is removed.
- Running-config snapshots uploaded by connectors are kept per device up to a configurable retention cap (default: the most recent 50 per device; older ones are pruned).
- Activity log rows are kept up to 200 per project, used to render the Dashboard feed.
- Presence is ephemeral — dropped as soon as you disconnect.
- Account info is kept while your account exists. Delete your account and we remove account-level data; project data you own goes with it.
Security
- All traffic between your browser, the connector, and NetBase uses TLS.
- Device credentials and project content are only readable by project members.
- Connector enrolment tokens are one-shot — once a connector uses one, it can't be reused to enrol a second connector.
-
The connector scrubs its own log output: passwords, SSH keys, enable secrets, and enrolment
tokens are replaced with
[redacted]before anything is written to disk.
No system is bulletproof. If we ever experience a security incident that affects you, we'll let you know without undue delay.
Your rights
You can access, export, correct, or delete the data NetBase holds about you at any time — either directly from the app (settings → delete account, Projects → delete) or by writing to [email protected]. If you're in the EU/EEA, UK, or another jurisdiction with similar data-protection laws, the usual statutory rights apply (access, rectification, erasure, restriction, objection, portability).
Cookies
NetBase uses only essential cookies — the ones that keep you signed in and remember your theme preference. There are no marketing or analytics cookies. The marketing site you're reading this on doesn't set any cookies at all.
Changes to this policy
We'll update this page when something material changes and bump the "Last updated" date at the top. Significant changes (new sub-processors, changes in how data is used) will also be announced via in-app notification or email before they take effect.
Contact
Questions, data requests, or complaints: [email protected].