GDPR guide
GDPR compliance checklist for companies in Sweden
GDPR compliance means following the EU's General Data Protection Regulation (Regulation (EU) 2016/679) whenever your company handles information about people. In Sweden it is supplemented by lag (2018:218) and supervised by IMY, the Swedish Authority for Privacy Protection. This checklist covers the main duties and marks which ones are legal duties and which are good practice. New to the topic? Start with What is GDPR?
On this page
This is a plain-language summary, not legal advice. Where this page and the law differ, the law decides. In the checklist, Duty means the Regulation or the Swedish law requires it. Good practice means it is not a legal requirement in itself, but it helps you meet one or show that you do.
1. In short
- GDPR applies to the processing of personal data: any information about an identified or identifiable person (Article 4(1)).
- The company that decides why and how data is used is the controller. It must be able to show that it complies (Article 5(2)).
- A personal data breach must be reported to IMY within 72 hours of you becoming aware of it, where feasible, unless it is unlikely to risk people's rights and freedoms (Article 33(1)).
- Fines go up to EUR 20 million or 4 % of worldwide annual turnover, whichever is higher, for the most serious infringements (Article 83(5)).
2. The Swedish law and IMY
GDPR is an EU regulation. It is "binding in its entirety and directly applicable in all Member States" and has applied since 25 May 2018 (Article 99). You do not need a Swedish law for it to apply.
Sweden has added a supplementary law: Lag (2018:218) med kompletterande bestämmelser till EU:s dataskyddsförordning, often called dataskyddslagen. It "kompletterar" (supplements) the Regulation (1 kap. 1 §). Two of its rules:
| Section | What it says in plain English |
|---|---|
| 2 kap. 4 § | For online services offered directly to a child living in Sweden, the child's own consent is enough from age 13. Under 13, a parent or guardian must give or approve it. |
| 6 kap. 2 § | For public authorities, the fine is capped at SEK 5 million (Article 83(4) breaches) or SEK 10 million (Article 83(5) and 83(6) breaches). |
The supervisory authority is IMY (Integritetsskyddsmyndigheten), in English the Swedish Authority for Privacy Protection. It takes breach reports and the contact details of data protection officers. The text of the law is on riksdagen.se.
3. Does GDPR apply to you?
Almost every company does, for example with customer contacts and staff records. "Processing" means any operation on personal data, such as collecting, storing, using, sharing or deleting it (Article 4(2)).
It applies to processing in the context of an establishment in the EU, wherever the processing takes place (Article 3(1)). It also applies to a company outside the EU that offers goods or services to people in the EU or monitors their behaviour there (Article 3(2)).
Two roles matter. The controller decides the purposes and means of the processing. The processor processes data on the controller's behalf (Article 4(7) and (8)).
4. The checklist
| Item | Status | What to do |
|---|---|---|
| 1. Lawful basis Art 6 | Duty | For every processing purpose, pick at least one of the six bases in Article 6(1). Do not process without one. |
| 2. Principles Art 5 | Duty | Meet the principles, and be able to show it: lawful, fair and transparent, limited purpose, minimal data, accurate, kept no longer than needed, secure. |
| 3. Records of processing Art 30 | Duty (with an exemption) | Keep a written record of your processing activities. See below for who can skip it. |
| 4. Tell people Arts 12 to 14 | Duty | Give clear, plain-language information about your processing. A privacy notice is the usual way. |
| 5. Data protection by design Art 25 | Duty | Build safeguards into systems, and by default process only the data each purpose needs. |
| 6. Processors and contracts Art 28 | Duty | Use processors that give sufficient guarantees, and sign a contract with the required terms. |
| 7. Security Art 32 | Duty | Apply technical and organisational measures that fit the risk, and test them regularly. |
| 8. Breach handling Arts 33, 34 | Duty | Notify IMY within 72 hours where feasible, tell people when the risk is high, and document every breach. |
| 9. Impact assessment Art 35 | Duty (high-risk cases) | Assess the risks before starting processing that is likely to be high risk. |
| 10. Data protection officer Art 37 | Duty (in listed cases) | Appoint one if you are a public body, or your core activity is regular, systematic, large-scale monitoring of people, or large-scale special-category or criminal-conviction data. |
| 11. People's rights Arts 12 to 22 | Duty | Answer requests such as access within one month. |
| 12. Transfers Arts 44 to 49 | Duty | Send data outside the EU only under one of the allowed routes. |
| 13. Policies and review Art 24 | Duty where proportionate | Adopt data protection policies, and review and update your measures. |
| 14. Staff awareness | Good practice | Train people who handle personal data. The Regulation requires steps so that staff only process on your instructions (Art 32(4)). |
| 15. Breach response plan | Good practice | Write down who decides, who reports and how. IMY advises having procedures and an action plan ready. |
| 16. Records even if exempt | Good practice | IMY recommends keeping a record even where the exemption applies. |
Lawful basis (Article 6)
You need at least one lawful basis for each purpose (Article 6(1)).
The six bases are: consent (freely given, specific, informed and unambiguous, Article 4(11)); contract with the person; legal obligation; vital interests; public task or official authority; and legitimate interests of you or a third party, unless the person's rights and freedoms override them. Public authorities cannot use legitimate interests for their tasks.
Special categories of data, such as health data or trade union membership, are prohibited by default and need an extra condition (Article 9). See What is GDPR?
Records of processing (Article 30)
A controller's record holds your contact details, the purposes, the categories of people and data, the recipients, transfers to other countries and, where possible, the time limits for erasure and a general description of security measures (Article 30(1)). A processor keeps a shorter one (Article 30(2)). It must be in writing, which can be electronic, and you must give it to the authority on request (Article 30(3) and (4)).
Exemption. Article 30(5) says the duty does not apply to an organisation with fewer than 250 people unless the processing is likely to risk people's rights and freedoms, is not occasional, or includes special-category or criminal-conviction data. So to skip it, all three must hold: the processing is unlikely to risk people, is occasional, and has no such data. IMY says each processing activity is judged separately. Payroll is not occasional, so it needs a record.
Processors and data processing agreements (Article 28)
If a supplier handles personal data for you, for example hosting, payroll or email, the processing must be governed by a binding contract. Article 28(3) says the contract must make sure the processor acts only on your documented instructions.
It must also bind the processor to confidentiality, require the Article 32 measures, require your prior specific or general written authorisation before it uses another processor (Article 28(2)), require help with people's requests and with Articles 32 to 36, require deletion or return of the data at the end, and allow audits.
The contract must be in writing, and electronic form counts (Article 28(9)). It is often called a DPA. You stay responsible for the personal data. If your processor is breached, it must tell you, and you must report to IMY unless the breach is unlikely to risk people's rights and freedoms (Article 33(1) and (2)).
Security of processing (Article 32)
Measures must give "a level of security appropriate to the risk" (Article 32(1)). As appropriate, they include pseudonymisation and encryption, keeping systems confidential, intact, available and resilient, restoring access to data in a timely manner after an incident, and a process for regularly testing and evaluating the measures.
Data protection impact assessment, DPIA (Article 35)
Before starting processing that is likely to result in a high risk to people, you must assess the impact.
Article 35(3) names three required cases: systematic and extensive evaluation of people based on automated processing, including profiling, that leads to decisions with legal or similarly significant effects, large-scale special-category or criminal-conviction data, and large-scale systematic monitoring of a publicly accessible area.
The assessment describes the processing, judges necessity and proportionality, assesses the risks and sets out the measures (Article 35(7)). If the assessment shows a high risk without measures to reduce it, you must consult IMY before you begin (Article 36(1)). IMY puts it this way: if you still consider there is a high risk, consult IMY first.
Data protection officer, DPO (Article 37)
You must appoint a DPO in the cases listed in Article 37(1).
This applies if you are a public authority or body (not courts acting in their judicial role), or if your core activities need regular and systematic large-scale monitoring of people, or consist of large-scale processing of special categories or criminal-conviction data.
Otherwise appointing one is optional (Article 37(4)). You must publish the DPO's contact details and give them to the supervisory authority (Article 37(7)). IMY has an online form for this.
5. Data breaches: 72 hours to IMY
A personal data breach is "a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data" (Article 4(12)).
| Who | Duty | Source |
|---|---|---|
| Controller to IMY | Notify without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. If later than 72 hours, give the reasons for the delay. | Art 33(1) |
| Processor to controller | Notify without undue delay after becoming aware. | Art 33(2) |
| Controller to the people affected | Tell them without undue delay when the breach is likely to result in a high risk, in clear and plain language. | Art 34(1), (2) |
| Controller, always | Document every breach: the facts, its effects and the action taken. | Art 33(5) |
The notice to IMY must at least describe the breach, give a contact point, describe the likely consequences and describe the measures taken or proposed (Article 33(3)). If you do not have everything yet, you can give the information in phases (Article 33(4)).
You do not have to tell the people affected if, for example, protection such as encryption made the data unintelligible to anyone unauthorised, if you have since removed the high risk, or if telling each person would take disproportionate effort and a public notice works instead (Article 34(3)). In Sweden, Articles 33 and 34 do not apply to incidents that must be reported under the säkerhetsskyddslag (2018:585) (lag 2018:218, 1 kap. 4 §).
6. GDPR and NIS2 reporting
If your company is also covered by NIS2 (in Sweden, Cybersäkerhetslagen), one incident can trigger two separate reports. A GDPR report is about personal data and goes to IMY. A NIS2 report is about a significant incident and goes to the CSIRT unit (Cybersäkerhetsförordningen 2025:1507, 6 §), which since 1 July 2026 is Försvarets radioanstalt, FRA (31 §, as changed by SFS 2026:623).
| GDPR | NIS2 | |
|---|---|---|
| First deadline | 72 hours, where feasible (Art 33(1)) | 24 hours, early warning (Art 23(4)(a)) |
| Second step | Information may follow in phases (Art 33(4)) | 72 hours, incident notification (Art 23(4)(b)) |
| Final step | No final report step in Article 33 | Final report within one month of the notification (Art 23(4)(d)) |
The NIS2 Directive says that when a supervisory authority finds that an infringement of Article 21 or 23 can involve a personal data breach, it must inform the data protection authority without undue delay (NIS2 Article 35(1)). It also says the NIS2 authority must not fine for the same conduct that the data protection authority has already fined under Article 58(2)(i) of GDPR (NIS2 Article 35(2)). In Sweden, the supervisory authority must cooperate with IMY on incidents that are also personal data breaches (Cybersäkerhetsförordningen 2025:1507, 18 §). Details on the NIS2 side are in NIS2 incident reporting and Cybersäkerhetslagen.
7. People's rights, including access
People can ask what you hold about them and ask you to act on it. You must make this easy (Article 12(2)). The main rights are:
Access (Article 15), rectification (16), erasure (17), restriction (18), data portability (20), objection (21) and the right not to be subject to a decision based solely on automated processing (22).
The access request (Article 15). The person can get confirmation of whether you process data about them, a copy of the data, and information about the purposes, categories of data, recipients, storage period (or the criteria for it), their other rights, the right to complain to the authority, the source if you did not collect it from them, and any automated decision-making (Article 15(1) and (3)).
Respond without undue delay and within one month. Complex or numerous requests can extend this by two months, with reasons given within the first month (Article 12(3)). It is free of charge, unless a request is manifestly unfounded or excessive (Article 12(5)). If you refuse, say why, and say that the person can complain to the authority and go to court (Article 12(4)).
8. Transfers outside the EU
Chapter V (Articles 44 to 50) controls sending personal data to a country outside the EU or to an international organisation. A transfer may take place only if the conditions in the chapter are met (Article 44). The main routes are:
- An adequacy decision: the European Commission has decided the country ensures an adequate level of protection. No specific authorisation is needed (Article 45(1)).
- Appropriate safeguards, where people have enforceable rights and effective remedies. Binding corporate rules under Article 47 are one example (Article 46).
9. Fines
Each authority must make fines "effective, proportionate and dissuasive" (Article 83(1)). The amount depends on factors such as how serious and long the infringement was, whether it was intentional, and how you cooperated (Article 83(2)).
| Maximum | For infringing |
|---|---|
| EUR 10 million, or for a company 2 % of worldwide annual turnover, whichever is higher | Controller and processor duties in Articles 8, 11, 25 to 39, 42 and 43 (design, processors, records, security, breach notification, DPIA, DPO) (Article 83(4)) |
| EUR 20 million, or for a company 4 % of worldwide annual turnover, whichever is higher | Basic principles (Articles 5, 6, 7, 9), people's rights (Articles 12 to 22), transfers (Articles 44 to 49), and ignoring an authority's order (Article 83(5), (6)) |
People who suffer damage can also claim compensation (Article 82, and lag 2018:218, 7 kap. 1 §).
10. How SimpleSecurity helps
SimpleSecurity keeps records and watches your systems. It does not decide your lawful basis, write your privacy notice or make an organisation compliant by itself, and SimpleSecurity holds no certification.
| Duty | SimpleSecurity service |
|---|---|
| Show you comply (Art 5(2), 24) | Compliance: maps controls across 22 frameworks, GDPR included, with an export pack. |
| Know your systems (Art 30, 32) | Asset Database: one list of assets, linked to vendors. |
| Processors (Art 28) | Vendor Risk: tiered questionnaires and a portal where the vendor answers. |
| Security and testing (Art 32) | Vulnerability Scanner and SSL/TLS Monitor. |
| Restore access (Art 32(1)(c)) | Backups: a heartbeat for your backup jobs, with restore tests logged per job. |
| Breach clock and records (Art 33) | Incident Register: NIS2 24h/72h and GDPR breach-notification clocks. |
| Policies and staff (Art 24, 32(4)) | Policy Register and People & Awareness. |
SimpleSecurity publishes its own DPA and sub-processor list. See every service or see the plans.
Related guides
11. Sources
- Regulation (EU) 2016/679 (GDPR), Articles 2 to 6, 9, 12 to 18, 20 to 22, 24, 25, 28, 30, 32 to 37, 44 to 46, 82, 83, 99
- Lag (2018:218), 1 kap. 1, 4 §§, 2 kap. 4 §, 6 kap. 2 §, 7 kap. 1 §
- IMY: personal data breaches and IMY: notification form
- IMY: processing record, impact assessments, data protection officers and about IMY
- Directive (EU) 2022/2555 (NIS2), Articles 23 and 35
- Cybersäkerhetsförordning (2025:1507), 6, 18 and 31 §§, as changed by SFS 2026:623