Keep the distinction clear — this notice belongs to one survey and is supplied or approved by your organization. It does not replace the Dayalogs platform Privacy Policy, cookie preferences or your own legal review.
When to use a survey notice
Add one when respondents need to read and accept project-specific wording before taking part: for example, the identity of the data controller, the purpose of the research, retention terms or a link to the customer's full policy.
Do not ask an AI assistant to invent legal terms. Start from wording supplied or approved by the responsible organization, and retain its policy version or date when one exists.
What respondents see
The survey intro displays an acceptance checkbox and a button that opens the notice. The respondent cannot start until they accept it.
- The notice can have its own title, acceptance wording and link label.
- The body supports a restrained Markdown format: paragraphs, headings, lists, bold, emphasis and HTTPS links.
- Dayalogs sanitizes the rendered content; raw HTML and unsafe link targets are not trusted.
- Each supported survey locale can present approved localized wording.
How it relates to email questions
One accepted survey-level notice also covers an email question in that survey, so Dayalogs does not show a second consent checkbox beside the email field.
If the survey-level notice is removed, email questions return to their field-level consent fallback. Removing a notice therefore changes the respondent experience and should always be an explicit decision.
Languages and personalized wording
Translate the notice together with the questionnaire and preview every supported locale. Variables such as a customer or company name may be inserted at runtime; their values are escaped as plain text and cannot introduce their own Markdown or HTML.
Changing the notice creates a new survey version. Existing responses keep their original evidence rather than being rewritten with the latest wording.
What Dayalogs records
When a response is submitted, Dayalogs stores the exact notice they accepted: timestamp, locale, policy version, title, Markdown, sanitized HTML and a content hash.
The acceptance is bound to the wording rendered for that respondent attempt. If a runtime variable changes before submission, it cannot replace the notice the respondent actually saw.
This immutable acceptance snapshot remains available in JSON and NDJSON response exports. It records what Dayalogs displayed and accepted; it is not a substitute for deciding the appropriate legal basis or wording.
A safe authoring workflow
- Obtain the approved wording and its policy version or date.
- Add the complete notice through survey JSON or an MCP-compatible assistant.
- Preview its formatting, HTTPS links, variable substitutions and every locale.
- Have a responsible person approve the rendered wording before publication.
- After publishing, use a controlled public link to confirm that Start remains disabled until acceptance.
An MCP assistant must not invent or silently rewrite legal wording. It should preserve the complete approved notice, show the preview for human review and remove it only after an explicit request.