docs: add a consolidated Data Deletion page (FIL-894)

[filipagr]

Re-opens the work from #27, which was merged before it was meant to go live and has been reverted off main (ba20747). Content is byte-identical to what #27 merged (git diff aedc15d HEAD is empty), so nothing was lost and nothing needs re-reviewing beyond what was already discussed.

Merge this when the page should be published.

Why this is a revert-of-a-revert rather than the original branch

Re-merging filipa/fil-894-data-deletion would restore nothing. Git already considers those commits merged into main, so the merge would be a no-op and the page would silently stay missing. This branch reverts the revert, which is the standard way back.

What the page says

Single reference for what deletion means at the object, bucket, and account level, for due-diligence and data-subject-request answers. Object deletion (including delete markers and the billing consequence on versioned buckets), bucket deletion, deletion under Object Lock, account closure, residual data in sealed sectors, account records beyond stored objects, and a limits section.

Review feedback already addressed in here

• "What Fil One does not claim" read as a double negative. Heading is now Limits of these guarantees, so the No ... bullets scan correctly.
• "It stays encrypted" was too broad for a page covering account-level deletion. Correct for object data on the storage network, but not for account records Fil One holds itself, which sit under different encryption and key-custody arrangements, or for the sign-in cookie, which is signed rather than encrypted. New Account data beyond your stored objects section covers this. Written generically, since the repo forbids naming internal infrastructure or vendors in the docs. If those specifics should be named publicly, that is a deliberate disclosure decision, not a wording fix.
• The erasure claim was untrue. "Erasure available on request" is not something we can promise. Now: closure revokes access, nothing is erased automatically, and anyone with a regulatory deadline is pointed to support for their own account.
• Deletion is not cryptographic destruction. One bullet in Limits, framed as a scope boundary: deletion removes access, key destruction is not guaranteed. The structural bucket-versus-object point is kept because it explains the limit.

An earlier revision of the last two points published our internal investigation status and singled out a region as lacking account-level removal. That was pulled out in 7e3b17c before the merge. There is no process narration or region-specific gap language on the page.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
filone-docs	Ready	Preview	Aug 6, 2026 8:51pm