In short
Raw writing samples and the source text you paste to generate are not stored — they're used once and discarded. What persists is the profile you build and the outputs you explicitly choose to save, held in a workspace only you can access. Operational logs record metadata, never your writing.
Content Flow is a private tool for creating reusable writing style profiles and drafting content in those styles. This page explains, in plain English, what happens to the material you put into the tool and what actually gets stored.
Writing samples
When you create a style profile, you paste authorised writing samples that represent the communication style you want the profile to learn from. Those samples are sent once to the analysis service, which reads them for tone, structure and communication patterns. The samples themselves are then discarded — not stored, not logged, not written to the Content Flow database.
What's kept is the profile the analysis produces: the reusable style guidance, not the source writing. The samples used to build it do not persist.
Source text you paste into Generate
When you generate a draft, you paste source text — the facts, points or brief you want the draft to cover. That text is sent to the generation and review services only when you trigger those actions. It is not saved to the database, not logged, and not kept as a record.
Worth knowing
If you refresh the page or navigate away, the source text is gone. You'd need to paste it again next time — it's genuinely not being held anywhere.
Generated drafts
The draft Content Flow produces is session-only by default. Close the tab without saving and it disappears.
If you click Save output, the draft is stored in your signed-in workspace, along with which profile was used and how the review checks came out. The source text you pasted to generate it is still not stored — only the draft itself, its title, its subject line if it's an email, and the review outcome.
What is stored in your signed-in workspace
When you sign in, Content Flow connects to a workspace that only you can read from and write to. That workspace holds:
- Style profiles you've created — the Personal Voice or Brand Voice profiles describing the writing style for a person or brand.
- Saved outputs you've explicitly chosen to save.
- Versions — if you edit a saved output as a new version, the edit is kept as a linked version of the original.
- Projects — optional groupings you can use to organise saved outputs.
Each of these is scoped to your account. The database is set up so signed-in users can only access the workspace data they're allowed to — enforced at the database level, not just hidden in the app. The API key that lets Content Flow generate content lives only on the server side; it's never sent to your browser or exposed in any page.
Deletion and archive
Normal app controls archive items rather than permanently deleting them. Archived items are hidden from everyday views and can be restored where the app offers a restore option. If permanent deletion is needed, it's handled separately through an admin or support process.
What Content Flow doesn't do
- No analytics tracking on your usage.
- No third-party cookies.
- No pixel trackers or session replay.
- No sharing of your data beyond the analysis, generation and review services — which are called only when you trigger them.
- No advertising anywhere in the tool.
Your part
Only paste writing samples or source material you're authorised to use. Content Flow's storage rules limit what's kept, but authorisation to use the material in the first place is always yours to confirm — not something the tool can check for you.