Privacy law is not static. The EDPB publishes new guidelines, the AEPD updates its cookie guide, and occasionally an article-level GDPR amendment lands. miniterms tracks these changes for you and tells you when it is time to regenerate.
What miniterms tracks
We monitor four sources daily and surface changes in the dashboard:
- EUR-Lex — for amendments to the GDPR itself or new EU instruments that touch personal data
- BOE — for changes to the LOPDGDP, accounting law, or other Spanish statutes referenced by your output
- EDPB — for new or revised guidelines
- AEPD — for new circulars and revisions to the official guides (especially the cookie guide)
When a change lands that affects citations in your generated documents, a banner appears in the dashboard with the affected document types and a one-click regeneration button.
When to regenerate vs. amend by hand
- Regenerate when the change is upstream — a new EDPB guideline, an AEPD circular update, a BOE amendment to LOPDGDP. The clauses tied to that source need to reflect the new language; the safest path is a full regeneration from your unchanged profile.
- Amend by hand only when the change is to your business (new product, new sub-processor, new processing purpose) and is small enough that you do not want to re-publish. Even then, ask yourself whether the next regeneration will overwrite your edit — it will. Hand-edits do not survive a regenerate.
If you have hand-edited clauses and the dashboard prompts you to regenerate, the prompt will list the clauses that will be overwritten. Read that list before pressing the button.
The update history page
Every regeneration creates a new entry in Documents → History. Each entry records:
- The timestamp of the regeneration
- The jurisdiction at the time of generation
- The citation set version (a hash of the regulator citation list that was applied)
- A diff link to the prior version
This page is your accountability evidence. If an auditor asks "what version of the cookie guide informed your policy on date X?", the history page answers directly — citation set hash plus its publication date.
When a regeneration is required vs. recommended
Most updates are recommended — the change clarifies wording or adds an example, and your existing policy is not wrong. Some updates are required:
- Required — the citation set bumped a required clause type (new disclosure obligation, new retention rule that conflicts with your prior text). These flow with a red banner.
- Recommended — clarifications, footnote-level updates. Yellow banner.
The dashboard will not auto-regenerate, ever. The decision is yours, and the timing matters: regenerating creates a new "last reviewed" date on the published document, which is itself a signal to your users and to regulators.
Citations and their versioning
The citation set itself is versioned. Each generated document records the citation set hash in a hidden HTML comment (<!-- miniterms citation-set: <hash> -->) and in the JSON-LD export. This means an auditor can reconstruct exactly which regulator state your policy responded to, even years later.
If you want to manually re-trigger the daily check — for example after seeing AEPD news on a Friday — there is no API for that today. The check runs once per day from our side.