Data retention and deletion
What Laya keeps, for how long, what deletion actually removes, and how to export your data before you go.
Last updated
Laya’s retention model is deliberately simple, and deliberately conservative in your favour: we keep your work for as long as your account exists, and we do not delete it on a schedule. Nothing is silently aged out from under you. Deletion happens because you asked for it.
What is kept, and for how long
| Data | Retention |
|---|---|
| Customer content: boards, work items, docs, comments, attachments | For as long as the workspace exists. Not auto-purged. |
| Mirrors of connected boards | Until you remove the board or disconnect the tool. A disconnected Jira connection keeps its boards, paused, until you remove them. |
| Guest links shared from Laya Board for Jira with no linked workspace | A copy of the board’s issues, deleted when a Jira admin uninstalls the current version of the app; otherwise kept until you ask us to delete it. |
| Ready or Not results for a Jira project | Kept by our own servers that grade them (Amazon Web Services in Stockholm, Sweden, with their database in London, UK): each scanned work item’s latest result (its key, summary and type, and the AI’s assessment and suggestions), each scan’s list of work item keys, and the Atlassian account id of the person who ran it. No set expiry, and deleting a workspace does not remove them: ask us at privacy@laya.net. |
| Account data: profile, security settings | For as long as the account exists. |
| Connection credentials | Encrypted, held while the connection exists, destroyed when you disconnect. |
| Sessions | Until signed out, revoked from the Active sessions list, or expired. |
| Request logs | Kept for 30 days, then deleted automatically. |
| Error diagnostics | Kept with no set expiry, like the rest of the service’s records (see Data retention in our Privacy Policy). |
| Email delivery records | Kept so we can prove what was sent and honour unsubscribes and complaints. |
| Backups | Rolling. Deleted content ages out as the backup cycle turns over. |
What deletion removes
- Disconnect a tool: Laya destroys the stored credential and stops syncing. For Azure DevOps, monday.com, GitHub and GitLab it also deletes its mirror of that tool’s boards; a Jira connection keeps its boards, paused, so reconnecting resumes them. Nothing in your source tool is touched.
- Remove a connected board: Laya deletes its synced copy of that board’s items.
- Uninstall Laya Board for Jira (its current version, no linked workspace): Laya deletes the copy behind its guest links.
- Archive a board: hidden from the workspace (an admin can restore it).
- Archive an item: hidden from its board, and kept so it can be restored. Where an item is linked to a connected tool, deleting in Laya does not delete in the source tool unless you explicitly ask for that behaviour.
- Delete a workspace: its customer content is removed.
- Delete your account: your account data is removed. Content you created inside a workspace belongs to that workspace, and its administrator decides its fate; that is why the workspace, not Laya, is the controller for it.
- Backups: deleted data ages out with the rolling backup cycle rather than being surgically extracted from historical backups, which is standard practice and is disclosed here rather than glossed over.
Export before you go
You can export your work at any time from the product. If you are leaving, export first: deletion is intended to be final. If you need an export format we do not offer, ask at support@laya.net before deleting anything.
Was this page helpful?
Still stuck?
Contact supportEmail support@laya.net and include what you expected, what happened, and a link to the affected board or item so we can help quickly.