Back to the subscription dictionary

GDPR

The General Data Protection Regulation (GDPR) is a European Union law that governs how organisations collect, store, and process personal data. It sets strict requirements for transparency, security, and consent, with territorial scope determined by factors such as an EU establishment or certain activities directed at people in the EU. For subscription and service businesses, GDPR defines how customer information must be managed throughout the customer lifecycle.

Prepared with AIContent updated

When does the EU GDPR apply?

The EU General Data Protection Regulation has applied since 25 May 2018. Its territorial scope follows Article 3, including processing in the context of an EU establishment and, in specified circumstances, offering goods or services to people in the EU or monitoring their behaviour there from outside the EU. Citizenship alone does not decide its application.

Personal data can identify someone directly or indirectly. Contact details, payment references and usage records can therefore be covered. Pseudonymisation does not by itself make data anonymous.

Map one processing activity

Illustrative mapping of contact details used to administer a subscription.

  1. Purpose and role

    Explain why data is used and who decides

  2. Basis and scope

    Assess the legal basis and necessary data

  3. Recipients and security

    Record access, suppliers and safeguards

  4. Retention and rights

    Set periods and a process for requests

This is a working map, not legal approval or a compliance score. Assess requirements for the actual processing.

Roles and responsibilities

A controller determines purposes and means; a processor handles personal data on the controller’s behalf. An organisation can have different roles for different activities. A supplier is not automatically a processor for every function.

Where Article 28 applies, processing terms must address matters including instructions, security and subprocessors. Signing terms does not replace the required assessment and ongoing oversight.

Purpose, lawful basis and necessary data

Map actual purposes, data types, recipients and retention. Identify an appropriate lawful basis for each processing activity. Consent is one possible basis, not necessarily the correct basis for necessary billing. Special-category data needs an additional assessment.

Apply lawfulness, fairness, transparency, purpose limitation, data minimisation, accuracy, storage limitation, integrity and confidentiality. The controller must be able to demonstrate compliance. Further use for another purpose needs an appropriate assessment.

Rights and retention

Rights include access and rectification and, subject to conditions, erasure, restriction, objection and portability. They are not unconditional rights to every record or every requested action. Legal retention obligations can limit erasure.

Portability concerns data provided by the person where automated processing relies on consent or contract. Arrange secure handling and proportionate identity checks. Article 12 governs response timing and possible extensions; assess the request rather than promising an unconditional deadline.

Security and risk assessment

Choose technical and organisational safeguards appropriate to the processing risk. Restrict access, handle incidents and assess relevant breach reporting and notification obligations. A privacy notice or internal score alone does not demonstrate compliance.

An Article 35 impact assessment is required for processing likely to result in high risk. A data protection officer is mandatory in the cases specified by Article 37, not for every SaaS business. Document the actual assessment.

Subscription-business implications

Assess billing, analytics, support, marketing, suppliers and any international transfers separately. Electronic marketing and cookies can involve additional rules. A lawful basis for one task is not unrestricted permission for every other use.

Data protection is a duty and can matter to customers and risk. It does not guarantee higher CLV, lower churn or ARR growth. Sanctions and incident costs can affect profit and cash; they are not deducted directly from ARR.

Questions and answers

Must every activity rely on consent?

No. The appropriate basis depends on the actual processing. Consent must meet its conditions, while other laws can impose separate requirements, for example for electronic marketing.

Is every supplier a processor?

No. Assess the role for the specific processing. A supplier can be a processor for some activities and a separate controller for others.

Does every business need a DPO and an impact assessment?

No. DPO requirements follow Article 37. An Article 35 impact assessment concerns processing likely to result in high risk. Assess and document whether the relevant conditions apply.

Does cancellation require immediate deletion of every record?

No. Assess purposes, retention needs and legal obligations, and handle rights under their applicable conditions. An ended subscription does not establish one universal deletion date for every record.

How can a GDPR fine affect financial metrics?

For certain infringements, the ceiling is €20 million or 4% of total worldwide annual turnover, whichever is higher. Other infringements have a different ceiling. These are maximum limits, not automatic fines. An actual sanction can affect profit and cash, but is not directly deducted from ARR.

Sources and documentation

We update our content regularly and do our best to keep it accurate. If you find an error or think something is missing, please tell us. We are always looking for ways to improve the content.

Found an error? Let us know