Skip to main content

Data Safety & Trust Boundaries

Smart Without Spying​

HausFlow is designed to be useful without becoming invasive.

The trust standard is:

  • use the minimum data needed
  • keep explanations plain
  • avoid creepy product behavior
  • give users control where possible

What Smart Features Should Use​

  • event counts
  • timing patterns
  • completion signals
  • feature usage trends

What Smart Features Should Not Require​

  • reading private content by default
  • mining sensitive personal details
  • building manipulative psychological profiles
  • pretending the product knows more than it actually does

User Control​

Where supported in a given build, users should be able to:

  • manage notifications
  • disable optional smart features
  • export their data
  • delete their account

Third-Party Boundary​

Third-party services should only receive the data needed for their role.

HausFlow does not authorize third parties to sell user data for advertising through its integrations.

Security Standard​

HausFlow aims to protect data through:

  • secure transport
  • controlled access
  • reasonable storage protections
  • ongoing reliability and security improvements

Core Trust Rule​

The product should feel helpful, not watchful.

That rule should stay true across Family, Roommate, and future Professional or white-label editions.