Assentics provides privacy-oriented controls for research workflows, but each study still needs its own controller decision, participant notice, legal basis, retention plan, and review process.
Before launch
Confirm these points before you invite participants:
who is the study controller and privacy contact,
what data you need and which fields can be avoided,
whether the study may collect health, wellbeing, mental-health, or other sensitive information,
how long participant records, survey responses, exports, logs, and messages should be kept,
who is allowed to access the project and export responses,
where participants can send rights or withdrawal requests.
During the study
Use the least identifying onboarding method that fits your protocol. A public survey link is convenient but can be forwarded. An invitation code gives more control, especially when each participant should be known to the study team.
Avoid putting sensitive information in project names, invitation labels, email subjects, or free-text operational notes.
After collection
Review exports, retention, participant removal, and rights requests as operational tasks. Raw exports can contain identifiable or sensitive response data, so handle them outside Assentics only when there is a clear study purpose.