Jurisdictions — Spain and the EU

What each jurisdiction adds, how to choose when you serve more than one, and how RGPD differs from GDPR proper.

miniterms supports two jurisdictions in the dashboard today: Spain and EU. The free public generators on miniterms.com also offer a Germany version (GDPR + BDSG). Each jurisdiction ships its own regulator citation set, and the right choice is determined by where you are established — not where your users live.

Spain

The Spain set is the largest. It includes:

  • The General Data Protection Regulation, Regulation (EU) 2016/679, in full
  • Ley Orgánica 3/2018, de Protección de Datos Personales y Garantía de los Derechos Digitales — LOPDGDD, BOE-A-2018-16673
  • AEPD circulars and guidance referenced from the Agency's "Documentos" library
  • The cookie-specific guidance from the AEPD's "Guía sobre el uso de las cookies" (current edition)
  • Spanish accounting / commercial law minimums (Código de Comercio art. 30) for retention of billing records

Pick Spain if your business is incorporated in Spain, regardless of where your customers are. The LOPDGDD layers Spain-specific obligations on top of the GDPR — for example its own 14-year threshold for minors' consent ([BOE LOPDGDD art. 7]).

A note on terminology: in Spanish, the GDPR is called RGPD (Reglamento General de Protección de Datos). Same instrument, same article numbers, same paragraphs. The Spanish output uses RGPD; the English output uses GDPR. Citations point to the same EUR-Lex URL either way.

EU

The EU set is Spain minus the LOPDGDD-specific layer and minus the AEPD-specific guidance. It includes the GDPR in full, the EDPB common guidelines, and the e-Privacy Directive (2002/58/EC, as amended by 2009/136/EC) for cookie obligations.

Pick EU if you are established in any EU or EEA member state other than Spain. The EU output is appropriate for an Italian, German, French, Irish, or Dutch controller. It will not include AEPD-specific clauses, and the citations will not include BOE references.

If you operate from a country with its own national transposition (e.g. Germany's BDSG, France's Loi Informatique et Libertés), you may want to take the EU output and have local counsel add the national layer. Apart from the Germany version of the public generators, miniterms does not generate those national layers today.

Not supported yet

miniterms does not cover the UK GDPR or US state privacy laws such as the CCPA. The business profile lists UK GDPR and CCPA as coming soon, and you cannot select them yet. If you are established in the UK, or you need CCPA disclosures, the Spain and EU outputs are not written for your regime.

I serve users in several countries — which do I pick?

You pick the country where your business is established (registered office, principal place of business). The GDPR's one-stop-shop mechanism means your lead supervisory authority is the one in your country of establishment, regardless of where your users are. So a Spanish SL serving customers across the EU still has a Spanish-led regulatory posture and should use the Spain jurisdiction.

There is one exception: if you have specific operations in another EU country — say, a German branch with German employees — you may have local obligations there. miniterms does not handle multi-establishment controllers today; if that is you, generate the primary country and ask counsel to layer the secondary obligations.

Switching jurisdictions later

You can switch jurisdictions in the dashboard at any time. Switching does not change a draft you already saved; the next time you generate and save, that draft is replaced, because miniterms keeps only the current saved draft of each document. Keep the copies you published if you need the old version. Customers who already saw the old version are not retroactively affected; the change applies from the publish date forward.