Five common issues, in symptom-to-fix format. If your problem is not here, email hello@dekimu.com with the steps to reproduce.
1. "Your business profile is missing: …"
Symptom. You press Generate draft and, instead of a draft, you see "Your business profile is missing:" followed by one or more fields.
Cause. miniterms only renders a document once your business profile has the details the document prints. Every document needs the entity name, registered address and contact email. Every document except the DPA also needs the website URL. The tax ID is needed when Spain is ticked under Jurisdictions, and always for the Terms of Service and the DPA. miniterms never fills a missing field with sample text.
Fix. Open Business profile, fill in the fields the message lists, save, and press Generate draft again. If your profile is end-to-end encrypted, unlock your vault first.
2. I want different wording than the generated text
Symptom. You want a clause worded differently, but generating again gives you the same text.
Cause. This is by design. Mode B builds the full document from your profile each time. miniterms has no editor for the generated text.
Fix. Either (a) capture the change you want in the business profile so the next generation produces it natively, or (b) download the Markdown (Download .md, or the ZIP on Publish & sync) and apply your edits in your own copy outside miniterms.
3. The cookie scanner missed cookies my site sets
Symptom. You ran the cookie scanner, but the draft Cookie Policy leaves out cookies you know your site sets.
Cause. The scanner is static: it fetches your page and parses its HTML without running JavaScript. Cookies that scripts set after the page loads — common with analytics and advertising tags — are not detected.
Fix. Add the missing vendors to the draft by hand before publishing, and update your consent tool's categories to match. Rescan whenever you add or remove a tracking script.
4. I can't find a cookie banner snippet to embed
Symptom. You are looking for a cookie banner or consent script to paste into your site, and the dashboard has none.
Cause. miniterms does not generate a cookie banner, banner script or consent snippet. It generates the Cookie Policy; the banner comes from your consent tool (a consent management platform, or CMP, or your own implementation).
Fix. Set up a consent tool that offers reject as easily as accept and a choice per category, publish your Cookie Policy on your own site (download it from Publish & sync), and link to it from the banner. The Cookie banner guide covers what the AEPD expects and how to keep the banner and the policy in sync.
5. Your Hub site footer has no policy links
Symptom. You published your Dekimu Hub site, but its footer does not link to your Privacy Policy or Cookie Policy.
Cause. miniterms does not host your documents. Hub reads the document URLs recorded in miniterms at the moment you publish your Hub site. If no URL was recorded, or you recorded it after publishing the Hub site, the footer has no link.
Fix. Publish the document on your own site, record its URL through the API (PUT /api/v1/publish), click Sync to Hub on Publish & sync, then publish your Hub site again.