Last updated: 3 October 2026
This policy explains how Hamahud Ltd, trading as PharmacyData (company number 17429503) ("PharmacyData", "we", "us"), collects, uses and protects personal data when you use pharmacydata.co, the PharmacyData iOS app and the PharmacyData AI connector. It applies to visitors, registered users, and Premium subscribers.
Account information
Email address, display name, and a securely hashed password (we never store passwords in plain text). If you sign in with Google, we receive your Google account email and profile name.
Pharmacy association
If you're a pharmacy owner or manager, the ODS code of the pharmacy you link to your account, so we can show you that pharmacy's data.
Billing information
Website subscriptions are processed by Stripe and iOS subscriptions are processed by Apple. We do not receive or store your card details. We store your subscription status, plan, and payment-provider reference so the site and app know what you're entitled to see.
Device and usage data
To protect accounts from unauthorised access, we record a hashed identifier for devices and IP addresses used to sign in, along with browser/app type and rough location (country/region/city derived from IP). We also log which features you use (e.g. viewing a pharmacy report) to maintain service reliability and enforce plan limits. If you enable iOS notifications, we also store the device push token and your notification preferences so we can deliver the updates you requested.
Business-intelligence enquiries
If you request a BI walkthrough, we collect the name, work email, company, role, use case, timing and message you choose to provide so we can assess and respond to that request. Submitting the form does not subscribe you to marketing.
Locum directory profiles
If you create a locum profile, we collect the professional and availability details you provide, including your name, GPhC number, role, location, travel radius, experience, skills, indicative rate, availability and profile description. We also store a contact email address and any contact telephone number you provide for direct enquiries.
Locum profiles are not shown to public visitors or free account holders. After our review, approved profile details are available only to signed-in users with an active paid PharmacyData subscription. The contact email and any telephone number provided are displayed to those paid members while the listing is active.
Analytics data
We record first-party, pseudonymous product events such as a search, scorecard view, signup step or checkout outcome. Records may include a random browser/session identifier, page, campaign fields, browser family and a one-way IP hash. We strip direct identifiers from event metadata. We also use Cloudflare Web Analytics to understand website visits and performance.
Account security checks
New account forms use Cloudflare Turnstile to distinguish legitimate visitors from automated abuse. Cloudflare processes browser, device and network security signals for this purpose; PharmacyData receives the validation result rather than a reusable copy of those signals.
The dispensing, service, and nomination figures shown on PharmacyData come from publicly published NHS and pharmacy regulator datasets (NHSBSA, GPhC, and equivalent bodies in Scotland, Wales and Northern Ireland). This data is published at pharmacy level, not patient level — it does not identify individual patients and is not personal data about them.
We do not sell your personal data, and we do not use it for third-party advertising.
The PharmacyData iOS app lets pharmacy professionals create an account, purchase or restore a subscription through Apple, and access the same account and pharmacy data available on the website. Existing subscribers can sign in with the same PharmacyData account. The app uses a secure sign-in token instead of a browser cookie. It does not use location tracking, advertising identifiers, or third-party advertising SDKs.
The PharmacyData AI connector lets you connect AI assistants such as Claude or ChatGPT to your PharmacyData account, so the assistant can look up pharmacy data for you. You choose to connect an assistant by signing in to PharmacyData and approving access on our consent screen.
We use essential cookies or local storage for sign-in sessions, OAuth security state, account protection and requested product limits. These are needed to provide or secure the service.
We use first-party pseudonymous browser and session identifiers, together with Cloudflare Web Analytics, to understand website visits, acquisition and product performance.
We have not added advertising or retargeting pixels. Any future advertising measurement must be reviewed and consent-controlled before activation.
Under UK GDPR, you can ask us to access, correct, export, or delete your personal data. You can:
To exercise any other rights, or if you have concerns about how we handle your data, contact us using the details below. You also have the right to complain to the UK Information Commissioner's Office (ico.org.uk).
We keep account data for as long as your account is active. Device session and usage logs are retained for a limited period to support security monitoring, then removed on a rolling basis. A deactivated locum profile is hidden from the directory immediately; we retain a limited review and audit record while the account remains active so we can prevent fraud and resolve disputes. When you delete your account, we deactivate it immediately and revoke all sessions; residual data is removed within a reasonable period thereafter, except where a limited record must be kept to meet legal, security or dispute obligations.
PharmacyData is a business tool for pharmacy professionals and is not directed at, or intended for use by, children.
We may update this policy as the product changes. Material changes will be reflected by updating the "Last updated" date above.
Questions about this policy or your data? Email hello@pharmacydata.co or use our contact form.