Coming soon. The Wiki is in active development, so features and these docs may still change. Early adopters: contact us for access.

Personal data (GDPR)

Download everything the Wiki stores about a person, or anonymize them for good: what each covers in pages, Q&A, the calendar and analytics

1. Overview

The Wiki answers the two most common data-protection requests from a user's page: Download personal data (access) and Anonymize… (erasure). Both are on the user's Privacy tab under Settings → Users, and need permissions super admins hold: users:export and users:anonymize. Available on every license tier.

2. Access: download a person's data

Download personal data saves a JSON file with everything the Wiki stores about the person: their profile and directory, role, groups, preferences, avatar choice, sessions, sign-in history, API tokens (never the secrets), alert preferences and the actions they performed (latest 5,000 audit entries), plus what the Wiki's own parts keep:

PartIn the download
PagesThe publishes they scheduled and the review-by dates they set
Q&AThe questions, answers and comments they wrote, their votes and what they follow
CalendarThe events they wrote, edited or are on leave in, and whether they have a calendar feed address (never the address itself)
AnalyticsThe pages they read, by day, as far back as reading history is kept (about 25 months)

People can download their own data under Profile → Security → Download my data. Every download is recorded in the audit log.

Page comments and review requests aren't in the download yet.

3. Erasure: anonymize a person

  1. Disable the user — Only disabled users can be anonymized, so nobody is erased by accident while still working. For a user from LDAP or Active Directory, disable them in the Wiki (they may still be in the directory).
  2. Download their data if you need it — Anonymizing can't be undone.
  3. Open the user's page — On the Privacy tab, select Anonymize….
  4. Confirm — Type the person's email address and your own password, then select Anonymize permanently.

What is removed from the account: name, email, username, directory ID, password, avatar image, theme and language, sign-in and failed-attempt details, sessions (they're signed out everywhere), sign-in history, API tokens and keys, group memberships, roles and alert preferences. In the audit log and in stored events, their email address, network addresses and browser are removed.

What the Wiki's own parts do:

PartRemovedKept
PagesThe publishes they scheduled (nobody would publish them), review requests they were asked to answer, their name on the review-by dates they set and on the review requests they madePages, versions, comments and the dates and requests themselves, which belong to the page; their comments show without their name
Q&ATheir votes (scores drop with them), follows, reputation and drafts; their name on their questions, answers, comments and earlier versions; mentions of them in every post; images they uploaded that no post showsThe posts themselves, since other people's answers and votes hang on them; a moderator removes a post whose text names the person
CalendarTheir leave and their feed address; their name on the events they wrote or editedThe events, which belong to the space (its editors change a title that names the person)
AnalyticsWho read what, by dayTheir views, as anonymous ones, so page and space numbers don't change

What stays: the account itself, renamed Deleted user with an unusable address, so the audit log and what they wrote still make sense. It can never sign in or be enabled again, and it doesn't use a license seat.

Directories: if the person still exists in an LDAP or Active Directory directory, sync doesn't bring them back; the run lists them as skipped (*anonymized*). The Wiki keeps only a keyed hash of their directory ID for that, not the ID itself.

Anonymizing erases the data inside the Wiki. Page text that names the person, database backups, exported files and logs you keep elsewhere still contain it: include them in your erasure process.

4. Events

Anonymizing raises user.anonymize. Plugins and automation can react to it to erase what they hold about the user ID, and policies can restrict who anonymizes whom. See Events.

5. Permissions

PermissionWhoAllows
users:exportSuper adminsDownloading another person's data
users:anonymizeSuper adminsAnonymizing a disabled person