What stays separate
- Secure records are intentionally separated from normal notes and references.
- Sensitive context is not mixed into public-facing product media.
- Screenshots for marketing use deterministic demo content only.
Privacy Model
Sensitive by design.
HourLife distinguishes between ordinary references and intentionally sensitive information, so trust is explicit.
Privacy principle
HourLife treats personal operating data as sensitive by default and separates high-sensitivity records from ordinary planning notes.
Data clarity
- Know what belongs in Secure Box versus general module storage.
- Understand export behavior before trusting the system with core life data.
- Use private workflows for personal records, not ad-hoc note dumping.
Marketing data rule
Public screenshots and demos use deterministic sample content only.
Operational clarity
Users can understand where sensitive data belongs before they commit trust.
Long-term trust
Privacy is treated as product architecture, not a legal afterthought.