Privacy Policy

Last updated October 3, 2026

m4x, LLC runs teem at teem.so. This page lists what teem collects, why it keeps it, and which outside services see it. Send questions to [email protected].

Teams and their visitors

teem serves two groups. Teams sign up, run an organization and work in the dashboard; for their accounts, m4x decides how teem handles the data. Visitors use the teem widget or a public board on a team's site. The team that installed teem decides what to collect about its visitors, and teem stores and processes that data for the team.

What teem collects

From team members

• Your email address, your name and a profile photo if you upload one.
• Sign-in sessions, with the IP address and browser user agent that started each one.
• What you write in teem: replies, feedback posts, changelog entries and help articles.
• Billing details through Stripe. teem stores your Stripe customer and subscription IDs and never sees your card number.

From visitors, through the widget and public boards

• Messages, feedback requests and votes.
• The name and email a visitor types, or that the team's site passes to teem when it identifies a signed-in user.
• The page path where a conversation started, the browser user agent, screen size, time zone, and the country Cloudflare derives from the IP address.
• A session token the widget keeps in the browser's local storage, so a visitor can come back to the same conversation.

teem sets no advertising cookies, and a team's widget and public pages load no analytics.

From Slack, if a team connects it

teem stores the workspace name and ID, the bot token (encrypted), the channel the team picks, the messages posted in teem's threads, and the email address of each Slack user who replies, so teem can match the reply to a team member.

From AI apps, if a team member connects one

When a team member connects ChatGPT, Claude or another AI app to teem, teem stores the app's name and the address it signs in from, which organization and access level they approved, and when the connection was last used. Access tokens are stored as one-way digests. teem sends the app only what that team member asks it to read, such as conversations, feedback posts, changelog entries and help articles, and the app handles it under its own privacy policy. Disconnect any app in Settings, under API & MCP.

On teem.so

teem's own home page and dashboard use a sign-in cookie and Umami, a cookieless analytics tool that m4x hosts.

teem's home page, its privacy, terms and support pages, and teem's own help site at help.teem.so run Google Analytics. It records the pages you view, the site that sent you, your device and browser, and your approximate location, and it sets cookies so it can tell a return visit from a first one. If you're in the EU, the EEA, the UK or Switzerland, it sets no cookies and counts your visit without them. teem turns off its advertising features and Google signals. The dashboard, sign-in pages, other teams' public pages and the widget never load it.

How teem uses it

teem uses this data to run the service: delivering messages, emailing sign-in links and replies, telling voters when a request ships, billing, and finding and fixing bugs. teem doesn't sell it, show ads with it, or train AI models on it.

Outside services

• Cloudflare carries all traffic to teem.so and reports each visitor's country.
• Resend sends teem's email and receives email replies.
• Stripe handles subscriptions and payments.
• Slack receives conversations for teams that connect it.
• Google Fonts serves the typefaces on teem.so pages. The widget serves its own fonts.
• Google Analytics counts visits to teem's home page, its privacy, terms and support pages, and help.teem.so.

The application, its database and its error reports run on servers m4x operates.

How long teem keeps it

teem keeps an organization's data until the team deletes the organization. Deleting it in Settings removes its conversations, visitors, feedback, changelog and help center. teem also clears these on its own:

• Expired sign-in links, after 90 days.
• Anonymous widget sessions that never started a conversation, after 90 days.
• The stored body of each delivered email, 90 days after delivery.

Backup copies expire as the backups rotate.

Your choices

Team members can edit their profile in Settings, delete an organization from Settings, or email [email protected] to get a copy of their data or have it deleted. Visitors should contact the company whose site they used, since that company controls their data. If you can't reach them, email us and we'll forward your request.

Security

teem serves every page over HTTPS, stores API tokens only as digests, and encrypts Slack tokens in the database.

Changes

When this policy changes, the date at the top changes too. For a change that affects how teem uses your data, m4x will email each organization's owners first.