Jurisdiction-matched language output

Documents are generated in the language of the selected jurisdiction: Spain produces Spanish, Germany produces German and EU (generic) produces English. Other languages are not offered yet.

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, set by the jurisdiction in your business profile.

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

The output language follows the jurisdiction in your business profile; Spain produces Spanish. Germany produces German, and EU (generic) produces 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 does not generate French or Italian output today. If you need a third 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.