GDPR (EU) · Platform guide
Privacy policy for SaaS and web apps
A SaaS or web app that collects account data needs a privacy policy. For EU users, GDPR Article 13 lists what to tell people when you collect their data: who you are and how to contact you, the purposes and legal basis, recipients such as subprocessors, how long you keep data, and their rights.
What GDPR (EU) requires
Article 13 — Information to be provided
“the identity and the contact details of the controller and, where applicable, of the controller’s representative”
Source: gdpr-info.eu verified 2026-10-30
What common SDKs collect
| SDK / API | Data it collects | Source |
|---|---|---|
| Google Analytics |
| Source: marketingplatform.google.com |
| Stripe (payments) |
| Source: stripe.com |
Everything in this table must appear in your policy if the SDK ships in your build.
Where to put the URL
- 3.1Site footer on every page, and on sign-up and checkout screens.
- 3.2Link it from your Terms of Service and Cookie Policy.
Sample clause
§ 4.1 · Subprocessors
We use trusted service providers (subprocessors) to run the service: our cloud host stores your account data, Stripe processes payments, and our email provider sends account emails. They process data only on our instructions. The current list is at /subprocessors.
Questions
- Does a SaaS need a privacy policy and terms?
- A privacy policy explains data handling; Terms of Service set the rules of use. Most SaaS products publish both, and many add a Cookie Policy.
- What is a subprocessor?
- A third-party service that processes personal data on your behalf, such as hosting, email or payments. GDPR Article 13 asks you to name recipients or categories of recipients.