What is GDPR — and why it's about your side project even if you're not in Europe

The usual reasoning: "GDPR is for European companies, I'm not in Europe, moving on." Understandable, and wrong.
GDPR looks at the user's location, not yours. And it says in its own text that being free doesn't save you. Your little site used by three people in Berlin is formally in scope.
What GDPR means in plain words
GDPR (General Data Protection Regulation) is the European regulation on protecting personal data, in force since 2018. Its idea in one sentence: the data belongs to the person, and you use it by permission and on the record.
Everything else follows. You must be able to say why you took the data, on what legal basis, who you passed it to, how long you keep it — and hand it over or delete it on request.
The big misunderstanding: it looks at the user, not at you
Scope is set by Article 3. The first part covers companies established in the EU. The second one catches everyone else, if they offer goods or services to people in the Union. The wording is literally: offering goods or services, "irrespective of whether a payment of the data subject is required".
In human terms: "but mine is free" is explicitly not an argument. The same article separately catches monitoring the behaviour of people in the EU — that is, ordinary analytics.
What this means for a solo dev:
- an English site with prices in euros and shipping to the EU → you're clearly offering services to Europeans;
- a side project in your own language, no mention of Europe anywhere, that someone in Prague stumbled onto → probably not; an accidental user isn't targeting;
- a free app with an analytics counter that you promoted in European communities → yes, you targeted them.
The line runs through intent, not through the flag in your footer.
What it actually asks for
The mass misconception is "GDPR is the cookie banner". The banner is a distant relative. The real requirements:
- A legal basis. You may process data only on one of six grounds: consent, performance of a contract, legal obligation, vital interests, public interest, legitimate interests. "It's convenient for me" isn't on the list.
- Transparency. You must tell the person up front who you are, why you're taking the data, on what basis, who you'll share it with and how long you keep it. That's the content of a privacy policy.
- Real consent, if consent is your basis. It has to be freely given, specific, informed and unambiguous. A pre-ticked box doesn't count — silence isn't consent.
- People's rights. See their data, correct it, delete it, take it away in a machine-readable form, withdraw consent. And withdrawing must be as easy as giving.
- Breach notification. A serious incident goes to the supervisory authority without undue delay — the reference point is 72 hours.
Fines: two tiers, and why the headline numbers aren't about you
Article 83 sets two ceilings. The lower one: up to €10 million or 2% of total worldwide annual turnover, whichever is higher. The upper one, for breaching the basic principles, consent and people's rights: up to €20 million or 4% of turnover, whichever is higher.
"Whichever is higher" is aimed at corporations, not at your app with a hundred users. For a solo developer the realistic path looks different: a user complaint, a letter from the supervisory authority, a demand to explain yourself, an order to fix it. Unpleasant, eats weeks — but it isn't millions.
Something else is riskier: payment providers, app stores and business customers ask about privacy long before any regulator does. A missing policy costs you deals far more often than fines.
What to do on your project today
- Write down what you collect. For real — by database fields and analytics snippets, not from memory.
- Write "why" next to each field. Anything with no answer, delete. Fastest possible risk reduction.
- List who the data goes to — hosting, analytics, mail, AI provider. That's your future policy section.
- Make account deletion a working button, not an email to support. That's half of the user's rights in one move.
Do I need a cookie banner?
Only if you set cookies the site works without: analytics, ads, external widgets. Strictly necessary cookies (login session, cart) need no consent. A "we use cookies, OK" banner with no choice is the worst option — annoying and legally useless at once.
I'm outside the EU — does GDPR reach me?
If you don't offer services to people in the EU and don't monitor their behaviour, no. But your own country probably has its own rules: many require a published data-processing policy and a filing with the regulator. We unpack the document side in privacy policy or terms of service.
If the user typed the data in themselves, isn't that consent?
No. Consent must be informed and specific: the person understands what they're agreeing to and why. A "leave your email" form gives you grounds to reply on that matter — not to add them to a newsletter and pass them to partners.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





