Data processing
A summary of how the operator processes personal data for the organizations that use wrkflow, in the terms a data protection review looks for. To sign a data processing agreement, write to the operator; it follows what is described here.
Last changed 14 October 2026
1. Roles
The organization is the controller of the personal data it puts into wrkflow, and the operator is its processor. The operator is the controller only of the account, billing and technical data described in the privacy page.
2. What is processed, and for whom
- Purpose: to provide wrkflow: building surveys, sending invitations, collecting and analysing responses, follow-ups, dashboards and exports, and the account and security controls around them.
- People: the organization’s members, its contacts and participants, and the respondents who answer its surveys.
- Data: names, email addresses and phone numbers, contact attributes the organization defines (department, location and so on), survey answers, response times, language, device type, files respondents upload, and the audit log. The organization decides what to ask; it is responsible for asking only what it has a lawful basis for.
3. Instructions
The operator processes the data only on the organization’s documented instructions, which are what the organization does in wrkflow and what it agrees in writing, and tells the organization if it believes an instruction breaks the law. People with access to the data are bound to confidentiality.
4. Security measures
Organization and role based access with row level security in the database, two-factor authentication, single sign-on and provisioning for those who need them, session and network policies an organization can set, an audit log, rate limiting on public pages, and encryption of answers to questions marked sensitive. The full description is on the security page.
5. Subprocessors
The organization agrees to the use of the subprocessors listed on the security page, which describes what each does and receives. The list is kept in step with how this deployment is set up; a change that adds a subprocessor is announced to organizations before it starts, and an organization that objects may end its use of wrkflow.
6. Where data is stored
The storage region is set by the operator of this deployment and stated here once it is.
7. Requests from people
Administrators can look up everything held about a person, export it and erase or anonymize it from within wrkflow, and each action is recorded. The operator passes on any request it receives directly from a person to the organization concerned and helps the organization answer within the time the law gives.
8. Personal data breaches
The operator tells the organization without undue delay after becoming aware of a breach affecting its data, with what is known, what has been done and what the organization may need to do.
9. Return and deletion
During the subscription the organization can export its data and set how long responses are kept. When an organization is deleted, or the agreement ends, its data is deleted; backups age out on their own schedule. Data the law requires the operator to keep is kept only for that purpose.
10. Evidence and audits
The operator gives the organization the information needed to show compliance with these terms, including the security documentation on request, and allows reasonable audits by the organization or an auditor it names, with notice and without harm to other organizations’ data.