GDPR and CCPA for Small Websites: A Plain-English Compliance Checklist
If your website uses analytics, ads, forms or a newsletter, privacy laws probably apply to you. This checklist explains the GDPR and the CCPA in plain English and the practical steps most small sites need.
Updated November 17, 2026 · 4 min read
Privacy laws are no longer just for big corporations. If your website collects names, email addresses, IP addresses or uses cookies for analytics and advertising, you are processing personal data. Two of the most influential laws are the EU’s General Data Protection Regulation (GDPR) and California’s Consumer Privacy Act (CCPA), as amended by the CPRA. Many other countries and US states now have similar rules.
- The GDPR can apply to businesses outside the EU if they offer services to, or monitor, people in the EU.
- Most small sites need an accurate privacy policy, a lawful cookie consent setup, secure forms and a way to handle data requests.
- Know which third-party tools collect data on your site, and sign data processing agreements with them.
This is a practical overview, not legal advice. For specific questions, especially if you handle sensitive data, consult a privacy professional.
Does the GDPR apply to you?
The GDPR applies to organisations established in the EU and also to organisations elsewhere that offer goods or services to people in the EU, or monitor their behaviour, for example through tracking cookies. The UK has its own almost identical version, the UK GDPR. Size does not exempt you, although some record-keeping duties are lighter for small organisations.
Does the CCPA apply to you?
The CCPA applies to for-profit businesses that do business in California and meet at least one threshold: annual gross revenue above a set amount (adjusted periodically for inflation), buying, selling or sharing the personal information of 100,000 or more California consumers or households, or making half or more of annual revenue from selling or sharing personal information. Many small websites fall below these thresholds, but other US state laws have different thresholds, and good privacy practice builds trust regardless.
Also readHow Small Businesses Can Use AI Tools Safely: A Practical PolicyThe checklist
1. Map the data you collect
List every way your website collects personal data: contact forms, newsletter sign-ups, accounts, checkout, comments, analytics, advertising tags, chat widgets, embedded videos and social media buttons. For each, note what data is collected, why, where it goes and how long it is kept.
2. Know your legal basis (GDPR)
Under the GDPR, you need a legal basis for each use of personal data. Common ones are consent (for example, for marketing emails or advertising cookies), contract (to deliver an order), legal obligation (such as keeping tax records) and legitimate interests (for some security and analytics uses, balanced against people’s rights).
3. Get cookie consent right
In the EU and UK, non-essential cookies and similar trackers, such as those used for analytics and advertising, generally require prior consent. A compliant consent banner should:
- Block non-essential cookies until the visitor agrees
- Make rejecting as easy as accepting
- Explain the purposes clearly and let visitors choose by category
- Let visitors change their mind later
- Record consent
If you use Google advertising products for visitors in the EEA, the UK and Switzerland, Google requires a certified consent management platform that integrates with its consent framework.
4. Publish a clear privacy policy
Your privacy policy should explain who you are, what data you collect, why, your legal bases, who you share data with, international transfers, how long you keep data, people’s rights and how to contact you. Under the CCPA, covered businesses must also explain the categories of personal information collected and whether it is sold or shared, and offer a “Do Not Sell or Share My Personal Information” option where relevant.
5. Sign data processing agreements
Your hosting provider, email marketing platform, analytics tools and payment processors process data on your behalf. Under the GDPR you need a data processing agreement with each one. Most major providers offer standard agreements that you can accept in your account settings.
6. Handle international transfers
If personal data from the EU is transferred to countries without an EU adequacy decision, you need safeguards such as standard contractual clauses. For transfers to the US, companies certified under the EU-US Data Privacy Framework can receive data on that basis.
7. Respond to data rights requests
People can ask to access, correct or delete their data, and under the GDPR also to object to processing or receive their data in a portable format. The GDPR generally requires a response within one month. Set up a simple process: a contact email, identity verification and a checklist of where data is stored.
8. Secure the data
Use HTTPS, keep your website software and plugins updated, use strong passwords and two-factor authentication for admin accounts, limit who can access data and delete what you no longer need.
9. Plan for breaches
Under the GDPR, a personal data breach that poses a risk to people must generally be reported to the supervisory authority within 72 hours of becoming aware of it, and people must be told if the risk is high. Many US states also have breach notification laws. Know who to call before it happens.
Quick summary
| Task | GDPR | CCPA |
|---|---|---|
| Privacy policy | Required | Required for covered businesses |
| Cookie consent before tracking | Required for non-essential cookies | Opt-out of sale or sharing |
| Data subject requests | Access, correction, deletion and more | Know, delete, correct, opt-out |
| Processor contracts | Data processing agreements | Service provider contracts |
| Breach notification | 72 hours to authority, where required | State breach laws apply |
Privacy compliance is an ongoing habit, not a one-time task. Review your tools and policy at least once a year and whenever you add a new service to your website.
This article is independent, general information and is not legal, financial or security consulting advice. Product features and prices change often, so check the vendor's current documentation before you buy or change your systems.





