Privacy.

What we store on your behalf

When you connect any network controller or device, Velanox polls it on the interval you set (default 60s) and persists time-series snapshots of devices, clients, VLANs, WiFi networks, and WAN status. Credentials for your controller are encrypted at rest with AES-256-CBC and only decrypted in-process when a poll runs.

VPN certificates generated by EasyRSA are stored with the same encryption envelope. Private keys for client .ovpn profiles are emailed once on issue and not retained server-side.

Hard boundaries between companies

Every database query is filtered by companyId. The requireCompanyUser middleware prevents global admins from reading company-scoped records via the API. White-label tenants do not share storage or background workers with each other.

What we keep about your users

For each user we store: email, name, bcrypt-hashed password (12 rounds), assigned roles, and last login timestamp. Refresh tokens are persisted in the database for the lifetime of the session (7 days) and revoked on sign-out.

Retention windows

Application logs retain request metadata (path, status, latency, anonymized IP) for 30 days for debugging and abuse mitigation. Time-series device metrics are pruned by the maintenance worker on a rolling window — the exact window is configurable per company.

Signed, unstored, replay-safe

If you register webhook endpoints, payloads leave Velanox and travel to your URL. We sign every payload with HMAC-SHA256 in the X-Velanox-Signature header. We do not retain webhook bodies after delivery is acknowledged.

Who else touches the data

Hosting and outbound mail are handled by infrastructure partners under standard data-processing agreements. We don't sell or share your data with advertising networks. There are no analytics trackers on this site.

Export, delete, ask

You can export or delete any company you own from the admin panel. Email privacy@velanox.nl for anything that page can't cover, including GDPR access requests.