Custom Links for Privacy Policy and Imprint

[l4rm4nd]

Selhosters running DocuSeal may want to provide links to a privacy policy, cookie policy and a general imprint.

Currently, none of such information is included when selfhosting DocuSeal. This may lead to legal problems if the software is used by third parties that are not made aware about those topics. I am living in the EU, where such things are mandatory to outline.

I propose a new feature that allows defining custom URLs to such documents. The Privacy Policy, Cookie Policy and Imprint links are then displayed in the footer of DocuSeal, if defined by the selfhoster.

Typically, I would recommend implementing those by setting environment variables.

[omohokcoj]

@l4rm4nd custom links and text can be added to the signing form in the field description.
For example you can add a checkbox field and put your privacy/imprint links in the field description.
Let me know if that's sufficient for your use case.

[l4rm4nd]

Hi @omohokcoj ,

many thanks for the feedback. That's a first good approach for adding privacy links and checkboxes into a fillable form itself.

My proposal would rather aim at the docuseal web application itself though. So if someone browses the root page, not via an unique form link from email or so, there should be a general privacy policy too.

So basically just two hyperlink placeholders someone can set. The root page and a signing page itself too would then display the links in the footer.

If someone questions how the docuseal website stores and handles data, the links would provide the necessary information. As on any other website via footer links to privacy policy, cookies etc.

To keep it simple, it would just be a hyperlink. No feature to put in real text, HTML or so. So selfhosters can point to another site (e.g. company homepage or so), which hosts the privacy policy etc.

I would like to keep the signable forms itself clean from such legal, required links etc.

[l4rm4nd]

Just referencing this, as it summarizes perfectly what I need and meant by this discussion:

#306