For Data Protection Officers
Every DPO duty, turned into registers, deadlines and evidence.
Iodynka keeps the record of processing, counts 72 hours after a breach and one month after a request, and holds DPIAs, processor agreements and authorisations in one place. Built around GDPR as it is practised in Poland, with the Polish supervisory authority (UODO) in mind.
The application is in Polish. We answer in English or Polish.
Made for three kinds of DPO.
In-house DPO
One organisation, many processes. Registers linked to real systems and suppliers, so nothing is typed twice.
External DPO
Several clients, each with its own registers, deadlines and readiness score. Switch organisations without switching tools.
Law firms
Data protection practice across many organisations, with breach and request deadlines visible for the whole portfolio.
What GDPR asks of a DPO, and what Iodynka actually does.
Duty by duty, with the article. Where the app does only part of the work, we say so.
| Article | Duty | In Iodynka | Status |
|---|---|---|---|
| Art. 30 | Record of processing | Entries linked to systems, processes, suppliers and data categories. Versioned publishing with a diff. | Covered |
| Art. 33, 34 | Personal data breaches | 72-hour clock from detection, ENISA severity method, decisions with reasons, notification text and correspondence. | Covered |
| Art. 12 to 22 | Data subject requests | Case number, identity check, affected processing, Art. 19 notices. One-month deadline and extension tracked. | Covered |
| Art. 35, 36 | DPIA | Screening, necessity, risk matrix with measures, prior consultation and DPO opinion in one assessment. | Covered |
| Art. 28 | Processors | Role, scope, agreement and sub-processor checks on every supplier. | Covered |
| Art. 44 to 49 | Transfers outside the EEA | Transfer register tied to processing, with the safeguard for each recipient. | Covered |
| Art. 6, 7, 13, 14 | Legal bases and information duties | Balancing tests for legitimate interest, consent templates and records with proof, notices generated from register entries. | Covered |
| Art. 37, 39 | Cooperation with the authority | DPO details with appointment and notification dates, a log of questions to the DPO with answers, breach notification number and follow-up. | Covered |
| Art. 29, 32 | Security and access | Measures per processing activity and per DPIA risk, authorisations with history. No organisation-wide risk analysis. | In part |
| Art. 38, 39 | Monitoring and reporting | Readiness score with gaps, deadline dashboard, printable register. The report itself is yours to write. | In part |
| Art. 39 | Training and awareness | Iodynka does not run or record training. Authorisations show who has access to which data, so you know whom to train. | Outside |
Ordering takes one email.
Write to us and we reply with an offer and a data processing agreement. Iodynka is made by the team behind RealSec, the compliance platform for regulated companies in Poland.