miniterms generates your documents; it never hosts the canonical copy. Your own site is always where the live policy lives. There are two publish flavors, both on Publish & sync in the dashboard.
Option 1 — Download ZIP (host anywhere)
Click Download ZIP. The archive holds your latest saved Privacy Policy, Terms, Cookie Policy and DPA drafts as Markdown files (drafts/<type>-<version>.md), the Cookie Policy from your last scan, your business profile, the publish record and a README. Paste the Markdown into your CMS, or convert it to your site's format, and publish it on your own domain.
Pros:
- Your policy lives on your domain — same brand, same TLS certificate
- No third-party dependency in the critical path
- Works offline, in air-gapped reviews, in vendor due-diligence packets
Cons:
- You are responsible for re-publishing when you regenerate. miniterms cannot push updates to your site.
- Keep the provenance comment at the top of each draft that carries one — that is your machine-readable provenance trail.
Option 2 — Dekimu Hub sync
For Dekimu Hub customers. Click Sync to Hub and miniterms records the current version of every document as your published baseline. When you publish your Hub site, its footer links to the document URLs recorded in miniterms; you record those URLs through the API (PUT /api/v1/publish). The documents themselves still live wherever you host them.
What about embedding the policy in your app?
miniterms does not offer an embed, an iframe or a public render API. If your app fetched the policy at runtime, your accountability trail would depend on miniterms being up, which is not a property you want for a legally required disclosure. Host the document yourself and link to it.
What "canonical" means
The canonical home of the legal document is your own site. Link to it from your site footer so visitors can find it.