gdpria.eu
Data processing agreements, the register, the privacy statement and breach notification assistance — in plain language, with the legal articles included.
GDPR has applied since 2018 to virtually every business, including a self-employed person with a customer database in an accounting package. In practice, nothing usually happens until someone asks for it: a major customer wants to see a data processing agreement before signing, a tender includes a privacy questionnaire, or an email was sent to the wrong recipient and then the question suddenly arises how many hours are left.
gdpria was built for precisely those moments. No course and no advisory process, but the documents you need at that moment, a register you keep yourself, and a decision tree that calculates what you must do within which timeframe in the event of a data breach. Every statement is accompanied by the legal article it comes from, so you can check it and show it to someone else.
இது செய்வது
The data processing agreement
The agreement your customer wants to see from you, drawn up based on what you actually do — and the explanation of who is the processor in that relationship and who is the controller, because that's where things usually go wrong first when filling it out.
The processing register
What you process, why, on what legal basis and how long you keep it. This is the document that the Personal Data Authority requests first, and the only one with which you can demonstrate that you have an overview.
Breach notification assistance
Three time limits that are often confused: 72 hours to notify the Authority from the moment you discover it, inform those affected immediately if the risk to them is high, and always document it in your own register — even if nothing needs to be reported. The decision tree keeps them separate.
The privacy statement
The text for your website, built from what you actually process instead of from a template with placeholders in it.
The knowledge base
Nineteen topics with the article numbers included, from retention periods to AI in the workplace. What is stated is automatically checked against the official text on EUR-Lex, so a reference doesn't silently point to the wrong article.
யாருக்கு
- Self-employed persons and small businesses who have never done anything about it and now have a customer on the line asking for it
- Businesses that have just had a data breach and want to know if it needs to be reported and within what timeframe
- Entrepreneurs bidding for a contract that includes a privacy questionnaire
- Accountants and web builders who want to set this up for multiple clients
இது கண்டுபிடித்த போது
"Do I need to sign a data processing agreement", "notify breach within 72 hours", "processing register example self-employed" — questions that people type in at the moment it matters. In addition, a programmatic series per software package: what data is in it, what data processing agreement the provider offers and what you still need to arrange yourself. Dutch only: one language that is correct is worth more than eleven that say the same thing.
बडे प्रश्न
I am self-employed with five customers. Does this really apply to me too?
Yes, as soon as you process personal data — and a customer database with names and email addresses already counts as that. What does differ is the scope: below 250 employees there is an exception to the register requirement, but this ceases to apply as soon as you process non-incidentally or use special categories of data, and the latter is the case with most businesses. The knowledge base explains where you stand.
An email was sent to the wrong person. Do I need to report that?
That depends on what was in it and who received it. The decision tree goes through it with you and keeps the three time limits separate: notify the Authority within 72 hours of discovery, inform those affected if the risk to them is high, and always document it in your own register. The latter applies even if the answer to the first two is no.
Is this a replacement for a lawyer?
இல்லை. நாங்கள் ஆவணங்களையும் கட்டுரைகளுடன் விளக்கத்தையும் வழங்குகிறோம்; ஒரு சர்ச்சை, மேற்பார்வைக் கொள்கையின் விசாரணை அல்லது ஒரு அசாதாரண கட்டமைப்பின் விஷயத்தில் ஒரு வழக்குரைஞர் இதைப் பார்க்க வேண்டும். நாங்கள் அகற்றுவது என்பது ஒவ்வொரு நிறுவனமும் செய்ய வேண்டிய பகுதியாகும் மற்றும் இப்போது ஆயிரம் யூரோக்கள் நிகழ்த்தப்பட்டு வருகின்றன.
ஏன் எல்லா இடங்களிலும் கட்டுரை எண்கள் உள்ளன?
ஏனெனில் ஒரு கூற்று இல்லாமல் தேடக் கூட்டல் சரிபார்க்க முடியாது, மற்றும் நீங்கள் ஒரு வாடிக்கையாளர் அல்லது ஒரு மேற்பார்வைக் கொள்கையிற்கு ஏதோ அடிப்படையாக இருக்கும் இடத்தைக் காட்ட வேண்டும். கூடுதலாக, அவை ஆணை உரைக்கு எதிராக இயந்திரத்தால் சரிபார்க்கப்படுகின்றன, இதனால் ஒரு இடங்கோல் கட்டுரை வருடங்களாக நின்று இருப்பதற்கு பதிலாக தெரிய வருகிறது.
இந்த மঞ்சம் எப்படி கட்டப்பட்டுள்ளது
Theos Group இன் ஒவ்வொரு தளத்தையும் போல: ஒரு ஒற்றை பகிர்ந்த அடிப்படையில், தன்சார்பு நிர்வாகத்தில், ஒரு சொந்த தானியங்கு நிர்வாகியுடன் — இங்கே GELOS — நாள்தோறும் சுழற்சிகளைத் திருப்புகிறது, தகராறுகளைப் புகாரளிக்கிறது மற்றும் நாள் அறிக்கையை எழுதுகிறது. நாங்கள் ஒரு அமைப்பில் கற்றுக்கொள்வது, அடுத்த வாரம் மற்ற அனைத்தக்கிலுமே இருக்கிறது.