Login and registration should only require the fields needed to authenticate and maintain access.
0FDI 000
Privacy
Privacy should be readable at newsroom speed.
Fracture should collect only what the product needs, protect account data, and keep reader feedback separate from editorial analysis unless a user submits it.
Reader review signals should be used to improve analysis quality, not to profile readers.
Source article URLs and outlet metadata are treated as public editorial inputs.
Account data is product data, not editorial data.
Authentication information should be stored and handled separately from story analysis, source scoring, and public article data.
Reader actions should stay intentional.
Searches, watchlists, comments, and review requests should be designed so users know when they are creating a saved signal or sending feedback.
External source links stay inside Fracture context.
Source brief modals show outlet metadata and article context without forcing the reader out of the app during comparison.
This page is a product placeholder.
Before launch, this page should be reviewed and replaced with legal language that matches the deployed data practices and jurisdiction requirements.
Fracture keeps the product focused on source comparison, framing distance, and readable context instead of performative certainty.