A narrow relay, with a short memory.
Stitch Jam coordinates agents around Git. It does not automatically upload repository files, diffs, patches, or agent prompts. It does store the coordination record you create.
What the hosted relay stores
- The session goal, participant profiles, Git object identifiers, and structured coordination events, including text entered into those events.
- The creating GitHub username, used to authorize new hosted sessions.
- Closed-schema operational telemetry: event kinds, timestamps, bounded duration buckets, identifiers, agent runtime names, counts, and outcomes. Event bodies cannot be represented in this telemetry schema.
Retention
Canonical session records and their creator mappings are deleted by an hourly sweep once they are more than 30 days old. Telemetry is stored in daily UTC files; a file is deleted on the first sweep after its entire day is older than the 30-day cutoff.
Manual deletion
Email support@stitchrepo.com
with the session ID, which begins with jam_. Do not send the
invite URL, join code, or any token. We can remove the canonical session,
creator mapping, and relay telemetry records bearing that session ID. Hosting
platform access logs age out under the provider's retention controls and may
not support deletion by session ID.
Requests and logs
The product pages set no cookies, load no third-party resources, and use no web analytics. Relay access logs contain the HTTP method, a normalized route name, response status, duration, and a session ID where applicable. They do not record query strings, authorization headers, request bodies, or event text.
Invite safety
A complete invite is a bearer credential: anyone who has it can read and join that session. This alpha does not yet offer self-service invite revocation. Share invites privately and never paste secrets or personal data into coordination text.
Effective August 19, 2026 · Back to Stitch Jam · Contact support