Privacy Policy
Last updated: November 17, 2026
The short version.
- We store what your team puts in its workspace so we can show it to your team.
- We don't sell your data, use it for advertising, or train AI models on it.
- Apps you connect to search from DumbSlab are only read, with your own access. Their tokens are encrypted, and only you can use your connections.
- From Google Drive, DumbSlab sees only the names and details of the files your search finds, never what's in them, and doesn't save them.
- Admins can export the whole workspace at any time. Email us to have it deleted.
Who we are
DumbSlab runs the hosted team knowledge base at dumbslab.com and its workspace addresses, such as acme.dumbslab.com. This policy covers that hosted service. "We" and "us" mean DumbSlab.
Each workspace belongs to its admins. They decide who joins, what the workspace keeps and when it is deleted. We store and handle the workspace's content on their behalf.
DumbSlab is also open-source software. If you use a copy that someone else runs on their own server, they are responsible for your data there, and this policy doesn't apply.
Questions or requests: simplycoo+dumbslab@mail.grokbot.com.
What we store
Each workspace has its own separate database. It holds:
- Workspace content. Posts and their earlier versions, comments, reactions, topics, uploaded files and images, and the search index built from them. Also who follows what, notifications, and which posts each person has viewed.
- Accounts. Each person's name, email address, handle, role, and optional bio and picture. Your password is stored only as an Argon2 hash; we never keep the password itself. If an admin turns on people sync, profiles also get job title, department, location, work phone, pronouns and manager from BambooHR.
- Single sign-on. If you sign in or sign up through Google, Microsoft, Slack, Okta or another identity provider, we keep the provider's ID for your account and the email address it gave. Signing up that way also takes your name from it.
- Sessions. Signing in sets one cookie,
dumbslab_session, holding a random token. We store only a SHA-256 hash of that token, with your browser's user-agent string and when the session ends. Sessions last up to 30 days. - API tokens. Personal access tokens, and the tokens AI tools get when you approve them, are stored only as SHA-256 hashes. A token is shown once, when it's made.
- Activity events. A feed of changes: who did what, to which post, topic or setting, and when. It doesn't copy comment text.
- Usage. The workspace's size and how many database rows it writes each hour, to apply plan limits.
- Sign-in protection. Counts of failed sign-ins, keyed by a hash of the email address and a hash of the network address, so we can slow down password guessing. They are cleared after a short window.
- Sign-up protection. To limit how many workspaces one visitor can create, the sign-up service keeps a keyed hash of the IP address that created each workspace, never the address itself.
- Billing. When a workspace subscribes to Pro, we keep its Stripe customer and subscription IDs and the subscription's status. Card details go to Stripe and never reach us.
Your browser also keeps a few things in local storage: your light or dark theme, whether you hid the editor preview, which topics you collapsed in the sidebar, and a recovery copy of a post you're editing until it's saved, so a crash or a closed tab doesn't lose your work. Signing out clears the recovery copies. The sign-up page remembers the setup link it just made, for that browser tab only. When session recording is on, the recorder keeps a random visitor ID there too. The session cookie is the only cookie we set, and none of this is used for advertising.
Connected apps and integrations
DumbSlab can work with other apps in a few ways. In each case, we never sell what we read, never use it for advertising, and never use it to train AI models.
Apps you connect yourself
Each person can connect their own account in another app to search it from DumbSlab or to preview its links. DumbSlab makes those requests with your access, so you see only what that app already lets you see. It only reads: it never creates, changes or deletes anything in these apps. Results are fetched when you ask and shown to you. They aren't saved in the workspace.
For each connection we keep your encrypted credential and a label, such as the email address of your Google account. For Jira, Confluence and Trello we keep only the site, not your name or email.
- Asana: tasks and projects in your workspaces.
- Box: files and folders you can open.
- ClickUp: tasks you link to.
- Confluence: pages and blog posts on one Atlassian site.
- Dropbox: file and folder names and details, including your team's space.
- Freshdesk: tickets you link to.
- GitHub: issues, pull requests and repositories you can see.
- GitLab: issues and merge requests you link to.
- Google Drive: the names and details of files you can open, including shared drives, but never what's in them. See Google user data.
- Guru: cards you can read.
- Jira: issues on one Atlassian site.
- Linear: issues you link to.
- monday.com: items you link to.
- Shortcut: stories you link to.
- Slack: messages you can see, through Slack's search.
- Todoist: tasks you link to.
- Trello: cards you link to.
- Wrike: tasks you link to.
- Zendesk: tickets and Help Center articles you can see.
Integrations admins set up for the workspace
- Docs sync from GitHub or GitLab. Reads the Markdown files and images in one repository folder and saves them as posts. Through DumbSlab's GitHub App it has read-only access to files, and each sync uses a one-hour token for one repository; we keep no GitHub token. GitLab offers only full API access for adding webhooks, so that's what you approve. DumbSlab uses it only to list your projects, read files, and add and remove its own push webhook on the project you pick.
- People sync from BambooHR. Reads job title, department, location, work phone, pronouns and manager for people already in the workspace, matched by work email. It never adds or removes anyone.
- Slack app. Lets people search DumbSlab and start drafts with
/dumbslab, and shows previews of DumbSlab links pasted in Slack. If admins choose channels, DumbSlab also posts there when posts are published or updated. This is the one integration that writes to another app. - Single sign-on. When you sign in through your identity provider, we receive your account ID, email address and name from it.
How credentials are protected
Every credential for these apps and integrations is encrypted with AES-256-GCM, using a key derived from a server secret (CONNECTOR_KEY). Each one is bound to the person and app it belongs to. No part of DumbSlab ever shows a stored credential again.
Your connections are yours alone. Nobody else in the workspace can use them, admins included: a token someone else makes for your account can't reach them, and if an admin or we set a new password for you, your connections are deleted.
Disconnecting an app deletes its stored credential right away. To also cancel DumbSlab's access on the app's side, revoke it in that app's settings. Removing DumbSlab's shared Slack app from Slack is done by a Slack admin in Slack.
Google user data
This section covers the data DumbSlab gets from Google APIs: from Google Drive, when you connect it, and from your Google account, when you sign in with Google.
Limited Use. DumbSlab's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
Data access: what DumbSlab gets from Google
Google Drive. When you connect Google Drive in Settings › Connected apps, DumbSlab asks Google for one permission: https://www.googleapis.com/auth/drive.metadata.readonly ("See information about your Google Drive files"). With it, DumbSlab gets:
- the email address of the Google account you connected;
- an access token and a refresh token, so it can search for you;
- each time you search, for the files Google's search finds (at most 20 per search): the file's name, its type (such as Google Doc or PDF), its link, when it last changed and its owner's display name.
Google runs the search, over your files' names and contents, and sends back only those details. That permission can't read or download what's in your files, and it can't create, change, share or delete anything in your Drive. DumbSlab never asks for anything else in your Google account, such as Gmail or Calendar.
Sign in with Google. When you sign in or sign up with Google, DumbSlab asks only for your basic profile (openid email profile). Google sends your Google account ID, name, email address and profile picture link. DumbSlab keeps your account ID and email address, takes your name when you sign up, and ignores the picture. This gives DumbSlab no access to your Drive or other Google data.
Aggregated and anonymized data. DumbSlab makes no aggregated or anonymized data from Google user data, and doesn't count, profile or analyze it.
Data use: what DumbSlab does with it
- Drive results are used only to show you the Drive files that match your search, in DumbSlab's search page and quick search, and to answer the same search when an app you connected to your own DumbSlab account asks for it (see Data transfer).
- Your Google account's email address labels the connection in Settings, so you know which account is connected.
- Tokens are used only to send Google the searches you ask for.
- Sign-in details are used only to sign you in, to match you to your account and, when you create a workspace with Google, to name your account.
We never use Google user data for advertising (including targeted, personalized or interest-based ads, or retargeting), never sell it, never use it to decide credit-worthiness or for lending, and never use it for anything other than the features above.
No AI or machine learning. DumbSlab doesn't use any AI or machine-learning model or service. We never use raw or derived Google user data, including Workspace data, to develop, improve or train AI or machine-learning models, and we never send it to an AI provider.
No person at DumbSlab reads Google user data unless you ask us to (for example, to help with a problem), it's needed for security, such as investigating abuse, or the law requires it.
Data transfer: who receives it
DumbSlab shares Google user data only in these cases:
- With you. Drive results go only to you, in your browser. Other people in your workspace, its admins included, can't see your results or use your connection.
- With apps you connect to your own DumbSlab account. If you connect an API client or an AI assistant (such as Claude, ChatGPT or Cursor) to your DumbSlab account, and it asks DumbSlab to search your connected apps for you, DumbSlab sends that client the same Drive results it would show you. This happens only for clients you approved yourself, only when they ask, and their own terms cover what they do with the results. DumbSlab doesn't send your Drive results to any of them on its own.
- With our hosting provider. Cloudflare runs DumbSlab's servers. Your encrypted token and email address are stored there, and requests to Google pass through it. Cloudflare handles them only to run DumbSlab for us.
- When required. To comply with the law, to protect DumbSlab and its users (security and abuse), or as part of a merger, acquisition or sale of assets, with your consent first.
We never transfer or sell Google user data to advertisers, data brokers or information resellers, or to anyone for any other purpose.
Data protection: how it's kept safe
- Encrypted in transit. Everything between your browser, DumbSlab and Google uses HTTPS (TLS).
- Encrypted at rest. Google tokens are encrypted with AES-256-GCM, using a key from a server secret, and bound to you and to Google Drive. No part of DumbSlab, its API included, ever shows a stored token again.
- Not stored. Drive results aren't saved anywhere on our side. They exist only while DumbSlab answers your search, and in your open browser tab.
- Only you. Each workspace has its own database, and only the person who connected Google Drive can use that connection. A token someone else makes for your account can't use it, and if an admin or we set a new password for you, your connections are deleted.
- Kept out of diagnostics. Results from your connected apps are recorded as empty boxes in our session recordings, and error reports carry no page content or error messages (see Companies that help us).
- Limited access. Only DumbSlab's operator can reach the servers, and only for the reasons above. Sign-ins with Google use PKCE and one-time state values, and requests are rate-limited.
Data retention and deletion
- Drive results: not kept. Our servers discard them as soon as they've answered your search, and your browser forgets them when you leave or reload the page.
- Your Google account's email address and encrypted tokens: kept only while Google Drive is connected. They're deleted right away when you disconnect Google Drive in Settings › Connected apps, when an admin deactivates your account, when someone else sets a new password for you, or when the workspace is deleted.
- Sign in with Google: your Google account ID and email address stay linked to your DumbSlab account until you unlink Google in Settings › Profile or the workspace is deleted. To have them removed sooner, ask your workspace's admins or email us.
- Backups: deleted tokens and email addresses can remain, encrypted, in our backups for up to 30 days, then they're gone for good (see Keeping and deleting data).
- At Google: you can also remove DumbSlab's access at myaccount.google.com/permissions. The stored token then stops working; disconnecting in DumbSlab deletes it.
- On request: email simplycoo+dumbslab@mail.grokbot.com to have your Google user data deleted. We'll do it within 30 days and confirm.
How we use data
- To run the service: show your workspace to the people in it, search it, and answer the AI tools and API clients you connect.
- To keep it safe: limit requests and sign-in attempts, and stop abuse.
- To find and fix problems, using the error reports and recordings described below.
- To bill for Pro, and to answer your requests.
- To comply with the law.
We look at a workspace's content only when you ask us to help, when it's needed to investigate abuse or a security problem, or when the law requires it.
When you connect an AI tool (such as Claude, ChatGPT or Cursor) to your workspace, it reads what you allow it to. That tool's own privacy policy covers what it does with that data.
Companies that help us
- Cloudflare hosts DumbSlab and stores all workspace data, uploads included. Its network carries every request and protects the service from attacks. It keeps short-lived request logs to run and protect the service. On the sign-up site and these policy pages only (not in workspaces), Cloudflare Web Analytics counts visits: the page, the site that linked to it, and how fast it loaded. It sets no cookies and doesn't build a profile of you.
- Stripe handles payments for Pro.
- Sentry receives error reports.
- From your browser, only on signed-in pages: the type of error, function names and line numbers, the page as a route template (like
/p/:id), your user ID and your workspace's address. Error messages are replaced with "[redacted]", and no IP address is sent. - From our servers: only a failure category, the app version and a random ID. No user details, addresses or content.
- From your browser, only on signed-in pages: the type of error, function names and line numbers, the page as a route template (like
- Quill is a session-recording server we run ourselves (it's compatible with PostHog). It records how the app is used after you sign in to a workspace, so we can see where it breaks or confuses people.
- All text and every input are masked. Post and comment bodies, the editor, search results and results from your connected apps are recorded as empty boxes.
- Page addresses are cut down to route templates, like
/p/:id, so titles, IDs and search words aren't recorded. - No canvas, console logs or network requests are recorded.
- Nothing is recorded on the sign-up site, these policy pages, or the setup and sign-in pages.
- Quill doesn't store IP addresses.
- Each recording is linked to your user ID, name, email address and workspace address, so we can follow up on a problem. Signing out stops recording.
- The apps you connect receive the requests DumbSlab makes with your access. Their own privacy policies apply there.
Cloudflare runs in many countries, and our other providers are in the United States. Your data may be stored and handled outside your country, including in the United States.
Keeping and deleting data
- Workspace content stays until someone deletes it or the workspace is deleted.
- Export. Admins can download the whole workspace as JSON at any time, from Settings or with
GET /api/v1/export. - Deleting a workspace. An admin can email us to delete their workspace. We erase its database, uploads included, and free its addresses. A workspace with an active Pro subscription is cancelled first.
- Disconnecting an app deletes its stored credential right away.
- Connected apps' credentials are also deleted when an admin deactivates you, or when an admin or we set a new password for you.
- Sessions end after 30 days, or when you sign out.
- Accounts. Admins can deactivate people. To have your personal data removed from a workspace, ask its admins, or email us.
- Backups. Cloudflare can restore a workspace's storage to any point in the last 30 days. We also keep an encrypted copy of every workspace each night, for 14 days, on computers we control. So deleted data can remain in backups for up to 30 days before it's gone for good.
- Error reports and recordings are used only to find and fix problems.
Your choices and rights
Depending on where you live, laws such as the GDPR, the UK GDPR and California's CCPA give you rights over your personal data. You can ask to see it, correct it, get a copy, have it deleted, or object to or limit how we use it.
Email simplycoo+dumbslab@mail.grokbot.com with your request. We may need to confirm it's you. For data inside a workspace, we may work with that workspace's admins, since they control it. We won't treat you differently for using these rights.
We don't sell personal data, and we don't share it for cross-context behavioral advertising.
You can also complain to your local data protection authority.
Security
- Every connection uses HTTPS, and browsers are told to always use it.
- Passwords are hashed with Argon2. Sessions and API tokens are stored only as hashes.
- Credentials for other apps are encrypted with AES-256-GCM.
- Each workspace has its own database, and roles and private topics limit who sees what.
- Requests and sign-in attempts are rate-limited.
No system is perfectly secure. If a breach affects your personal data, we'll tell you as the law requires. To report a security problem, see SECURITY.md or email us.
Children
DumbSlab is made for teams at work. It isn't meant for anyone under 16, and we don't knowingly collect children's data. If you think a child has given us personal data, email us and we'll delete it.
Changes to this policy
When we change this policy, we'll update the date at the top. For changes that matter, we'll also post a notice on dumbslab.com before they take effect.
Contact
DumbSlab: simplycoo+dumbslab@mail.grokbot.com.