Disclaimer
Last updated: 2026-08-19
Some of what flanner reports is a judgement, not a fact. This page says which parts, so nobody mistakes a signal for a guarantee.
1. Freshness is a signal, not a verdict
Flanner scores how likely a plan is to have drifted from the code it describes. It does this from evidence it can see: commits, file changes, timestamps.
It cannot read intent. A plan marked fresh may be wrong, and a plan marked stale may be perfectly accurate. Treat the score as a reason to look, never as a reason not to.
2. Review and approval record decisions, they do not make them
Marking a plan accepted records that a person approved it. It is an audit trail, not an assurance that what was approved is correct, safe, legal, or a good idea.
3. Sync is between your machines
Flanner is not a backup service. Plans sync between devices you control, and we hold no copy. If every one of your machines is lost, so are the plans, unless you have a backup of your own.
Use git, or your normal backups. The plan directory is an ordinary directory of Markdown files.
4. Signatures prove authorship, not truth
Every version is signed by the device that wrote it, and any device can verify that history. That proves who wrote something and that it has not been altered since. It says nothing about whether the content is right.
5. Output from AI agents
Flanner stores and versions planning documents your AI tools produce. It does not check them. Anything an agent writes is the agent's output and your responsibility to review, exactly as it would be without us.
6. No professional advice
Nothing in the product or on this site is legal, financial, security or other professional advice.
7. The open-source client
The client is provided under the MIT licence, which disclaims warranty in its own terms. Read it in the repository.
Liability for the hosted service is addressed in the Terms of Service. Questions to support@flanner.io.