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.
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
- A lawful basis for each use (Article 6). Processing is lawful only if at least one listed basis applies: the person's consent for one or more specific purposes; necessity for a contract; a legal obligation; vital interests; a task in the public interest; or legitimate interests. There is no basis called "we'd like to".
- Consent has conditions (Article 7). When consent is your basis, you must be able to demonstrate it; a consent request bundled into a broader declaration must be clearly distinguishable, intelligible, easily accessible and in clear, plain language; and the person must be able to withdraw it.
- Children (Article 8). For information society services offered directly to a child on the basis of consent, the processing is lawful where the child is at least 16; below that age it requires consent given or authorised by the holder of parental responsibility. Member states may set a lower age by law, but not below 13.
- Special categories (Article 9). Data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs or trade-union membership, plus genetic, biometric and health data, are prohibited by default and allowed only under specific exceptions.
- Security measures (Article 32). Controllers and processors must implement technical and organisational measures appropriate to the risk, including, as appropriate, the pseudonymisation and encryption of personal data.
- Records (Article 30). Controllers must maintain a record of processing activities - what you hold, why, who receives it. The duty formally exempts organisations with fewer than 250 employees, but only where their processing is unlikely to risk people's rights and freedoms, is occasional, and involves no special categories or criminal-conviction data. An app with ongoing user analytics is processing on a non-occasional basis, so the exemption rarely covers a running product.
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
- Consent flows that mean it. Optional tracking must be actually optional - declined means declined, including analytics and advertising SDKs.
- A privacy notice that matches reality. It must say what you collect, why, who receives it and how long you keep it - and it must be true, which means it tracks your actual SDKs and processors, not a template.
- Processor terms with vendors. Analytics, crash-reporting, email and hosting providers all touch user data; each needs appropriate contractual terms and each belongs in your disclosure.
- Start with minimization. Every field in your signup form and every analytics event should have an answer to "why do we need this?" Deleting what you cannot justify is the cheapest compliance work there is.
Related: safe handling of return URLs and our subscription lifecycle notes.
Sources
- Regulation (EU) 2016/679 (GDPR), consolidated text via EUR-Lex - Articles 3, 6, 7, 8, 9, 15, 17, 30 and 32 (verified 19 November 2026): https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679
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.