summaryrefslogtreecommitdiff
path: root/docs/content/guides/providing-terms.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/content/guides/providing-terms.md')
-rw-r--r--docs/content/guides/providing-terms.md25
1 files changed, 25 insertions, 0 deletions
diff --git a/docs/content/guides/providing-terms.md b/docs/content/guides/providing-terms.md
new file mode 100644
index 00000000..54a792f6
--- /dev/null
+++ b/docs/content/guides/providing-terms.md
@@ -0,0 +1,25 @@
+# How to set up your terms of use
+
+## Setup your terms of use
+
+To setup your terms of use, you need to provide a document called `terms-of-use.md` which contains them. Of course written in Markdown.
+
+It has to be provided under `./public/docs/` and will be automatically turned into a HedgeDoc document. It will also automatically updated as soon as you change the document on disk.
+
+As soon as the file exists a link will show up in the bottom part along with the release notes and link to them.
+
+## Setup your privacy policy
+
+To add a privacy policy you can use the same technique as for the terms of use. The main difference is that the document is called `privacy.md`.
+
+See our example file `./public/docs/privacy.md.example` container some useful hints for writing your own privacy policy.
+
+As with the terms of use, a link to the privacy notices will show up in the area where the release notes are provided on the index page.
+
+## Setup your imprint
+
+To add an imprint you can use the same technique as for the terms of use. The main difference is that the document is called `imprint.md`.
+
+It has to be provided under `./public/docs/` and will be automatically turned into a HedgeDoc document. It will also automatically updated as soon as you change the document on disk.
+
+As with the terms of use, a link to the imprint will show up in the area where the release notes are provided on the index page.