Security and privacy

How access is enforced, identity access and masking, sharing with external clients, encryption at rest and what it does not cover, the activity log, and the known gaps.

Survey data names real people. These pages describe how Joripo decides who may see and change what, what protects stored data, and, plainly, what is not yet protected or not yet proven. Where something depends on how a server is run (encryption at rest must be switched on by whoever runs the server), the page says so.

How access is enforcedOrganisations kept apart, roles checked on the server, sign-in protection, what the browser is told, and how uploads and submissions are handled safely.
Identity access and privacyMarking the questions that identify a respondent, what everyone without identity access sees instead, who has identity access, and the identity map.
Sharing a workspace with external clientsGiving a funder, a principal investigator's team or a partner access to one workspace, the roles a grant can have, and what a client can never do.
Encryption at restWhat Joripo seals on the server's disk and in its database, what it leaves plain and why, how it is switched on, and what it does not protect.
The activity logAn organisation's own audit trail: what is recorded, who can read it, filtering and downloading it, and what is never shown.
Known gaps and what is unverifiedThe open security and privacy gaps, stated plainly, and the parts of Joripo that have been built and tested but not yet proven in production.