Privacy policy
GPnav Hub and GPnav Notify. Last updated 17 October 2026.
The short version
- We never collect patient data. GPnav Notify works inside Patchs in your browser. It does not copy, store or send any patient details, messages or page content anywhere.
- GPnav Hub holds practice accounts, licence keys and settings (box and template names). That is all.
- No analytics, no advertising, no tracking cookies, and we never sell or share data for marketing.
Who we are
GPnav Hub and GPnav Notify are sold to GP practices under the GPnav brand by Tower Family Healthcare Partnership, and built, hosted and maintained by Xnet Technology Ltd, a company registered in England and Wales. In this policy "we" means both.
For the accounts a practice sets up for its staff, the practice decides what is held and is the data controller. GPnav processes that data on the practice's behalf, and Xnet Technology Ltd hosts it as our sub-processor. Practices can ask us for a data processing agreement.
Questions about this policy or your data: appsupport@gpnav.net.
GPnav Notify (the browser extension)
What it reads
Notify runs only on Patchs pages (patchs.ai). It reads the page so it can find the Assign staff member box, the message box, the Send as SMS tick box and the Send and Assign buttons, and fill them in when a member of staff picks a box that has a rule. Everything it reads stays on the page.
What it keeps in the browser
- The licence key, its status, the practice name and the end date.
- The practice's box rules (box names and template names or messages) and the Patchs page map (where the buttons are on the page).
- A random install ID, created when Notify is installed. It identifies the browser profile to GPnav Hub, not a person or a PC.
- Settings chosen on the options page.
- In the optional "assign first" mode only: the Patchs request number and box name for up to 10 minutes, so the request can be reopened to send the SMS, and the internal Patchs ID of each box with a rule.
This is stored with the browser's extension storage on that computer. Removing the extension deletes it.
What it sends
Notify contacts one server, GPnav Hub (hub.gpnav.net), when the licence is activated, at browser start-up, every 4 hours and when someone clicks Check now or Remove licence. Each request contains only:
- the licence key,
- the random install ID,
- the browser type (Chrome or Edge) and the extension version,
- the version numbers of the box rules and page map it already has.
Like any web request, it also reveals the computer's internet (IP) address to our server. Notify sends nothing to Patchs that a member of staff could not send themselves: it clicks Patchs' own buttons, and the SMS is sent by Patchs.
Chrome Web Store
The use of information received by GPnav Notify adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use the data above only to provide and license Notify, never for advertising, credit decisions or any purpose unrelated to Notify, and we do not let people read it except to keep the service secure, to give support you ask for, or where the law requires.
GPnav Hub (the website)
What we hold
| Data | Why |
|---|---|
| Practice name and ODS code | To know which practice a licence belongs to. |
| Users' name, email address, role and password (stored only as a secure one-way hash) | To let practice staff sign in and manage their licences. |
| Licence keys (encrypted), labels the practice gives them, and for each browser using a key: install ID, browser type, extension version, first and last seen | To license the extension, show the practice where its keys are used, and let them release a key. |
| Box rules and settings | To send them to the practice's browsers. |
| A record of changes (who, what, when, IP address) and sign-in attempts | Security, preventing misuse and resolving disputes. |
| Server logs (IP address, time, the last four characters of a licence key, part of the install ID) | Running the service securely and fixing problems. Full keys are never logged. |
We rely on our contract with the practice, and our legitimate interest in running a secure service, as the lawful bases for this.
Cookies
GPnav Hub sets one cookie, a session cookie that keeps you signed in. It is strictly necessary and is deleted when you sign out or close the browser. We use no analytics, advertising or third-party cookies.
Who else sees it
Only Tower Family Healthcare Partnership (GPnav) and Xnet Technology Ltd, to run and support the service. When payments are added, card details will be handled by our payment provider (Stripe), not by us. We do not sell data or share it with anyone else unless the law requires it.
Where it is kept and for how long
GPnav Hub is hosted in the United Kingdom. We keep account and licence data while the practice has an account, and delete it within 90 days of the account closing, except billing records we must keep by law. Security records and server logs are kept for up to 12 months.
Keeping it safe
All traffic is encrypted (HTTPS). Passwords are hashed, licence keys are encrypted, access is rate limited and every admin change is recorded.
Your rights
Under UK data protection law you can ask to see the personal data we hold about you, have it corrected or deleted, object to or restrict how we use it, and receive a copy. Practice staff should usually ask their practice first, as it controls their account. Email appsupport@gpnav.net and we will reply within one month. If you are unhappy with how we handle your data you can complain to the Information Commissioner's Office at ico.org.uk.
Changes
If we change this policy we will update the date at the top. If a change affects what Notify collects, we will say so in the extension's release notes before it takes effect.