What a report carries
TeamFlow draws a map of your delivery from reports about the work, not from the work itself. This page is the whole of what that means, and the rule is enforced by the service rather than promised here.
What a report carries
Derived state, and nothing else:
- the issue key, its link, and its short title and status;
- parent and related issue keys;
- who did the work, the repository and the branch;
- the stage and the status, plus the gate a rework came back from;
- a derived summary of the state, capped at 180 characters;
- where the branch stands, as counts and flags: commits since main, ahead, behind, pushed, dirty, and the head commit's subject line;
- what the forge already publishes about a pull request: its number, its state, and how many checks are passing, failing and pending;
- compact evidence references, execution identifiers and timestamps;
- which tool reported, and the plugin's version.
A count of commits is not the commits. A tally of checks is not the logs.
What never leaves the machine
A report is never allowed to persist:
- prompts, transcripts or model output;
- source contents or diffs;
- shell commands or tool output;
- secrets;
- issue descriptions, comments or attachments;
- raw CI or test logs.
Why that holds even if a reporter misbehaves
The contract is an allowlist, and it is enforced where the report arrives rather than where it is sent.
- Unknown fields are dropped, not rejected. The service accepts the report and answers with a list of what it dropped. A reporter that grows a field — or is talked into attaching a prompt or a diff under a name nobody has heard of — still cannot make that content reach the store.
- The tenant comes from the credential. An organisation named in a request body is ignored, so a report cannot be addressed to somebody else's board.
- The same rule applies to trackers. Issue bodies, comments, attachments and custom fields are dropped at the webhook boundary, and an import does not ask for them in the first place.
You can read the live allowlist yourself at the capabilities route, which is the authority whenever anything else disagrees with it.
What TeamFlow writes back to your tracker
Nothing, until an owner turns it on per connection. When it is on, there are two switches:
- Comment on the issue when a ticket reaches verified or prod review. One fixed sentence carrying a stage, a clock and the report's own summary. Once per ticket per stage.
- Move the issue to a status you choose, from those two stages only.
It never reopens an issue and never closes one, and nothing goes out for a rework, a failure or any earlier stage. If somebody closes, cancels or deletes an issue, TeamFlow stops writing to it.
Where it is stored
On Amazon Web Services in eu-west-1, Ireland. The privacy policy has the full account: who processes what, how long it is kept, and your rights over it.
There are no analytics, no advertising, no tracking pixels and no third-party scripts on this website, and no cookies.