Document language

On the English pages, the free Privacy Policy, Terms, DPA and Cookie Policy generators write every document in English, whichever jurisdiction you pick, except Portugal, Poland, Sweden, Denmark, Finland and Norway: their documents are in Portuguese, Polish, Swedish, Danish, Finnish and Norwegian (bokmål) by default, and you can choose English instead. In the dashboard, a profile that includes Spain gets its Privacy Policy, Terms and DPA for Spain in Spanish; everything else is in English.

If you serve users in Spain and elsewhere in Europe, you will likely want your privacy policy in at least English and Spanish. miniterms generates each document in one language. Which one depends on where you generate it.

Why this matters

Spanish data protection authorities care that the information notice is intelligible to the data subject. For a service whose user base is largely Spanish-speaking, a policy available only in English may not meet this standard: [GDPR art. 12(1)] requires the information be provided "en forma concisa, transparente, inteligible y de fácil acceso, con un lenguaje claro y sencillo".

The same logic applies to your Terms of Service in B2C contexts — clauses presented only in a language the consumer is unlikely to understand are more easily challenged.

Which language you get

  • Free generators, English pages: the Privacy Policy, Terms, DPA and Cookie Policy generators write every document in English, whichever jurisdiction you pick.
  • Free generators, Spanish pages: the Privacy Policy, Terms and DPA for Spain and EU (generic) come out in Spanish, for Germany in German, for France in French and for Italy in Italian. The Cookie Policy comes out in Spanish for Spain and EU (generic), in German for Germany, in French for France and in Italian for Italy.
  • Free generators, German, French and Italian pages: the Privacy Policy, Terms and DPA come out in the page's language for EU (generic) and for the page's own country, and in the country's language for the other countries (Spanish for Spain, German for Germany, French for France, Italian for Italy). The Cookie Policy follows the same rule, except that for EU (generic) it comes out in English for now. The German Impressum, the French mentions légales and the Italian note legali are generated in their own language only.
  • Dashboard: if your business profile includes Spain, the Privacy Policy, Terms and DPA are generated for Spain in Spanish; otherwise, including a profile for Germany, France or Italy, for EU (generic) in English. The Cookie Policy drafted from a scan, and the other dashboard documents, are in English.

If you publish more than one language version on your own site, add a <link rel="alternate" hreflang="..."> pair to each page so search engines route users to the right version.

Translating to a third language

miniterms generates English, Spanish, German, French and Italian documents in the free generators, and only English and Spanish in the dashboard. If you need another language, the recommended path is:

  1. Generate the EN version (EU generic jurisdiction) as the source-of-truth
  2. Have a legal translator localize it (not a generalist translator — privacy law is full of terms of art)
  3. Keep the citation tags intact in the translated output

Do not run the policy through a generic machine translator and publish the result. Phrases like "lawful basis" do not map to a single target-language term automatically — a translator who has handled DPAs and consent flows will get this right.

What miniterms does NOT translate

The HTML comment at the top of the file is always in English, with a fixed format. This is intentional — it is a machine-readable marker, not user-facing text, and tooling that consumes it expects English.

Display on your site

If your site is bilingual, link to the matching language version from the corresponding language of your site. Most CMSes support <link rel="alternate"> and a language switcher. A pragmatic minimum: include both links in your footer, with the language name in that language ("English", "Español"), so a Spanish-speaking user can find the Spanish version even if they landed on the English page.