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 both in one pass from a single profile, and keeps them in lock-step when you regenerate.
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 is not compliant with [BOE LOPDGDP art. 11], which requires the information be provided "de forma concisa, transparente, inteligible y de fácil acceso, con un lenguaje claro y sencillo". The AEPD has cited language accessibility in enforcement actions before.
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.
How EN+ES generation works
When you press Generate in the dashboard, miniterms produces both EN and ES outputs simultaneously from the same business profile. The two outputs:
- Use the same citations with the same article numbers.
[GDPR art. 13]appears identically in both (we do not localize the citation tag, because the underlying instrument is the same). - Use jurisdiction-correct local terminology. In the ES output, GDPR is referred to as "RGPD" in body text. LOPDGDP is named in full as
Ley Orgánica 3/2018, de Protección de Datos Personales y Garantía de los Derechos Digitales. - Render to the same structural sections, in the same order, with the same headings — translated.
This means a reader cross-referencing the two languages can rely on the structure as a navigation aid: section 4 in English is section 4 in Spanish.
Synchronization on regeneration
When you regenerate (because your profile changed, or because the citation set updated), miniterms re-generates both languages. There is no path where you can have a policy that is current in English but stale in Spanish — the two are always generated as a pair from the same profile and the same citation set.
If you publish both to Dekimu-hosted slugs, the two slugs share a <link rel="alternate" hreflang="..."> pair so search engines and accessibility tools route users to the right version.
Translating to a third language
miniterms does not generate French, German, or Italian output today. If you need a third language, the recommended path is:
- Generate the EN version as the source-of-truth
- Have a legal translator localize it (not a generalist translator — privacy law is full of terms of art)
- 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. Likewise the JSON-LD sidecar keys are English (per the JSON-LD convention).
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.