Nodkeeper

What GDPR means for a small business website

A trainer who takes a booking needs a name, a way to confirm the appointment and a date. Each detail has a purpose. Following the information from booking to deletion is a practical way to start applying the GDPR.

Sources checked

Which information is personal data?

The General Data Protection Regulation is the EU law governing the use of personal data. It gives people rights over information about them and sets duties for the organisations using it. A Swedish studio falls within its scope when it handles client bookings, even if only a few people visit its website each week.

Names and email addresses are straightforward examples. An online identifier can also be personal data when the person can reasonably be identified, directly or indirectly. A repeatable code derived from an IP address may allow a business to recognise or link visits. Hashing an IP address alone does not establish anonymity. Consider who holds the other information and what they can reasonably do with it.

Give each use of data a purpose

For each activity, write down what you collect, why you need it, which lawful basis applies, who receives it and when you will delete it. Give visitors a clear privacy notice explaining these decisions and how to exercise their rights.

  • Scheduling a session. Processing the details needed to arrange the session may be necessary for the contract with the client. Ask only for details the booking actually requires.
  • Keeping financial records. A legal obligation may require you to retain particular invoice data after the appointment. Identify the applicable obligation and period.
  • Adding a marketing audience. This is a separate purpose. Assess the legal basis and electronic marketing rules before using a booking address for campaigns.

Decide who can access each system and how a client can reach you about their data. If your intake form asks about injury or illness, health data has extra protections under Article 9. Start by considering whether the website needs to collect it at all.

Who needs a data processing agreement?

The business deciding the purpose and essential means of obtaining bookings is usually the controller. A booking supplier storing those bookings solely on its instructions acts as a processor for that work. A provider using data for its own purposes can have a different role for that use. Follow the actual activity when assigning roles.

Where a processor acts for a controller, Article 28 requires binding terms. A data processing agreement (DPA) sets out the work, data, people affected, duration, documented instructions and protections. Check the authorisation process for subprocessors, security, help with rights and incidents, audits, and arrangements for returning or deleting data. Also check where suppliers process the data and any applicable transfer safeguards.

For a consent service, distinguish the choices it handles for your website from its own account administration. Read the Nodkeeper processing terms.

What if a client asks about their data?

Imagine a client asks for a copy of the personal data you hold about their appointments. Give them a way to reach the business, verify their identity in proportion to the risk, and check the booking system and any other relevant records. Your processor agreement should make it possible to obtain the information you need from suppliers.

Article 12 generally requires a response without undue delay and within one month. A necessary extension for complex or numerous requests can add up to two months. Tell the person within the first month and explain the reason. Access, correction and erasure are distinct rights. If you must retain an invoice under another law, explain that obligation when handling an erasure request.

A consent management platform (CMP) can present purposes, record choices and control optional integrations that have been connected to it. You still choose which booking fields to collect, set retention for client records, secure staff accounts and respond to rights requests. A sensible starting point is to list every supplier that receives customer or visitor information.

Sources