OOmnistu

Blog / Security

Security

GDPR basics for a small business app: the obligations that bite first

Lawful basis, minimization, real consent and vendor terms - what the GDPR expects from companies established in the EU or offering services to people there.

OOmnistu
Reviewed 2026-11-19 · 4 min read

If your company is established in the EU, or your app or site offers goods or services to people in the EU or monitors their behaviour there, the GDPR applies to what you collect, why you collect it and how long you keep it - wherever the processing physically happens. The obligations are manageable for a small business, but they are not optional, and "we're too small" is not one of the exemptions.

This guide covers the working basics from the regulation itself (Regulation (EU) 2016/679, the GDPR, via EUR-Lex), checked against the official consolidated text on 19 November 2026. It is orientation, not legal advice; a qualified adviser should review your specific data flows. Note that the UK operates its own post-Brexit data protection regime, which this guide does not cover.

The starting point: what counts as personal data

Personal data is any information relating to an identified or identifiable person - names and emails, but also device IDs, IP addresses, location history and behavioral profiles. Analytics IDs and advertising identifiers count, which is why "we only collect analytics" is rarely true in the way teams hope.

Who the regulation reaches (Article 3)

The regulation applies to processing in the context of an establishment of a controller or processor in the Union, regardless of where the processing takes place. It also applies to controllers and processors not established in the Union when they process data of people in the Union in connection with offering them goods or services (paid or free), or monitoring their behaviour as far as that behaviour takes place within the Union. A US startup with an EU user base can therefore be in scope even with no EU office.

The obligations that bite first

User rights you must be able to serve

Article 15 gives people the right to confirmation of whether you process their data and access to it; Article 17 gives the right to erasure ("right to be forgotten") without undue delay when its conditions apply. Practically: you need a way to find one person's data across your database, backups and third-party tools, and to delete it when required.

What this looks like inside an app or website

Related: safe handling of return URLs and our subscription lifecycle notes.

Sources

Drafted with AI assistance from this source. Data protection obligations depend on your data flows, markets and scale; this is general orientation and not legal advice - have a qualified professional review your implementation. The UK has a separate regime (the UK GDPR and Data Protection Act 2018) not covered here.