Privacy Policy

1. Who we are

NVRblink is a trading name of Creswick Media Ltd, a company registered in England and Wales (Company No. 16680472), registered office Great North Business Centre, 82 Great North Road, Hatfield, England, AL9 5BL, United Kingdom. Creswick Media Ltd is registered with the UK Information Commissioner’s Office (ICO), registration number ZC157455.

You can contact us about privacy at [email protected].

2. Our role: controller or processor

NVRblink is supplied to installers, integrators and security companies (“partners”), who set it up for their own clients. We do not sell to consumers. Who is responsible for personal data depends on whose data it is:

• •We are the controller of the personal data we collect for our own purposes: visitors to this website, partner accounts and their team members and engineers, billing and support records, and the security of our services.
• •The partner (and, for video and face or plate data, the partner’s client that owns the site) is the controller, and we are the partner’s processor, for personal data that they put into or process through NVRblink about other people. Examples: a partner’s clients and sites, the location and work records of a partner’s field engineers, photos, signatures and customer names captured on jobs, and the video, faces and number plates that a client’s own NVRblink Hub records. We handle that data only on the partner’s instructions, under the data processing terms in our Terms of Use.
• •If you are one of those people (for example a partner’s engineer, or someone recorded by a partner’s client’s camera) and want to use your rights, please contact the partner first. We will help them respond.

3. This website

• •Contact form: the name, email address and message you send, so we can reply. Kept only as long as needed to deal with your enquiry.
• •Server logs: our hosting infrastructure keeps basic technical logs (such as IP address, requested page and time) for security and troubleshooting.
• •Cookies: we do not use advertising or analytics cookies. When you sign in to the partner portal we set a session cookie that is strictly necessary to keep you signed in. Our website and portal are protected by Cloudflare, which may set security cookies. If you pay through embedded checkout, Revolut may set its own cookies for fraud prevention.

4. Cloud Storage and Hostname

A partner can switch on two optional services for a client’s site. Both are off unless switched on.

• •Cloud Storage: we hold the recordings the Hub uploads (stored with our storage provider, Bunny.net) and how much space is used.
• •Hostname: we hold the DNS record that points the chosen address at the site’s IP address (managed through Cloudflare).

The partner is the controller of this data and we process it for them (see “Our role” above).

5. Partner accounts

For partner (business) accounts we hold, as controller:

• •the company’s name, contact details, address, phone number, company and VAT numbers, and the people who have logins for the partner’s account (name, email, role, sign-in and security records);
• •the partner’s subscriptions, licences, orders, invoices, pricing and support tickets, and the state of each connected Hub (see below). Card payments are taken by Revolut (Revolut Merchant); we never see or store full card details (Revolut handles and stores payment details) and keep only the Revolut customer, subscription and invoice references;
• •records of what staff do in the portal (an audit log) so we can keep the service secure.

Information a partner records about its own clients (client names, contacts, site addresses, tickets, notes, equipment lists and floor plans) is held as the partner’s processor.

We send release emails about new NVRblink releases to the main contact on each partner account. Every one includes an unsubscribe link, and unsubscribing stops release emails only, not account, ticket or order emails.

6. The NVRblink Installer app (field engineers)

The NVRblink Installer app (Android and iOS) is used by a partner’s field engineers. The partner creates and removes engineer accounts; the app has no sign-up. The partner is the controller of the engineers’ data and the data about the partner’s customers, and we process it for them. What the app handles:

• •Sign-in: the engineer’s email and password, sent to our server (api.nvrblink.co.uk) to sign in. If the engineer turns on Face ID or fingerprint sign-in, the phone’s own security does the check and NVRblink never receives your biometric data; the app keeps the saved password locked behind that check.
• •Location: see the next section.
• •Work records: jobs and tickets assigned to the engineer, the times they travel, arrive and finish, answers to forms the partner has set up, and the customer’s name, signature, rating and comments if the partner uses the customer sign-off form.
• •Photos and video: taken with the phone’s camera (and the microphone, on iOS, for video) for job records and forms. The app asks permission first.
• •Time and money: time clock and time sheets, holidays, expenses (including a photo of the receipt), fleet mileage, and van stock and materials used on jobs.
• •Sites: site details and notes; when the engineer connects to a customer’s NVR, that NVR’s live cameras, playback and settings, shown on the phone.
• •Stored on the phone: the sign-in session, and a small queue of location points waiting to be sent. There are no analytics, advertising or crash-reporting tools in the app, and no advertising or device identifiers.

The app talks only to our server (api.nvrblink.co.uk), to secure upload links that our server issues for photos, signatures and attachments, and to the customer NVR the engineer chooses to connect to. It sends nothing anywhere else.

7. Location data

The NVRblink Installer app can share the engineer’s location with their employer (the partner) so the partner’s scheduling team can see where engineers are and send the nearest one to an urgent job. We built it to collect as little as possible:

• •When: only while the engineer is clocked in, or while a job assigned to them is travelling or on site. Our server tells the app when it may share, and the app stops when the engineer clocks out, when the job ends, and when they sign out. Outside those times nothing is collected.
• •Background use: while it is sharing, the app can keep sending location when it is in the background, so the partner can see where the engineer is. On Android a “location sharing is on” notification is always showing; on iOS the system location indicator and an in-app banner show. The app asks permission and shows an explanation before it collects anything.
• •What is collected: latitude, longitude, accuracy and the time, about every five minutes. Points are queued on the phone if there is no signal, and points older than three days are dropped before sending.
• •Who sees it: the partner’s own managers and scheduling users, on their live board and map. Other partners and other engineers cannot see it. We use it only to provide the service.
• •How long we keep it: location points are deleted automatically after 30 days. Deleting an engineer’s account also deletes their location history.

Engineers can decline or withdraw location permission in their phone’s settings. Partners are responsible for having a lawful basis, telling their staff, and keeping it proportionate; see the Terms of Use.

8. The NVRblink Mobile app

NVRblink Mobile (Android and iOS) lets you watch cameras and recordings on your own NVRblink system. It connects directly to your own NVR or Hub; it does not send your video, credentials or settings to us, and it does not contact our servers.

• •On the phone: the connections you save (a name, address, port and username), your sign-in session, and your grid layout. On Android the session is encrypted with a key held in the Android Keystore.
• •Permissions: network access only. On Android 9 and earlier it can save downloaded clips to your device. It does not ask for location, camera, microphone, contacts or notifications.
• •No accounts: you sign in to an existing user on your own NVR. There is no account to create or delete in the app. “Reset App” in Settings removes all saved connections and logins from the phone.
• •No analytics, advertising or crash-reporting tools, and no advertising or device identifiers.

Because home and business NVRs use self-signed security certificates, the app trusts a system’s certificate the first time you connect and then remembers it (“pins” it), and warns you if it changes.

9. The NVRblink Hub

Video, still images, faces and number plates handled by a Hub or the NVRblink Viewer are stored on the client’s own equipment. We do not receive them unless Cloud Storage is switched on. What the Hub does send to us:

• •Licence and status check-ins: the licence number and status, software version, uptime, storage, CPU and memory use, and, for each camera, its name and whether it is online. This is what shows a partner whether a site is running.
• •Remote settings: a partner can send changes to a Hub through our portal. Our server passes the command and the Hub’s reply.
• •Support bundles: logs the client or partner chooses to send us for support.
• •Email relay: a Hub can send email (two-factor codes, alerts, health reports, and motion snapshots if enabled) through our mail server. The content passes through to the recipient; we do not keep it beyond normal delivery and mail-server logs.
• •Hostname: the site’s public IP address, kept up to date so its chosen hostname keeps working, if the Hostname service is used.

The Windows apps and tools that check for updates on start-up (the Partner Toolkit and Employee Enrolment) fetch a small file from nvrblink.co.uk; our server logs record the request like any web request.

10. Employee Enrolment (faces, vehicles and HR requests)

Employee Enrolment is a Windows app used by a partner’s client to enrol employees for face recognition, register employees’ and visitors’ vehicles, and manage staff data requests. It handles biometric data (face photos and templates), which is special category data under UK GDPR. It needs a licence for the client, so it contacts our server to check the licence is active. That check sends only the licence and installation identifiers, and never any enrolled person’s data.

• •The data is encrypted on the client’s PC and shared only with the client’s own NVRblink Hub on their network. It is not sent to us, and we cannot see it.
• •The client (usually the employer) is the controller and decides the lawful basis, records each person’s consent, and sets retention. Deleting a person in the app removes them from the Hub.
• •Clients and partners who use face recognition or number-plate recognition must meet their own legal obligations, including a data protection impact assessment and clear notices. See the Terms of Use.

11. Why we use personal data, and our legal bases

12. Who we share data with

We do not sell personal data. We use a small number of service providers (processors) to run NVRblink. They may only use the data to provide their service to us:

• •Revolut Ltd (Revolut Business) - card payments and subscriptions.
• •Bunny.net - storage for Cloud Storage recordings, and for uploaded photos, signatures and attachments.
• •Cloudflare - DNS, security and delivery for our websites, and DNS records for the Hostname service.
• •Our hosting and email infrastructure, and our accounting software (for invoices).
• •Apple and Google distribute the mobile apps to you. They do not receive data from us.

We may also disclose data if the law requires it, or to protect our rights, our users or the security of the service.

Some of these providers process data outside the UK. Where they do, we rely on an adequacy decision or on the UK’s approved safeguards (such as the international data transfer agreement or the UK addendum to standard contractual clauses).

13. How long we keep data

14. How we protect data

• •All traffic between apps, browsers and our servers uses HTTPS.
• •Passwords are stored only as strong one-way hashes (Argon2id). Two-factor authentication is required for the partners portal.
• •Sensitive fields in our database (such as phone numbers, addresses and company numbers) are encrypted, and staff access is logged.
• •The NVRblink Installer app keeps its sign-in session in the platform’s secure storage (encrypted preferences on Android, the Keychain on iOS). NVRblink Mobile keeps its sign-in session in encrypted storage on Android.
• •Recordings and other client content stay on the client’s own equipment unless Cloud Storage is switched on.
• •Every Hub generates its own random, unique local password at install - there is no shared factory default. It receives security updates automatically for a minimum of 3 years from activation, and we welcome vulnerability reports at [email protected]; see the full policy on the Security page.

No system is perfectly secure. If a breach affects personal data, we will tell the affected controller and, where required, the ICO without undue delay.

15. Your rights

Under UK GDPR you can ask to see the personal data we hold about you, correct it, have it deleted, restrict or object to how it is used, receive a copy in a portable form, and withdraw consent where we rely on it. For anything you would like to ask, email [email protected].

If your data is held by us on behalf of a partner or customer (for example you are a partner’s engineer, or were recorded by a partner’s client’s camera), please contact them; we will help them respond. You also have the right to complain to the ICO at ico.org.uk.

16. Deleting your account and data

• •Partner engineers using the NVRblink Installer app: your account is created and removed by your employer (the partner). Ask them to delete it, or email us and we will pass your request to them. Deleting the account also deletes your location history.
• •Partner accounts: email [email protected] to close the account and delete the data we hold for it, including any Cloud Storage recordings.
• •NVRblink Mobile: there is no account with us. Use “Reset App” in Settings to remove everything the app stores on your phone.

When we delete data we may keep the minimum needed by law (for example invoices).

17. Children

NVRblink is a business product. It is not aimed at children and we do not knowingly collect their data.

18. Changes to this policy

We update this policy as NVRblink develops. When the changes matter, we will update the date at the top and, for partners, tell you by email or in the portal.