Loading…
Loading…
Security camera footage is sensitive by definition - it can show your home, your business, your staff, your customers. Here's exactly what protects it, on the device, in the platform, and in how we run the company behind it.
Every Hub runs all of this by default - none of it is a paid add-on.
Footage, camera credentials, and accounts are stored on the Hub itself, on site. There's no mandatory cloud account and no NVRblink server your footage passes through by default. Cloud storage is an optional, clearly-labelled backup add-on, never the primary copy.
Camera passwords and other stored credentials are encrypted on disk, never held in plain text. Login passwords are hashed, never stored or transmitted in a recoverable form.
Face Recognition and Number Plate Recognition both run entirely on the Hub, using local neural network models. Footage and recognition data are never sent elsewhere to be processed.
Every login, setting change, and camera edit is written into a SHA-256 hash-chained audit trail. Alter a past entry and the chain breaks - built to make silent tampering detectable, not just logged after the fact.
Standard TOTP-based 2FA (Google Authenticator, Authy, and similar apps) for admin sign-in, with one-time recovery codes if a device is lost.
Repeated failed sign-ins lock an account out for a cooldown period. The Hub itself runs with fail2ban, a host firewall, an SSH on/off toggle, and automatic security updates - hardened from the moment it's plugged in, not something an installer has to remember to configure.
The Hub's second network port, with its own built-in DHCP, keeps every camera off a client's actual network entirely. No IP conflicts, nothing for their IT provider to worry about, and a compromised or misbehaving camera physically cannot reach anything else on site.
Remote access is off until it's deliberately turned on. When it's on, every device gets a free hostname so remote access survives an IP change, and the Hub can manage a genuine trusted HTTPS certificate via Let's Encrypt automatically if pointed at your own domain - or use a self-signed certificate with the apps pinning it on first connection, the same trust-on-first-use model SSH uses for host keys.
The same discipline applied to every account that can reach a device remotely.
Partners, staff, and field engineers each authenticate through entirely separate, isolated login systems - a compromised login in one never grants access to another. Partner and engineer accounts lock out after repeated failed attempts, the same as every other account on the platform.
Every API call is scoped to what the signed-in account actually owns - a reseller can only ever see their own clients, sites, and devices; an engineer only the sites they've been assigned. Accessing something outside that scope returns "not found," not an error that confirms it exists.
Remote engineer access to a live site is granted through a short-lived, single-use token tied to one verified session, not a shared password - a typical grant-to-verify round trip completes in around a second, and the credential is worthless the moment it's used.
Every login and password-reset endpoint on the platform is rate-limited per IP address, on top of the account-level lockout above - a real, tested defence against automated password guessing, not just a checkbox.
Partner details such as phone numbers, addresses and company numbers are encrypted at rest with AES-256-GCM, not stored as plain text, and staff access to them is logged.
NVRblink is a trading name of Creswick Media Ltd, a company registered in England and Wales, registered with the Information Commissioner's Office (ICO registration ZC157455). Development, hosting, and support are all handled in-house in the UK - nothing outsourced overseas.
This website runs no tracking cookies and no analytics pixels. What little is collected - a contact form submission, ordinary server logs - is exactly what it looks like, nothing more.
Account data can be reviewed, corrected, or deleted through self-service tools in the partner portal - you're never dependent on a support ticket to exercise a right you already have under UK GDPR.
We'd rather tell you plainly where a security model has a real limitation than oversell it - see the full breakdown on the apps page for exactly what mobile session storage does and doesn't protect against, for example.
Published to meet the UK Product Security and Telecommunications Infrastructure (PSTI) Act 2022 - the three things it requires every connectable product like the Hub to state publicly.
Every Hub generates its own random, unique local password at install time - there is no factory default and no password shared across devices. This is checked and reported per device (see the release notes for details); an installer or a partner engineer can retrieve a device's own password, but there's no single value that unlocks every Hub.
If you believe you've found a security vulnerability in the NVRblink Hub, the partner portal, or any of our apps, email [email protected] with what you found and how to reproduce it. We aim to acknowledge reports within 2 working days, and we won't take legal action against good-faith security research carried out in line with this policy. Every Hub also publishes this contact at /.well-known/security.txt (RFC 9116), machine-discoverable without needing to sign in first.
Every NVRblink Hub is supported with security updates for a minimum of 3 years from the date of activation, for as long as it remains connected and checking in - automatically, with no separate subscription required to keep receiving them. In practice the platform is updated far more often than the minimum: it's under active, continuous development.
Want the legal detail?
Read the full privacy policy, or get in touch if you have a specific question about how we handle data.