Nowy standard. Twoje centrum tworzenia inteligentnego, szybkiego i zrównoważonego oprogramowania AI

Zobacz teraz
Padlock next to a checklist with check marks, illustrating GDPR compliance questions

GDPR Compliance: 30 Questions & Answers for Digital Businesses

Joanna Staromiejska-Drwięga
|   Zaktualizowano 15 lis 2026

GDPR compliance means you can show, for every piece of personal data your product touches, why you collect it, on what legal basis, how long you keep it, who sees it, and how users can exercise their rights over it.

The regulation has applied since May 25, 2018, and it still doesn't hand you a checklist: it sets principles and leaves the implementation to you. Meanwhile enforcement has grown up. European regulators had issued around 2,700 fines worth about €6.1 billion by March 2026, according to the CMS GDPR Enforcement Tracker.

This article walks through the 30 questions every digital business should be able to answer, with a short answer to each and notes on what it means for your product.

Executive Summary

GDPR applies to any company that offers goods or services to people in the EU or monitors their behavior there, wherever the company is based.

The fastest way to find your compliance gaps is a data-flow audit: map what you collect, why, on what legal basis, where it goes and how long it stays. The 30 questions below structure that audit, from your role as controller or processor to breach response and documentation.

Most of the answers turn into concrete product requirements, such as access logs, per-purpose consent, data export and deletion that reaches every recipient, so the cheapest time to address them is before you build.

What is GDPR and does it apply to my business?

The General Data Protection Regulation (GDPR) is the EU law that governs how organizations process personal data. It replaced the 1995 Data Protection Directive and has applied since May 25, 2018. Personal data means any information relating to an identified or identifiable person: a name, an email address, location data, an IP address or another online identifier.

GDPR gives users more control over their data. They can find out what you store about them, get a copy, correct it, restrict or object to its use, and have it deleted. Supervisory authorities in each member state enforce these rights and can sanction companies that don't respect them.

Your location doesn't exempt you. GDPR applies to businesses outside the EU, including US companies, whenever they offer goods or services to people in the EU (paid or free) or monitor their behavior there. If your app is available to EU users, your newsletter goes to EU subscribers, or your CRM holds data on European customers, GDPR applies to that processing.

What happens if a company doesn't comply with GDPR?

The most serious infringements can bring administrative fines of up to €20 million or 4% of total worldwide annual turnover for the preceding year, whichever is higher (Art. 83 GDPR). These aren't theoretical. In May 2023 Ireland's Data Protection Commission fined Meta €1.2 billion for transferring EU users' data to the US without adequate safeguards.

Fines get the headlines, but regulators have other powers that can hurt a digital business more. They can order you to bring processing into compliance by a deadline, temporarily or permanently limit processing, or ban it outright (Art. 58 GDPR). For a product built on data, a processing ban can mean switching off a core feature.

Then there's reputation. If you suffer a breach that puts users at high risk, you have to tell them, not just the regulator. That notification costs you user trust, which can hurt more than the fine itself.

How can a digital business reduce its GDPR exposure?

You can't escape GDPR by moving your company, so the only way to reduce its impact is to process less. Collect fewer data points, avoid sensitive categories such as health data or religious beliefs, keep fewer purposes, and share data with fewer third parties. "We might need it later" is no longer a reason to keep data. Every field you store is a field you have to secure, justify and eventually delete.

Anonymization is the cheapest win. Teams often store full personal data for analytics when aggregated numbers would do. Data that's properly anonymized falls outside GDPR entirely.

The rest falls to your designers and developers. They don't need to be lawyers, but they need to know data protection by design and by default: by default, you process only the data each purpose needs, which limits the amount you collect, how far you process it, how long you keep it and who can access it. In practice that means building audit logs, per-purpose consent, data export, a restriction flag and deletion that reaches downstream systems into the architecture from the start, not retrofitting them before a launch.

How should you use these 30 GDPR compliance questions?

Use the questions as a structure for an internal data-flow audit. Run through them once for each purpose of processing: one pass for creating user accounts and providing your service, another for marketing, another for analytics. The answers differ by purpose, and so do your obligations.

The questions were originally written in 2018 by Kamila Koszewicz, then Monterail's in-house lawyer, who had followed and contributed to the GDPR legislative process since 2012. Our teams used them on client projects, and we've updated the answers for 2026. They're a starting point for conversations with your team and your lawyer, not legal advice.

Unless stated otherwise, the answers refer to data controllers.

Controller or processor: what is your role under GDPR?

1. Are you a data controller or a processor?

The answer sets the scope of your obligations. A controller decides what data is collected, for what purpose, how it's processed and for how long. Controllers carry the broadest duties: securing the data, meeting principles such as data minimization and transparency, and handling data subject requests.

A processor processes data on behalf of a controller and only within the scope the controller defines. A processor can't decide what data is processed or how; its main duty is to protect the data from unauthorized access or modification. Many software companies are both: a controller for their own users and marketing, a processor for client data they host.

2. Do you process data yourself or use third-party services, such as cloud hosting?

If a third party processes data for you, you need a written data processing agreement (an electronic one counts). It has to cover the subject matter and duration of the processing, its nature and purpose, the types of personal data and categories of data subjects, and both parties' obligations and rights (Art. 28 GDPR).

You stay responsible for the processing even when you outsource it. Choose only processors that can guarantee appropriate technical and organizational security measures.

3. Who in your company can access personal data, and are access levels different for different roles?

Being entitled to process data as a company doesn't mean every employee should see it. Grant access only to people whose role requires it, and define the scope: which data (client data, HR data) and what they can do with it. Some people need full rights to enter, modify and delete; for others, read-only access is enough.

4. Do you log who enters, modifies, deletes or accesses personal data, and when?

GDPR's integrity and accountability principles mean you need technical or organizational measures that show exactly who did what with personal data and when, whether it was an employee or the data subject. For most products, that means an audit log designed in from the start.

What should you check about how you collect personal data?

5. Do you get personal data from the data subject or from a third party?

The source determines what information you have to give the data subject (Art. 13 and Art. 14 GDPR). When you get data from a third party, it isn't enough that they obtained it lawfully: you need your own legal basis for processing it.

6. Do you collect personal data from children?

GDPR has special rules for offering online services directly to children. If you rely on consent, a parent or guardian has to give or authorize it for children under 16. Member states may lower that age to as low as 13 (Art. 8 GDPR), so the threshold depends on the country. Verifying parental consent is the hard part in practice. Design for it at the very start of a product; retrofitting it is expensive.

7. How do you collect data: by email, web forms, activity tracking, or something else?

Listing every collection channel is one of the first steps in auditing your data flows. Without it, you can't check whether you obtain valid consent where you need it or give users the information GDPR requires at each point of collection.

8. What categories of personal data do you collect?

By "categories" we mean name, address, IP address and so on. Listing them is essential for the audit, and you'll need the list for your record of processing activities (see question 30).

9. Do you collect sensitive data, such as health records, racial or ethnic origin, or religious beliefs?

Processing these special categories is prohibited by default and allowed only under the specific conditions in Art. 9 GDPR. The general recommendation is to avoid it. If your product can't, as in HealthTech, get legal advice early to establish a valid basis, and expect stricter security controls and a DPIA (see question 29).

10. Is all the data you collect actually necessary for its purpose?

Data minimization is one of GDPR's core principles. By default, limit the amount of data you collect, the extent of processing, how long you store it and who can access it to what the purpose requires. Apply it when auditing existing databases and when designing new user flows, from sign-up forms to tracking decisions.

11. What is the purpose of processing the data you collect?

You can process data only for specified, explicit and legitimate purposes, and you can't later reuse it in a way that's incompatible with them. A purpose like "improving our services" is too vague to rely on.

Every processing operation needs a valid legal basis. For ordinary (non-sensitive) data, Art. 6 GDPR gives six:

  • the data subject's consent for a specific purpose;

  • performance of a contract with the data subject, or steps taken at their request before entering into one;

  • a legal obligation the controller is subject to;

  • protecting the vital interests of the data subject or another person;

  • a task carried out in the public interest or in the exercise of official authority;

  • the legitimate interests of the controller or a third party, unless the data subject's interests or fundamental rights override them, particularly where the data subject is a child.

Consent isn't automatically the best option. If the processing is necessary to deliver what the user signed up for, contract is usually the more stable basis, because consent can be withdrawn at any time.

It has to be. If a user gave consent with one checkbox, they shouldn't have to email support to withdraw it (Art. 7(3) GDPR).

You should. If one consent clause bundles several purposes, the user can't agree to some and refuse others, so you can't show that consent to each purpose was freely given, and consent that isn't freely given isn't valid. A badly built consent clause leaves you without a legal basis at all.

How long can you keep personal data, and who can you share it with?

15. How long will you store the data, how do you set that period, and will deletion be manual or automatic?

Storage counts as processing, so you can keep data only as long as you have a valid legal basis for it. Define retention periods per category and purpose, and automate deletion where you can. Manual cleanup tends not to happen.

16. Do you have policies to correct or delete inaccurate data, and to delete data you no longer need?

Those are your duties under GDPR's accuracy and storage limitation principles. Put mechanisms and procedures in place so they happen as routine, not only when a user complains.

17. Do you keep statistical data in personal or anonymized form?

Anonymized data isn't personal data, so you can keep it as long as you like, even after the legal basis for the original personal data has expired. Anonymizing as much as your purpose allows also keeps you on the right side of data minimization. Pseudonymized data (where a key can re-identify people) is still personal data.

18. Do you tell data subjects who you are, how to contact you and what their rights are? When and how?

If you collect data directly from the data subject, give them this information at the moment of collection. If you get it from another party, inform them within a reasonable period and no later than one month after obtaining the data, or earlier if you contact them or disclose the data to someone else first. Write the information in clear, plain language and make it easy to find.

As a controller, sharing data takes one of two forms:

  • A processor works on your behalf: you define the purpose, duration and the processor's obligations in a data processing agreement. You don't need the data subject's consent for this.

  • The recipient becomes an independent controller: you lose control over what happens to the data, so you need your own legal basis for sharing it, such as consent that names the recipient and the purpose.

Companies in the same group are separate entities, so intra-group sharing follows the same rules.

20. Do you transfer personal data outside the EU?

Transfers outside the European Economic Area need a legal mechanism. The main ones are a European Commission adequacy decision, standard contractual clauses (the 2021 SCCs) and binding corporate rules. Explicit consent and other exceptions in Art. 49 cover only occasional transfers, not routine ones.

For the US, the EU-US Data Privacy Framework has covered transfers to certified US companies since July 2023. The EU General Court upheld it in September 2025, though an appeal to the Court of Justice may still follow. The Meta fine above shows what an unsupported transfer can cost, so check which mechanism each of your vendors relies on before any data moves.

How do you handle data subject rights requests?

21. How can users request access to their data, including a copy? Will you handle requests manually or automatically, and in what format?

Users can ask for a copy of the personal data you process about them (Art. 15 GDPR). The first copy is free; for further copies you may charge a reasonable fee based on administrative costs. If the request comes in electronically, provide the data electronically unless the user asks otherwise. You generally have one month to respond (Art. 12 GDPR).

Before the first request arrives, decide:

  • how users submit requests: a self-service page, a form, or email;

  • whether fulfilment is manual or automated;

  • if manual, whether you have enough trained people to handle the volume;

  • whether your procedures let you respond without undue delay.

Those four questions apply to every right below, so answer them once and reuse the setup.

22. How will you handle data portability, and in what format will you provide the data?

Portability applies when the user provided the data, processing is automated, and it's based on consent or a contract (Art. 20 GDPR). The user can ask for their data in a structured, commonly used and machine-readable format, or have it sent directly to another controller. GDPR doesn't name a format, so you choose one. JSON or CSV exports are the usual answer.

23. How can users request correction of their data, and how do you handle it?

Users can have inaccurate data corrected and incomplete data completed. When you correct, delete or restrict data, you have to tell every recipient you disclosed it to, unless that's impossible or would take disproportionate effort (Art. 19 GDPR). That's much easier if you've kept track of where data goes.

24. Can your system handle the right to restriction and the right to object?

Users can request restriction of processing when:

  • they contest the accuracy of the data;

  • processing is unlawful, but they want restriction instead of deletion;

  • you no longer need the data, but they need it for legal claims;

  • they've objected, and you're checking whether your legitimate grounds override theirs.

While processing is restricted, you can store the data but not otherwise use it. Restriction is usually temporary, so your system needs a way to switch processing off and back on for an individual record, with a visible flag showing the data is restricted.

The right to object needs the same design attention, and online services have to let users exercise it by automated means. When processing is based on legitimate interests, a user can object on grounds relating to their situation, and you can refuse only if you demonstrate compelling legitimate grounds or need the data for legal claims. An objection to direct marketing, including related profiling, is absolute: the processing has to stop.

This is the right to erasure, or "right to be forgotten" (Art. 17 GDPR). You have to delete data when:

  • it's no longer necessary for the purpose it was collected for;

  • the user withdraws consent and there's no other legal basis;

  • the user objects to the processing and there are no overriding grounds;

  • the data was processed unlawfully;

  • deletion is required by a legal obligation;

  • the data was collected from a child in connection with online services.

GDPR doesn't say how to do this technically, which makes it one of the harder rights to implement. For data you've made public, you're expected to take reasonable steps to inform other controllers, considering available technology and cost, not to track down every copy.

Such decisions are allowed only when they're necessary for a contract with the user, authorized by law, or based on the user's explicit consent (Art. 22 GDPR), and generally not on sensitive data. You also have to give users a real channel to get human review, express their point of view and contest the decision, with staff assigned to handle it. If your product uses AI models to approve, reject or score people, this question applies to you.

How should you prepare for breaches, DPOs, impact assessments and documentation?

27. Can you detect a personal data breach, and do you have a procedure for responding?

Controllers have to notify the supervisory authority of a personal data breach within 72 hours of becoming aware of it, unless the breach is unlikely to put people's rights and freedoms at risk (Art. 33 GDPR). A processor that discovers a breach has to tell the controller without undue delay. You have to document every breach, whether you report it or not: what happened, its effects and what you did about it.

If the breach is likely to put people at high risk, you also have to tell the affected users without undue delay. In some cases a public announcement is enough (Art. 34 GDPR). Seventy-two hours is very little time if you're working out the procedure for the first time, so write it and test it in advance.

28. Do you have a data protection officer, or know whether you need one?

Controllers and processors need a DPO when their core activities involve regular and systematic monitoring of people on a large scale, or large-scale processing of sensitive data, as well as in public bodies (Art. 37 GDPR). Many SaaS, AdTech and HealthTech products meet one of those tests.

29. Do any of your processes require a data protection impact assessment?

A DPIA is required when processing is likely to result in a high risk to people's rights and freedoms, especially when it uses new technologies (Art. 35 GDPR). It's required in particular for:

  • systematic and extensive evaluation of people based on automated processing, including profiling, that leads to decisions with legal or similarly significant effects;

  • large-scale processing of sensitive data;

  • systematic, large-scale monitoring of publicly accessible areas.

30. Do you know what documentation you need, and is your team trained for GDPR?

Controllers and processors have to keep records of processing activities (Art. 30 GDPR). A controller's records cover its details, the purposes of processing, the categories of data and data subjects, recipients, transfers outside the EU, retention periods and a general description of security measures. A processor's records cover its details and those of each controller it works for, the categories of processing, transfers and security measures.

Organizations with fewer than 250 employees are exempt, unless the processing is likely to create a risk, isn't occasional, or includes sensitive data. Most digital businesses process personal data continuously, so the exemption rarely helps them. The EU's Digital Omnibus proposal would raise the threshold to 750 employees, but as of late 2026 it's still going through the legislative process, so plan on keeping records.

Beyond the records, keep documentation that shows how you comply: your procedures, how you apply principles such as transparency and minimization, and evidence that your team has been trained.

Key Takeaways

  • GDPR applies to any business offering services to people in the EU, wherever it's based.

  • Fines reach €20 million or 4% of global turnover, but processing bans and breach notifications can hurt more.

  • Audit your data flows once per purpose of processing; the answers differ.

  • Most user rights become features: export, correction, restriction flags and deletion that reaches every recipient.

  • Collecting less data is the cheapest way to reduce your GDPR risk.

How should a digital business approach GDPR compliance in 2026?

Treat GDPR as a set of product requirements, not a legal document someone signs off once. The companies that handle it well know their data flows, collect less, and have logs, consent management, export and deletion built into their systems before a user or a regulator asks. Don't do it alone: the stakes are high enough that you should work with a data protection lawyer on the legal side and with engineers who know how to turn those requirements into architecture.

At Monterail we build software for regulated industries such as HealthTech and FinTech, where privacy and security shape the architecture from the first sprint. If you're planning a product that handles EU users' data, talk to our team about building it with GDPR in mind from the start.

GDPR Compliance FAQ

Joanna Staromiejska avatar
Joanna Staromiejska-Drwięga
Marketing Strategy Specialist
Linkedin
Joanna Staromiejska-Drwięga is a T-shaped marketer with over 10 years of experience in B2B tech marketing. As a Marketing Strategy Specialist at Monterail, she drives growth through multi-platform campaigns and cross-functional collaboration. Joanna holds a degree in International Business and Management. Her work spans landing pages, ebooks, and in-depth guides, including the well-known State of Vue reports.