Last updated: March 30, 2026
Account information. When you sign in to Jam, we collect your email address for authentication and to associate your sessions with your account.
API keys. Jam uses a bring-your-own-key (BYOK) model. Your Anthropic API key is sent directly to Anthropic’s servers from your session sandbox. We do not store, log, or have access to your API keys on our servers.
Session data. When you use Jam, your terminal input, output, code, and files exist within an isolated cloud sandbox (powered by E2B). Session content is used solely to provide the collaborative experience.
Usage data. We collect basic analytics such as page views, session duration, and feature usage to improve the service. We do not use third-party advertising trackers.
Jam is a collaborative tool. When you invite others to a session, all participants can see the shared terminal and its output in real time.
When you use the Share feature, a public project page and preview URL may be created. Shared content is publicly accessible by anyone with the link. You control when and what you share.
Jam integrates with the following services:
Session sandboxes are ephemeral and are destroyed after inactivity. Project pages and preview URLs you create persist until you delete them. Account information is retained as long as your account is active.
We use industry-standard security measures including encrypted connections (TLS), isolated sandbox environments, and signed tokens for preview access. However, no system is 100% secure, and we cannot guarantee absolute security.
You may request access to, correction of, or deletion of your personal data at any time by contacting us. You can delete your shared projects and leave sessions at any time.
We may update this policy from time to time. We will notify you of material changes by posting the updated policy on this page with a new “Last updated” date.
If you have questions about this privacy policy, please reach out to us at privacy@letsjam.now.