Why Leaving a Workspace Doesn't Delete the Boards You Built
Erasing your own account data in Tasks removes your personal data, not the boards you built — boards are workspace property and survive a member's departure.
If you're handling an employee's offboarding, or a team member's own data-erasure request, here's a policy worth knowing ahead of time: it doesn't take the boards they built with them.
What erasure actually removes
Tasks supports a self-erasure request consistent with GDPR's right to erasure. When a user erases their own data, the platform removes the personal data rows tied to that specific user — but it doesn't touch the boards, columns, or tasks themselves.
Why boards stay put
Boards are workspace property, not personal property. A board someone built belongs to the workspace it lives in, and the work on it — the tasks, the structure, the history — isn't erased along with one member's personal data when that member leaves or requests erasure. Only the data specifically tied to that individual is removed; the shared work product stays intact for the rest of the team.
Why we're stating this directly
This is the kind of detail that matters during offboarding planning: if you're counting on an employee's departure to also clear out their boards, that's not what happens, and it's worth knowing before you build an offboarding process around the wrong assumption. Conversely, if you were worried that an employee's own erasure request could take shared team boards down with it, it can't — the erasure is scoped to their personal data specifically, not to anything they built that the team still relies on.