Skip to main content

Data Privacy and Anonymization - Article

Choose appropriate questionnaire identity, retention and consent controls. Distinguish hidden personal details from removed identifiers or deleted responses, and understand schedule anchors, exports and follow-up responsibilities.
Updated: 9 Nov 2026
8 min read

Summary

Questionnaires can collect information needed for an application, practical training arrangements, evaluation or contextual consent. Useful collection also requires deliberate decisions about who can see the information, how long it is needed and what happens when a person changes an optional consent answer.

Eurekos provides controls for hiding personal details, removing profile-linked identifiers or deleting responses. These are different operations. None automatically makes identifying free text, attached files, exported workbooks or emailed copies anonymous.

Use this article to:

  • Choose between identity hiding, identifier removal and response deletion
  • Configure an appropriate anonymization schedule and anchor
  • Explain the limits of anonymous distribution and anonymized reports
  • Plan consent changes, authorized exports and operational follow-up

Decide what the process genuinely needs

An application reviewer may need to identify and contact an applicant. A course designer investigating relevance may need only grouped responses. Asking both audiences for the same information creates unnecessary exposure and can undermine trust in an evaluation.

State the purpose, intended recipients and relevant data-handling expectations before collecting responses. Use only the information necessary for the process. Privacy controls support the organization's policy; selecting a product option does not by itself establish a lawful basis, valid consent or compliance with every applicable obligation.

If someone must investigate an individual concern, retain an appropriate identified follow-up route for the period actually needed. If the purpose is a candid survey, do not promise anonymity while asking for names, unique circumstances or identifying documents.

Understand the three anonymization cases

Open Course administration → Questionnaires, select the questionnaire or More → Edit, and enable Configure anonymization rule. Choose Anonymization case according to the intended outcome.

CaseEffect on questionnaire evidenceImportant limit
Hide personal details in analytics and reports (all data is stored)Hides respondent name and email details in the relevant analytics and exportsIdentity data remains stored. Disabling the setting can make it available again; this is not deletion
Anonymize user data only (answers are stored)Removes profile-linked name and email data while retaining answersAnswer text or files can still identify the person; retained answers are not automatically anonymous in substance
Anonymize user data and responses (all data is deleted)Removes the relevant questionnaire response data rather than retaining an answer recordDo not expect the deleted response to remain available for later analysis or individual follow-up
A submitted response branches to three data-handling outcomes: hide personal details while retaining all data, remove profile-linked identifiers while retaining answers, or remove the relevant questionnaire response data. Free text and separate exported or emailed copies require their own review.
Identity hiding retains data, identifier removal retains answers, and response deletion removes the answer record. Review identifying content and separate copies as well.

These controls concern questionnaire data. “All data is deleted” is not an instruction to delete the person's platform account, all learning history or every other business record. Equally, deleting response data is not the same as masking a name in a report template.

The identity-hiding case has priority over report customization: selecting name or email columns in a custom export does not override the questionnaire's setting. Individual respondent details are not available in the normal question-detail view when the relevant identity-hiding rule applies.

Configure the timing and the anchor

For identifier removal or response deletion, choose the available Anonymization type and the relevant anchor. These controls let you align retention with a submission or a scheduled training event rather than treating every questionnaire as the same lifecycle.

Timing choiceTypical useWhat to verify
Days after SubmissionRetain information for a defined follow-up period after each replyEnter the required day offset; each response has its own submission timestamp
At the time of SubmissionAvoid an intended retention period for identifiable response dataProcessing uses background jobs; do not promise a zero-delay technical deletion guarantee
Days before, Days after or At the time of Start date / End dateAlign retention with the relevant scheduled activity or moduleThe response must have a usable activity/module relationship and schedule
Specific dateUse a fixed campaign or review deadlineCheck the date, time and whether a fixed deadline fits later submissions

Start and End date anchors depend on the activity or module schedule. A form shared as a standalone URL has no activity schedule to resolve. An activity without a configured schedule also cannot supply the date. Use a submission-based or suitable fixed-date policy when that is the real process.

The anonymization timestamp is resolved from the applicable anchor when the response is submitted. Later changes to the activity's schedule do not automatically recalculate that stored timestamp. Anonymization then runs through background processing, so a due time and the moment a new report reflects it are not necessarily identical.

The identity-hiding case stores the data and has no equivalent deletion schedule. Choose it only when presentation-level restriction, rather than removal, is appropriate. Save the questionnaire and verify the intended result with an authorized test process before using a destructive retention policy with live responses.

An anonymous link is not an anonymization policy

More → Copy link supports sharing a questionnaire with people who are not signed in. That is a distribution route. It does not automatically prevent a respondent from entering a name, email, reference number or another identifying detail in the answers.

Likewise, a signed-in respondent's answer can have personal details hidden or identifiers removed according to the questionnaire's policy. Anonymous access, hidden identity and deleted data are therefore three different concepts. Explain the actual configuration rather than calling all three “anonymous”.

If you need to update a profile or perform identified follow-up, use an appropriate authenticated workflow. A self-entered name in a public form is not an authenticated link to a platform account.

Handle consent as a continuing process

Use Consent for a clearly described contextual agreement or permission, not as a generic substitute for an evaluation question. Configure required or optional status, the available answer presentation and any supporting documents. Explain what the person is agreeing to and separate unrelated purposes rather than bundling them into one unclear statement.

Users can review questionnaire Consent answers in My overview → Profile → Edit profile → Legal permissions, where required and optional answers are grouped. Optional consent answers can be changed there. This is different from changing the platform's general privacy policy or newsletter preference.

The Updated user consent answer - admin template is available under Settings → Email sending → Questionnaires. Review the applicable notification and recipient configuration, and assign responsibility for processing changes. A shared, monitored team inbox is usually more resilient than relying on one person's mailbox.

A changed consent answer is not proof that every resulting business action has happened. The responsible team must review the change and apply the appropriate operational response. Do not promise that changing an answer automatically removes an account, erases every response, reverses an enrollment or deletes previously exported files.

For the user's broader account controls, see Use Your Profile and Account Settings.

Protect the information outside the dashboard too

Inspect free-text prompts and file requests before promising anonymity. A learner can identify themselves in an improvement suggestion; an uploaded accreditation document may contain a name or personal reference. Identifier removal does not rewrite the content of those answers or sanitize documents.

Send an email with replies to submitter, where enabled, creates an email copy. Administrative feedback notifications can also contain answers. Decide whether these are appropriate for the information collected and who will receive them. See System Email Notification Overview and Email Sending for the wider email controls.

Apply the organization's access, retention and secure-handling rules to authorized exports and other copies. A later questionnaire rule does not recall an already downloaded workbook or an email delivered outside the reporting view.

Check what remains after anonymization

For training feedback, the system retains the fact that feedback was submitted even after anonymization. A respondent who already completed it is not treated as missing feedback merely because the answer data was anonymized; the normal missing-feedback prompt and reminders should not restart for that reason.

Review both a new export and the relevant analytics view after the applicable process has run. Check identity fields, answer availability and the intended follow-up period. A response that was deliberately deleted cannot be used later to explain a trend. Agree any legitimate evidence requirements before deleting the data, not afterwards.

Troubleshooting

ProblemWhat to check
Names are hidden but the data is still identifiableReview free text, files and distinctive details. Hiding name/email columns is not complete anonymization
A report customization does not restore namesThe questionnaire's identity-hiding rule takes priority over selected export columns
Scheduled anonymization does not run as expectedCheck the case, timing, required offset, usable schedule anchor and background-processing status
A URL survey never reaches its Start/End date ruleIt has no activity schedule to resolve. Choose a suitable Submission or fixed-date policy instead
An exported or emailed copy still contains informationApply the policy to that separate copy; dashboard settings do not recall it
Consent changed but the business process did notCheck the configured notification and named follow-up owner. Consent change is not a universal deletion or unenrollment action

FAQ