A subscriber file isn't kept in a vault. It lives in a system that half the office can log into, and over the years it can pick up a shared password or two and an admin account belonging to someone who left long ago.
That's not a criticism. It's how things drift when everyone is busy getting issues out. But a subscriber file holds names, addresses, job titles, payment history and marketing consent for thousands of people, and the basics of looking after it are cheaper than the alternative.
This isn't about firewalls or penetration tests. It's the everyday stuff a circulation or subscriptions manager can check this week.
What the law actually asks for
UK GDPR has a security principle. It asks for "appropriate security of the personal data", and Article 32 talks about a level of security "appropriate to the risk". The ICO's guide to data security explains what that means in practice.
There's no checklist that makes you compliant. "Appropriate" depends on what you hold and what could go wrong. But the ICO's security outcomes page is fairly plain about the direction of travel: access limited to people who need it, strong authentication for privileged users, and a record of who accessed personal data.
That's most of this post, really.
Two-factor login, for everyone
If you do one thing, do this. A password on its own can be guessed, reused from another site or typed into a convincing fake login page. Add a one-time code from an authenticator app and a leaked password stops being enough.
The National Cyber Security Centre's advice on 2-step verification says it "helps to keep cyber criminals out of your accounts". The ICO suggests considering two-factor measures for users with privileged access.
Our view is that it should apply to everyone, not just admins. The customer service adviser can see every address on the file, and that's exactly what someone would be after. If two-factor is optional, the person who finds it a nuisance becomes the weak link.
Don't forget the other ways into the data. The email account that receives subscriber exports, the mailing house portal and the payment gateway all deserve the same treatment.
Permissions that fit the job
Giving everyone full admin rights is an easy trap to fall into. It tends to happen because someone needed one thing once, and admin was quicker than working out the right setting.
The ICO talks about access being "limited to those users who reasonably need such access". In a subscriptions team, that might look like:
- Customer service can view and update subscriber records, but can't delete invoices or export the whole file.
- Finance can see payments, credit notes and the ledger, and post adjustments.
- The gone-away desk can mark returned copies and nothing else.
- Marketing can run selections and counts, with exports restricted to named people.
- Admin is two or three people, not the whole office.
Once a year, export a list of who can do what and read it properly. If anything makes you wince, fix it there and then.
Audit trails: who changed what
When a reader rings to say their address was changed and they didn't ask for it, you want to be able to answer in a minute rather than shrug.
A decent audit trail records logins, failed logins and changes to records, with who made them and when. The ICO says you should "ensure there is an appropriate audit trail". It's also handy for reasons that have nothing to do with security. It settles arguments about who processed an order, it helps with subject access requests, and auditors like it.
The test is simple. Pick a subscriber at random and ask your system who last changed their record and when. If the answer is "no idea", that's worth fixing.
Starters, leavers and temps
Leavers are where access quietly piles up. Someone moves on, their account stays active, and nobody notices for a year.
A few habits help:
- Add system access to your leaver checklist, alongside the laptop and the door pass. That means every system, not just email.
- Give temps and contractors accounts that expire on the day their contract ends, so it doesn't depend on someone remembering.
- Never share logins. If two people use one account, your audit trail can't tell them apart, and you can't remove one without locking out the other.
- Review accounts quarterly. Anyone who hasn't logged in for three months probably doesn't need access.
Exports and spreadsheets
The best-protected database in the world doesn't help much if its contents are sitting in a spreadsheet attached to an email.
Exports are often the real risk. A list goes to a mailing house, a copy sits in someone's downloads folder, another gets forwarded to a sales rep. Each one is a copy of personal data outside the system's controls.
Keep exports to people who need them, send files securely rather than as email attachments, and delete them once the job's done. Our post on subscriber data retention covers how long to keep things in the first place.
Suppliers count too
Your bureau, mailing house, printer, email platform and software supplier may all handle subscriber data for you. The ICO's guidance says that as the data controller you remain responsible for compliance, and a processor working for you needs a binding contract that covers security.
So ask your suppliers the boring questions. Do they enforce two-factor login? Who on their side can see your data? Are they Cyber Essentials certified? The ICO describes Cyber Essentials as "a set of basic technical controls", and it's a reasonable baseline to ask for. If you're weighing up who runs the work, our comparison of in-house and bureau set-ups covers data control too.
When something goes wrong
A personal data breach isn't only a hack. The ICO's guide to personal data breaches includes loss, alteration, unauthorised disclosure of, or access to, personal data. A lost laptop or a file sent to the wrong person can count.
If a breach is likely to pose a risk to people's rights and freedoms, you must report it to the ICO within 72 hours of becoming aware of it, where feasible. That clock goes quickly, so decide now who makes the call and where the ICO's reporting page is, rather than finding out on the day.
Where we fit in
In Avio, our subscription platform for larger publishers, every user logs in with two-factor authentication, around 60 permissions control what each person can see and do, accounts can be set to expire, and a searchable event log records logins, failed logins and changes down to the field. In Adeptis, our all-in-one platform for smaller publishers, two-factor login is mandatory, permissions are set per user (down to a single screen for the gone-away desk) and consent is recorded by channel. As a company, we're Cyber Essentials certified.
If you'd like to see how that would look for your team, book a demo or just get in touch.