Data Retention

How contextflow handles source data

Last updated August 24, 2026

Connected sources help teams turn selected activity into living project documents. This page explains what contextflow reads, stores, processes, and deletes when a workspace connects services such as Discord or GitLab.

What We Read

contextflow reads only the Discord channels a workspace owner or admin selects as project sources. The bot must be allowed to view the channel and read message history. We do not read every channel in a server just because the bot is installed.

Initial live sync currently fetches up to 500 recent settled messages per selected channel. After that, automatic sync checks for newer settled messages. Very recent messages are skipped until they are older than the settling window, currently 10 minutes.

For GitLab repository sources, contextflow reads commit metadata and commit messages from repositories selected by a workspace owner or admin. Initial GitLab ingestion currently fetches up to 500 recent commits and processes them in batches of 50. Later syncs fetch only commits newer than the last commit SHA stored for that source.

What We Store

We store source configuration, selected channel or repository metadata, sync cursors, generated project documents, changelog entries, and source snapshots. Source snapshots can include raw Discord message text or GitLab commit-message transcripts so workspace admins can inspect the source material behind a project update.

Attachments are represented as links in the transcript. contextflow does not download or store attached files from Discord in the current product.

AI Processing

To generate or update project documents, contextflow may send project documents, source snapshots, prompts, and related context to an AI provider such as OpenAI. The AI provider processes that content on our behalf so contextflow can identify durable project facts, decisions, requirements, risks, status, and open questions.

Security

We use HTTPS, authenticated app sessions, workspace access checks, database access controls, database encryption at rest, and encryption for stored connector secrets. Raw Discord source snapshots and GitLab commit-message snapshots are protected by those database and application controls; they are not currently separately field-encrypted inside the database.

No internet service can guarantee perfect security. Our goal is to keep the data we need narrow, explain the tradeoffs plainly, and give workspace owners a clear deletion path.

Retention And Deletion

Source data is retained while the related source, project, workspace, or account is active, unless a shorter period is required by law or contract. Deleting a source stops future sync for that source and removes the source record and its stored source snapshots from contextflow. Deleting a project or account removes project documents, source records, source snapshots, changelog entries, people/subscriber records, notifications, and related project data.

Some information may remain temporarily in encrypted backups, logs, or records we are required to keep for security, legal, billing, or abuse-prevention reasons. For deletion requests, email support@getcontextflow.com.

Connected Services

Removing contextflow or deleting contextflow data does not delete messages, channels, files, commits, repositories, or users from connected services. Server owners can remove the contextflow bot from their Discord server at any time. GitLab users can revoke the contextflow OAuth application from GitLab account settings.

Related Policies

This page supplements our Privacy Policy and Data Deletion page. For questions, email support@getcontextflow.com.