Data retention, deletion and export
| Task | Who | Where |
|---|---|---|
| Set how long finished sessions are kept | Owner, admin | Settings > Data retention |
| Export the whole workspace | Owner, admin | Settings > Export workspace data |
| Delete one session | Owner, admin, creator | The session's results page > Delete this session |
| Erase one participant | Owner, admin, creator | Workspace API |
| Delete the workspace | Owner | Settings > Delete this workspace |
| Delete your account | Anyone signed in | Settings > Delete your account |
Every deletion is permanent. There is no recycle bin.
Retention
Keep finished sessions for (days), on the Settings page. Finished sessions older than this are deleted automatically, with every answer in them.
- 0 keeps everything, and is the default. Silently deleting results is a worse surprise than keeping them.
- Otherwise from 1 to 3650 days (ten years).
- The clock runs from when a session ended. A long survey is not deleted while it is still collecting, and one late visitor cannot extend everyone's data.
- Sessions that are still open are never deleted, because people may still be answering. A session left open is therefore never removed by retention: close sessions when they are done.
- A sweep runs hourly and works through old sessions in batches, oldest first, so switching retention on in a workspace with years of history is caught up over several hours.
- Each deletion is recorded in the audit log with the reason "retention", and so is every change to the setting.
What deleting a session removes
Its responses, submissions, board posts and votes, live tallies, its event history, more-time requests, its email invitations and their outcomes, its participants and teams, and the webhook events about it - including any not yet delivered, because an outcome about deleted data cannot be reported truthfully.
Erasing one participant
The basis for a request to erase a person's data. It is done through the workspace API,
DELETE /api/v1/sessions/<session id>/submissions/<submission id>/participant, and addressed by
submission - the identifier the results export shows - rather than by a participant identifier,
which would let someone link several submissions to one person.
Erasure removes the participant's answers and takes them out of the totals, removes their votes on others' posts, and deletes their own posts, since free text is what identifies people.
In an anonymous session nobody in the workspace can tell which submission is whose. That is the anonymity working: such a request can only be honoured if the person can identify their own submission. Retention and session deletion still remove the data wholesale.
Exporting the workspace
Download export produces workspace-export.zip:
| File | Contents |
|---|---|
manifest.json | Format version, export time, session count, and a note on what is excluded. |
workspace.json | Name, kind, retention setting and other workspace settings. |
members.json | Each member's email, name, roles and status. |
activities.json | Every activity with its versions, questions and options. |
sessions.json | Every session's settings, privacy mode, team settings and counts. |
sessions/<id>/responses.csv | That session's answers, one row per answer. |
sessions/<id>/contributions.json | That session's board posts. |
audit_log.json | The workspace's audit trail. |
Privacy carries into the file. Answers and board posts go through the same rules as everywhere else, so anonymous sessions stay anonymous: an administrator is still "the creator" as far as an anonymous session's promise is concerned. Team member lists are never included.
Left out on purpose: secrets of every kind (integration, webhook, identity provider, SCIM), API key hashes, participant tokens and identifiers, and email invitation addresses, which appear only as counts.
Each export is recorded in the audit log.
Deleting the workspace
Only an owner can, and they must type the workspace's name to confirm. Every activity, session, response, setting and integration in it is deleted, including its audit trail, and everyone is removed from it. Members' accounts are not deleted. Download an export first if you need a copy.
Deleting your account
Anyone can delete their own account from Settings, typing their email address to confirm.
- It is refused, before anything changes, if you are the only owner of a workspace that has other members. The message names the workspaces.
- Workspaces where you are the only member are deleted.
- You are removed from shared workspaces. Activities and sessions you made there stay, without your name on them - they belong to the workspace, and colleagues depend on them.
- Every audit entry naming you, in every workspace, is pseudonymised.
- Your sign-in identities and notifications are deleted.
- Answers you gave as a participant in other organisations' sessions stay with those sessions, unlinked from your account. To erase them, ask the organisation that ran the session.