Data ownership
Your words should not be trapped here.
WordFloor is being built around private writing, human-readable export, and user-controlled retention. What follows is the planned approach. The product is pre-launch, so some details will be confirmed closer to release.
Export
WordFloor is designed with human-readable export from the start. Export is not a paid-only add-on — your writing and activity record can leave with you.
Planned export formats include Markdown (one file per entry with frontmatter), a CSV activity record, and a JSON manifest. The export will preserve your words, effort data, and settings in standard formats that you can open and read without any special tools.
Words and effort are separate
WordFloor separates the words you write from the evidence of writing. You may delete the raw text of an entry while preserving the habit date, word count, and activity record. The square — the proof you showed up — can survive the content.
This means your writing history is yours to control: delete the words when you no longer need them, but keep the evidence of showing up. Both operations are designed to be explicit and reversible within any applicable retention window.
Deletion and retention
Deletion is not a vague UI gesture. WordFloor is being designed with explicit deletion semantics:
- You can delete an entry's text while preserving the activity record and word count.
- You can delete the entire entry record, including its contribution to activity history.
- Retention policies may be applied per entry or as account defaults.
- Future deletion tombstones will preserve deletion intent and audit information.
Retention applies to raw text payloads. The activity record (dates, word counts, floor met status) is designed to be more durable. The exact retention defaults and user-configurable options will be documented before the first private writing features launch.
Pre-launch status
WordFloor is pre-launch. Before private writing features launch, full documentation will be published covering export formats, deletion workflows, retention defaults, and account closure.
The product is being built such that privacy, export, and deletion semantics are core constraints — not afterthoughts.