How Listspace keeps your boards safe: where your data is stored, who can reach it, what agents may do with it, and how to report a security problem. For what we collect and why, see the Privacy Policy.
Where your data lives
Your account, boards, lists and items are stored in a database on our server in the EU, rented from Netcup. Sign-in and the website run on the same server, and so does our own mail server that receives email sent to a board's address. Files you upload are stored in Cloudflare R2 in the European Union. A locked, encrypted copy of the database is also stored with Backblaze in the European Union. Backblaze, Inc. is a US company, so standard contractual clauses apply. Emails from Listspace are sent through Lettermint, in the European Union.
Every provider that processes your data for us is listed on the sub-processors page. Services you connect yourself, such as Slack, GitHub, Telegram or your browser's push service, work under their own terms.
Encryption
Every connection to Listspace uses HTTPS. A plain HTTP request is redirected to HTTPS, and the site sends a Strict-Transport-Security header for one year, including subdomains, so browsers refuse an unencrypted connection.
Files you upload are stored in Cloudflare R2, which encrypts every object at rest with AES-256 (Cloudflare R2: data security).
The nightly off-site backups of the database and of uploaded files are encrypted with restic, which uses AES-256, before they are sent to Cloudflare R2 in the EU (restic: design). A further copy of the database is encrypted with age on our server before it goes to Backblaze in the EU. Backblaze cannot read it, because it never holds the key.
Notifications to your devices are encrypted on our server (RFC 8291) before they go to the push service of your browser's maker, which delivers them without being able to read them.
The disk of the database server itself is not encrypted at rest.
Passwords, sessions and tokens
- Passwords are stored as bcrypt hashes by the sign-in service. We cannot read them. Passwords on shared board links are stored as bcrypt hashes too.
- Sign-up, sign-in and password reset are protected by Cloudflare Turnstile and rate limits, which stop bots and password guessing.
- After 3 wrong passwords in a row, password sign-in for that account waits 10 minutes, counted per account and per network (one IP address, or the /64 block of an IPv6 address), so a stranger who knows your email address cannot lock you out with 3 guesses from another network. After 20 wrong passwords in an hour from all networks together, it waits 10 minutes from everywhere, and the next wrong password after each wait starts the next wait; we email you, at most once a day. Tries made at the same moment count too, so many networks together cannot get past the 20. A network that signed in to your account in the last 30 days is not held by the wait from all networks (its own 3 wrong passwords still start its own wait), so a stranger cannot keep you out from your usual places; changing or resetting your password ends that for every network. A new device on a new network can still be held for 10 minutes. People behind one shared network, such as a carrier or an office, count as one network. During a wait, even the right password is refused, and resetting your password or signing in with a code sent to your email still work. We keep only hashes for this, never a readable email address or IP address, and delete the counts about an hour after the first wrong password of the hour, and the record of a network that signed in 30 days after its last right password.
- A sign-in session token is valid for one hour and is then renewed with a refresh token, which is replaced each time it is used.
- Changing your password signs you out on your other devices at once. Resetting it with a link from your email also disconnects every AI app and API token connected to your account, turns off your Telegram link, Slack link, GitHub connection and calendar links, and pauses your webhooks.
- Two-step sign-in is optional: turn it on in Settings with an authenticator app (TOTP). For an account that has it on, the database itself refuses a session that has not passed the second step.
- You get an email when an authenticator is added to or removed from your account.
- You can also sign in with a code sent to your email. Asking for a code never creates an account.
- Turning on two-step sign-in gives you 10 one-time recovery codes, shown once. We store only a salted SHA-256 hash of each, and tries are rate limited. Each code signs you in once and two-step sign-in stays on; we email you each time one is used, with how many are left. You can get new codes in Settings. There is no SMS option. Without a code or an authenticator, we restore access by hand after checking that the account is yours.
- Personal API tokens are stored only as a SHA-256 hash. A token can be read-only, and you can revoke it in Settings at any time.
- During the beta, only people with an invite can create an account.
Each account reaches only its own boards
Row-level security is switched on for every table in the Listspace database. The database itself checks each request against the signed-in account, so a request for someone else's board returns nothing, and a write into another account is refused.
The one exception is a guest on a board. The board owner invites a person by email to that one board, as View, Comment or Edit, optionally until a date. The database gives the guest exactly that role on that board and nothing else of the owner's: not the owner's other boards, sharing, agent settings or Inbox. When the end date passes or the owner removes the guest, access ends at once, including live updates and links to files.
When you work with others
You can share a board with guests, or keep it in a team space where the team's members work on it. What they can change depends on the role you give them, and some things only the board owner can do.
- Team members with Editor access add and change items, and archive items and lists. Guests with Edit add and change items and archive items, but never change a list or a list group. Archived items and lists come back from the board's menu.
- Only the board owner, and on a team board the team's owner and admins, delete items and lists for good.
- Team members and guests remove only the files they uploaded themselves. The board owner and the team's owners and admins can remove any file.
- A removed file goes to Removed files in the board's menu, with its older versions and the comments on it. It stays there for 30 days, then it is deleted for good. Until then the board owner or a team owner or admin can bring it back, or delete it for good sooner.
- While a file is removed, only the board owner can open it. A guest who kept its address gets no new link to it.
- Agents never remove files, and never delete items, lists or boards.
Private files
Attachments are stored in a private bucket. They can only be opened through a signed link that expires after at most 15 minutes, and a link is only issued for files under your own account, or on a board shared with you as a guest while you still have access.
Files are checked for viruses on our server before others can open them. Every file added to an item is scanned with ClamAV there, and is not sent to another company for it. Until the check is done, only the person who added the file can open it. If the scanner is down or a file cannot be checked (for example a zip locked with a password, or one that unpacks to more than the scanner checks), it stays that way: the person who added it can open it, everyone else sees "Not checked yet", and the check runs again once the scanner is back. A file with a virus is blocked for everyone, the person who added it is told, and it is deleted after 30 days. A file over 250 MB is too large for the scanner and is not checked. It is marked "Not scanned: too large" for everyone and for AI assistants, it never opens inside Listspace, and Listspace asks before each download whether you want it anyway.
Images you choose to make public, such as board backgrounds and images on a shared board, are stored separately. A shared board only shows images that passed the virus check. Cloudflare checks those public images against known child sexual abuse material; files on private boards are not checked against that list.
When a file opens in Listspace:
- Word and markdown previews are shown in a sealed frame that cannot read your session or the rest of the app. Images from other websites in them are never loaded.
- A link in a preview first shows where it leads, and opens only when you confirm.
- Before a Word file or spreadsheet is previewed, it is checked for zip bombs: a file that unpacks to over 100 MB or has over 10,000 parts is not previewed. A file added in the app can be up to 25 MB on Free, 2 GB on Pro and 5 GB on a team's boards. A file over 10 MB goes from your browser straight to our file storage, not through our app server, and gets the same checks; a large one is sent in parts, each part signed for its exact size.
- Spreadsheet formulas and macros never run. PDFs are drawn as pictures, so scripts and links inside them do nothing.
- When your AI reads a spreadsheet or CSV file on an item, it is read on our server with the same rules as opening it, the virus check included. A spreadsheet is prepared once in the background after it is added, by a separate program that has no access to anything else, a memory limit and a 10 second limit. A copy of its text is kept with the file, never shown in the app, and deleted with the file. Formulas and macros never run, and your AI gets at most the first 1,000 rows of each sheet of a file up to 10 MB. Pictures (PNG, JPEG, GIF and WebP up to 3 MB) are passed to your AI as the picture. Other kinds of files are not read on our server: your AI gets their link instead.
- Uploaded HTML, SVG and script files are stored as plain-text downloads, so they cannot run as a web page.
The app itself
- A Content-Security-Policy is enforced on the app's pages: the browser runs scripts only from Listspace, our analytics and Turnstile, and blocks everything else.
- Text in descriptions, documents and comments is cleaned when it is saved and again every time it is shown, so a script in it never runs.
- Other websites cannot show Listspace inside a frame, browsers do not guess the type of a file, and the app has no access to your location, microphone or camera.
- When Listspace fetches a web address you or an agent gave it, such as for a link preview or an import, it refuses addresses inside private networks.
Backups
The database is dumped every hour on the server, and the last 48 hours of dumps are kept. Every night a copy of the database and of all uploaded files is encrypted with restic (AES-256) and stored off the server, in Cloudflare R2 in the EU. We keep 7 daily, 4 weekly and 6 monthly copies, and a script that tests a restore from them. Every 20 minutes a further encrypted copy of the database goes to Backblaze in the EU, locked, so that no key on our server can remove it before the lock ends. We keep those copies for about 10 days, and one a day for about 33 days. Our procedure is to back up the database before every change to its structure. When you delete your account, copies in backups are removed as those backups expire, within about 6 months.
Agents work within limits you set
AI agents reach your boards only after you connect them, by signing in or with a personal token. For each board you choose an agent access level, from 1 (Read only) to 5 (Full), or switch agents off for that board: an Off board does not exist for an agent, which cannot read or change anything on it. What is not an agent is not stopped: notifications sent to you, and a calendar feed or webhook you set up yourself, still carry the board's data, and a file download link an agent already holds works for up to 10 minutes. At the levels in between, changes that need your approval wait in the board's Inbox until you accept or reject them.
If your ChatGPT or Claude account belongs to your company, what your AI reads from a board ends up in its chat, which lives in your company's workspace under the AI provider's terms for that workspace. To keep a board out of it, set the board's agent access to Off. Some company workspaces need an admin to allow connected apps.
At any level, agents never:
- Delete your items, lists, boards, comments or files. Items, lists and boards are archived instead, and you can bring them back.
- Change agent access, or accept or reject suggestions in the Inbox.
- Make share links, board email addresses, API tokens or webhooks.
- Store text that looks like a password, key or token. The change is refused and nothing is stored.
A request your AI sends to another person on a board goes out in your name, so it waits in your Inbox until you accept it. On a board you own, you can change that in Board settings: "AI requests to people on this board" is Ask first until you switch it to Send directly. Only you can switch it, in the app, and never on a board someone shared with you. With Send directly, a request from an agent at level 4 (Act) or 5 (Full) goes out at once, only to people already on that board, and at most 20 a day for each agent connection on a board. The person who gets it, and the board's history, see which assistant sent it for you. Passing a request on still waits in your Inbox. Text on a board can steer an agent, so keep Ask first on boards where other people write.
Your AI can't confirm, replace or withdraw a decision, flag a conflict or add how one turned out on its own: these wait in your Inbox, whatever app your AI works in. Only a person can keep a decision as still true.
An agent can take a link off an item from level 3 (Capture), and remove a dependency between items from level 4 (Act). At level 5 (Full), it can also delete a label that no item uses, a custom field (undo brings it back with its values), and a checklist item it added itself.
Changes to items, lists and boards are recorded in the board's history with the name of the agent that made them, and you can undo them there for 30 days. Disconnecting an agent in Settings stops its access. The full rules are in What AI agents can do.
No AI models run by Listspace
Listspace runs no AI models itself, and we never use your data to train AI models. We never sell it or use it for advertising. The assistants you connect, such as Claude or ChatGPT, run with their own provider under that provider's terms. How we handle your data is described in the Privacy Policy.
Analytics and error reports
We count visits to the public pages with Umami, an open-source tool on our server. It sets no cookies and stores nothing that identifies you. The app itself, where your boards are, loads no analytics. There are no advertising or tracking cookies anywhere on Listspace.
Error reports go to Sentry in the European Union. Email addresses, tokens, the query strings of links and board content are left out, and the app adds no IP address. Sentry sees the address a report arrives from.
What you can do yourself
No one can guarantee complete security, and we cannot either. The sections above say what we do. Here is what you can do yourself:
- Turn on two-step sign-in in Settings.
- Give an agent that only needs to read a read-only token.
- Keep the agent access level low, such as 1 (Read only) or 2 (Suggest), on boards with sensitive content, or set the board to Off.
- Do not put passwords, API keys or other secrets in items, comments or files. Listspace refuses changes from AI agents and the API that look like a password, key or token, removes them from text that comes in by email, Slack or Telegram, and warns you before you save one in an item or a comment.
- Review the Inbox and the board's history now and then, and disconnect agents you no longer use.
Who you are dealing with

Listspace is made and run by Jordi Buskermolen. The company behind it is Sjenkie B.V., trading as Yellow House Digital, registered in the Netherlands (Chamber of Commerce: 60310030). Why he built it and where it runs: About Listspace.
Report a security problem
If you find a security problem in Listspace, email security@listspace.app with what you found and the steps to reproduce it. We confirm that we received your report, and we keep you informed while we work on it.
While you look, please:
- Use only your own accounts and boards. Do not open, change or keep other people's data, beyond the least you need to show the problem
- Do not run tests that slow the service down or interrupt it for others, and do not send spam
- Do not use social engineering, such as phishing us or our users, and do not try physical attacks
- Give us reasonable time to fix the problem before you publish it
If you report in good faith and follow these rules, we will not take legal action against you for your research. We do not run a paid bug bounty yet.
Our contact details for security reports are also in security.txt.
Contact points (Digital Services Act)
Listspace is run by Sjenkie B.V., a company registered in the Netherlands. Under the EU Digital Services Act we have a single point of contact for authorities and one for users. A person reads every message.
- For authorities (Article 11): authorities of EU member states, the European Commission and the European Board for Digital Services. Write to legal@listspace.app.
- For users (Article 12): everyone who uses Listspace. Write to hello@listspace.app. You do not have to go through a form or an automated tool.
Languages: you can write to us in English or Dutch.
To report illegal content on a shared board, use the "Report this board" button at the top of that board (notice and action, Article 16). Pick a reason and say which item it is and what is wrong with it. You can also email legal@listspace.app. What to include, and what happens next, is in Notices about unlawful content in the Terms of Service. For copyright complaints, see Copyright complaints.
Copyright agent (DMCA)
Our designated agent for copyright notices under the US Digital Millennium Copyright Act is registered with the US Copyright Office under number DMCA-1082111. Send notices and counter-notices to legal@listspace.app. What to include is in Copyright complaints in the Terms of Service.
What we are working on
Listspace has no security certification today, such as SOC 2 or ISO 27001. These are the next steps we have decided on:
- GDPR documentation: done. The sub-processor list and a Data Processing Agreement for business customers are published.
- SOC 2 Type II. This is a goal; there is no date yet.