The eight most-reported issues, in symptom-to-fix format. If your problem is not here, email hello@dekimu.com with the steps to reproduce.
1. "Generation failed — missing jurisdiction context"
Symptom. You press Generate and get an error mentioning missing jurisdiction context.
Cause. Your business profile does not have a country of establishment set, or the country is set to one that maps to a jurisdiction we do not yet ship (anything outside Spain/EU/UK).
Fix. Open Business profile, set the country, save. If your country is not Spain, EU member, or the UK, use EU as the closest fit for now and add a local-counsel-reviewed layer on top.
2. Regenerating broke my custom edits
Symptom. You hand-edited a clause in the dashboard editor, regenerated, and the edit is gone.
Cause. This is by design. Mode B regenerates the full document from your profile each time; manual edits do not survive a regeneration. The dashboard warns about this before the regenerate runs.
Fix. Either (a) capture the change you want in the business profile so the next generation produces it natively, or (b) export the generated HTML and apply your edits in your own copy outside miniterms. There is no "hand-edit mode" in miniterms today.
3. AEPD circular updated but my doc didn't change
Symptom. You saw the AEPD publish an update last week, but your generated policy is unchanged.
Cause. Either the AEPD change has not been incorporated into our citation set yet (we update daily, with a small lag for review), or the change does not affect any clause that applies to your profile.
Fix. Check Documents → History. If the latest entry has the same citation set hash as before the AEPD change, the change is still propagating. If the hash changed but your content is identical, the change does not apply to your processing.
4. Cookie banner not appearing on my site
Symptom. You embedded the banner snippet but no banner appears.
Cause. Usually one of: snippet placed after another tag manager that intercepted it, Content Security Policy on your site blocking inline scripts, or the snippet was pasted in <body> instead of <head>.
Fix. Move the snippet to the top of <head>, before any other scripts. If your CSP blocks inline scripts, add https://miniterms.com to your script-src directive. Test in an incognito window with no cached consent record.
5. Cookie banner shows in the wrong language
Symptom. Your site is in Spanish but the banner shows in English (or vice versa).
Cause. The banner reads its language from your business profile's default language, not from your site's <html lang> attribute.
Fix. Open Cookie banner → Settings → Language. You can either pin a single language or set it to "auto-detect from page lang", which reads document.documentElement.lang at runtime.
6. "DPA generator unavailable" on paid tier
Symptom. You upgraded but the DPA tab still says "upgrade required".
Cause. Stale entitlement cache. Hub has acknowledged your payment but miniterms has not yet refreshed the entitlement.
Fix. Sign out and back in. The new sign-in pulls a fresh entitlement from Hub. If the issue persists past one sign-out, email support — there is a known edge case where Stripe's confirmation webhook is delayed beyond the cache TTL.
7. Published slug returns 404
Symptom. Your miniterms.com/p/<slug> URL returns 404 immediately after publishing.
Cause. Publishes take a few seconds to propagate to the edge CDN. If 404 persists past a minute, the publish step did not complete server-side.
Fix. Go back to the editor and press Publish again. If you see an error, look at the dashboard event log (Settings → Activity) for the failure reason. Most common: required profile fields are missing (the publish step re-validates).
8. Custom domain not resolving
Symptom. You configured legal.yoursite.com to point to miniterms, but visiting it returns a TLS error or a blank page.
Cause. Either the CNAME has not propagated, or the certificate has not been issued yet.
Fix. From your terminal: dig CNAME legal.yoursite.com — confirm it points to the value miniterms gave you. From the dashboard: open Settings → Custom domain and check the certificate status. Certificate issuance usually completes within 5 minutes of CNAME propagation; if it has been more than 30 minutes, email support.