Privacy Policy

Who is responsible

SessionRun is provided by en:tribe. Operator and contact details are available in the Impressum linked from this page.

Use the Impressum contact channel for privacy requests, access requests, deletion requests, or questions about how your data is handled.

Local-first session data

You can use SessionRun without an account. Your session titles, purpose, details, planned times, agenda block titles, descriptions, private notes, assignee names, durations, colors and order, folders, imports, exports, language choice, and local preferences are kept in your browser until you enable sync, publish a Live Timer, connect an AI app, or share an export.

The browser also keeps up to 50 local product event names with their timestamps for troubleshooting the first-use flow. These events are not sent to an analytics provider. Local data stays until you delete it, clear browser storage, or remove the browser profile; clearing browser data can remove your sessions.

Account and cloud sync

If you sign in, Supabase handles your email address, account identifier and authentication credentials. Optional Cloud Sync stores the selected sessions and their agenda blocks, including the content and timing fields listed above, plus record identifiers, ownership links, change timestamps and cloud-selection settings. These fields support authentication, access control, backup, sync and conflict handling.

Your profile can contain a display name, marketing email consent choice and time, consent version and upgrade email preference. You control these choices in the account settings. If a paid entitlement is configured, RevenueCat receives a stable app user identifier and processes entitlement or purchase status so SessionRun can check access to paid features.

Cloud session content and profile data remain while your account exists or until you remove the content. The in-app account deletion request removes the Supabase account and its linked cloud rows; local browser data must be removed separately. Purchase records may remain with the payment provider under its own retention rules.

Public Live Timer sharing

If you publish a Live Timer link, Supabase stores a random share identifier, your internal account and session identifiers, the public session title and purpose, planned and estimated times, timer status and remaining time, and the shared blocks' titles, descriptions, assignee names, durations, colors and order. Anyone with the link can view the shared snapshot; private block notes are not included.

A published snapshot is readable through the public link for 12 hours after its latest publication. Its database row can remain after the link expires until you delete the account or request removal; expiry alone hides the row from public access and does not delete it. You can stop sharing by no longer distributing the link and ask us to remove a stored snapshot.

AI assistants and MCP connections

An AI app you authorize through MCP can send a list limit or a session identifier to read your sessions. With write permission, it can send session titles, purpose, details, planned times and blocks with titles, descriptions, private notes, assignee names, durations, colors, order and existing block identifiers. SessionRun uses those inputs only to perform the requested account-scoped operation. This MCP version cannot delete sessions or blocks.

The list tool returns only session identifiers and titles. A session read or write returns the session identifier, title, purpose, details, planned times and ordered blocks with their identifiers, titles, descriptions, notes, assignee names, durations and colors. SessionRun does not send your account identifier, email, ownership links, database timestamps, deleted records or diagnostic payloads in MCP tool results. Session and block identifiers are returned so you can select and edit the right records in follow-up requests.

To authorize a connection, we process your Supabase account identifier and email, the connected client's name and approved read/write scopes, authorization state and security tokens. Temporary consent and callback state expires after 10 minutes; MCP access tokens last up to 50 minutes and refresh tokens up to 30 days. Connection records are kept while the authorization is active. Disconnect the app in the connected client to stop its requests, delete your SessionRun account to end account access, or contact us to revoke a connection. Your AI provider receives the tool inputs and results and handles them under its own privacy terms.

Analytics and diagnostics

SessionRun does not use advertising identifiers or send the locally stored product events to a third-party analytics service.

Cloudflare hosts the site and MCP Worker and processes request metadata such as IP address, browser or device information, request path, time and error details to deliver and protect the service. Worker diagnostic logs are enabled and can retain request and error data for up to 7 days under Cloudflare's Workers Logs limits. We do not intentionally put session content or MCP tool payloads in application logs.

Recipients

Cloudflare receives technical request data for hosting, OAuth state storage and diagnostics. Supabase receives account, authentication, profile, synced session and public Live Timer data. RevenueCat receives the app user identifier and purchase or entitlement data if paid features are used.

An AI app you choose, such as ChatGPT or Claude, receives the MCP tool inputs and results described above. People who receive your Live Timer link or an export can see the content you chose to share. We do not sell your session content.

Your controls and requests

You can use local features without signing in, choose which sessions sync, edit or remove local content, export session data, change profile and marketing choices, refuse an MCP connection and delete your cloud account in the app. Deleting the cloud account does not clear local browser data or copies already sent to an AI provider, exported to others or opened through a shared link.

Use the Impressum contact channel to request access, correction, deletion, a copy of your data or help revoking an AI connection. We will also help remove an expired public Live Timer row on request.