Privacy
What Deskly records, why it records it, and what you can ask us to do with it.
Last updated 2026-09-23
A working draft. It describes what Deskly actually does today, but it has not been through a lawyer yet - treat it as our intent, not as cleared legal wording.
What we hold
Deskly is a virtual office, so most of what it stores is about where people were and what they were working on. Specifically:
- Account details: name, email address, a hashed password, and an avatar colour.
- Presence: which room you were in, your status, which device, and when - written by the server as a ledger.
- Content you create: whiteboard notes, chat messages and their attachments, and uploaded files.
- Recordings of meetings, where a workspace has recording enabled.
- Work attribution: which task you said you were on, and the hours derived from it.
- Mirrored issues from a connected tracker, and the mapping between a person and their tracker account.
- Site visits: the page, the site you came from, your country, and your kind of device, browser and system. These are not linked to your account, we do not store your IP address, and no cookie is used. They are kept for about 13 months, and browsers set to ask not to be tracked are not counted.
We do not sell any of this, and we do not use it to train models.
Why we hold it
Presence and attribution exist so a workspace can answer where the day went. Content exists because you wrote it. Account details exist so you can sign in. We hold nothing because it might be useful later.
Credentials for third-party services - a Jira or Azure DevOps token, calendar access - are encrypted before they are stored and are never shown back to a browser, not even to the admin who entered them.
Who can see it
Inside a workspace, visibility follows the same rule everywhere: you see yourself, a team lead sees the floor they lead, and a workspace admin sees the workspace. Task time is treated as more personal than presence time, not less.
Nothing crosses between workspaces. A guest pass is scoped to one room and enforced by the server rather than by the interface.
Where it lives
For the hosted product, data is held on our infrastructure in a single PostgreSQL database, with recordings and uploads on attached storage. If you self-host, none of it reaches us at all - the software runs on your hardware and we see nothing.
How long we keep it
Presence history is kept for the window your plan includes - seven days on Free, up to ten years on Enterprise. Notes, messages and files are kept until you delete them or close the workspace.
Meeting recordings are deleted automatically. On the hosted product a recording - the audio and video file, its transcript and its AI summary - is kept for 30 days from when it was made, then permanently deleted. On Enterprise it is kept for one year.
If you need recordings for longer, a workspace can buy Extended storage, a monthly add-on that keeps them for one year from when they were made. If it ends, there are 7 days of grace; after that the 30-day rule applies again and recordings older than 30 days are deleted.
Every recording shows the date it will be deleted, in the meeting library and on the recording itself, so you can download what you need first. Recordings made before this rule was introduced were given a full 30 days from the day it came in.
On the date shown a recording is removed from Deskly within about an hour: nobody can play, download or read it any more. Every copy - the file, its transcript and its summary - is then erased from our storage within 7 days. We keep those days only so that a mistake on our side can be undone; if your workspace renews Extended storage within them, recordings its lapse removed come back. After that, a deleted recording cannot be recovered.
Closing a workspace deletes its data. Ask us and we will confirm when it is done.
Self-hosted workspaces are not covered by this: recordings stay on your own storage, under your own rules.
Your rights
You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Write to us and we will act within thirty days.
Self-serve export and account deletion are not built yet. Until they are, these requests are handled by a person - which means they work, but they are not instant.