Last updated: September 2026 • Effective for all Teamsterx users
Summary: Teamsterx is an internal team collaboration tool. We collect only what's needed to provide the service, we don't sell your data, and your team's data stays yours.
Teamsterx ("we", "our", or "us") is an internal business collaboration platform. This Privacy Policy explains how we collect, use, and protect information when you use Teamsterx.
We collect information you provide directly and information generated through your use of the service:
Your data is stored using the following third-party infrastructure providers:
Data is stored in secure cloud environments with access restricted to authenticated team members through enforced security rules.
These are off by default. Nothing is sent to Slack or Google unless you or your team owner/admin chooses to connect them, and disconnecting stops future data flow.
We use the information we collect to:
We do not sell, rent, or share your personal information with third parties for advertising or marketing purposes.
We may share data only in the following limited circumstances:
Documents, sheets, and tasks marked as Private are only accessible to their creator. Other team members, including Admins and Owners, cannot view private content through the application interface.
Your data is retained for as long as your account exists and your team remains active. If you leave a team, your personal profile data is retained but your team-specific content remains with the team. If a team is deleted, all associated data is permanently removed from our systems.
Exceptions, deleted sooner than the rest. Voice recordings and their transcripts are deleted automatically 30 days after they are made, whether or not your account is still active (see Sections 15 and 16). Older Operator conversations are deleted as newer ones are started (Section 15).
You may request deletion of your account and associated data by contacting us (see Section 13).
Teamsterx uses browser localStorage and sessionStorage to store application preferences (such as your theme setting, sidebar state, and session tokens). We do not use third-party advertising cookies.
We take reasonable technical and organizational measures to protect your data, including:
No system is completely secure. We encourage you to use a strong, unique password for your account.
Teamsterx is designed for business and professional use. We do not knowingly collect personal information from anyone under the age of 16. If you believe a minor has provided us with personal information, please contact us and we will promptly delete it.
Depending on your location, you may have the right to:
To exercise any of these rights, please contact us using the information in Section 13.
If you have any questions about this Privacy Policy, or want to exercise any of the rights described in Section 12, please contact the team owner or administrator of your Teamsterx workspace.
We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page. Continued use of Teamsterx after changes are posted constitutes your acceptance of the updated policy.
Teams that have it enabled get access to an AI assistant built into Teamsterx, called Operator. This section explains what happens to your data when you use it, in addition to everything above.
What it reads. To answer you, Operator looks up workspace data on your behalf — tasks, documents, calendar events, and similar content. It only ever sees what you are already permitted to see: the same per-item permission checks that govern the rest of the app apply to it too, so it cannot show you, or act on, another member's private content.
We do not collect your conversations with it as a separate dataset. What you say to Operator, and what it says back, is used only to carry out your request and to maintain the conversation and memory described below. We do not analyze assistant conversations for marketing, and we do not use them — or the workspace data Operator reads while answering you — to train any AI model.
Voice recordings. If you talk to Operator instead of typing, the recording is stored in a private bucket, transcribed, and then automatically deleted after 30 days. The transcript becomes part of the conversation like anything you typed.
Conversation history. Your conversations with Operator are saved so you can pick one back up, in a history list scoped to you — other team members, including Admins and Owners, cannot see your conversations with Operator, the same as Private content described in Section 7. Only your most recent conversations are kept; older ones are deleted automatically as new ones are started.
Memory. Operator may retain a personal memory (things relevant to you specifically) and a team memory (things relevant to your whole team), so it does not need to be told the same context again in a later conversation. This memory is stored in our database. It is not something we review as part of normal operations, product analytics, or model training — it is handled with the same access restrictions as other private team content, and accessed only when legally required or necessary to investigate abuse or a security incident, consistent with Section 10's security measures.
Actions it takes. Some things Operator can do — like messaging other people or deleting several items at once — are queued for your one-tap approval rather than done automatically. Nothing it does bypasses the permission and security-rule enforcement described elsewhere in this policy.
Operator is optional: a team can leave it disabled, and it is only ever available to teams that have turned it on.
Teams that have it enabled can record a voice note for Operator to act on afterwards, rather than waiting for an answer. This section describes what happens to that recording, in addition to Sections 8 and 15.
What we keep, and for how long. Two things are stored: the recording itself, and the transcript — the text of what you said. Both are deleted 30 days after you record them, by an automated job; they are not kept for the life of your account, and the transcript does not outlive the recording it came from.
What is kept longer. Anything the assistant actually created or changed in your workspace — a task, a document, an edit — stays, along with a short record of which actions ran, exactly as it would if you had made those changes yourself. After 30 days that record no longer contains the words you spoke.
Why the transcript is kept at all. It is what lets you check what the assistant heard when it does the wrong thing, and it is how we investigate a report that it did. It is treated as private to you on the same basis as your Operator conversations (Section 15): other team members, including Admins and Owners, cannot read your voice notes or their transcripts.
Before it is sent. A note you record without a connection is held in your own browser's storage on that device, and nowhere else, until it can be uploaded. Until then it is not on our servers at all, and clearing your browser data will delete it.
Recording other people. A voice note captures whatever your microphone picks up. Please do not record other people without their knowledge — depending on where you are, doing so may be unlawful, and you are responsible for the content of what you record.
Voice notes are optional and off by default: they are only available on teams that have turned the feature on, and you can use Teamsterx entirely without them.