Role-aware access
Parents, nannies, babysitters, support users, and super-admins have different views and permissions.
Security and privacy
Built around trust, boundaries, and human control.
Homeflow coordinates sensitive household information, so access boundaries, auditability, and careful support workflows are core product requirements.
Today's Overview
7:30Role-aware access
8:30Audit trail
9:30Confirmation gates
Forecast
72°F
Warm, clear, and good for outdoor plans.
9 AM
Sun
12 PM
Sun
3 PM
Sun
Parent Note
We are going on a trip this weekend. Please help the kids pack snacks and prep for the drive.
Permission checks
Confirm sensitive actions
Human control remains visible.
Keep caregiver views scoped
Human control remains visible.
Audit-ready support
Dinner prep
Lunch notes
Shopping list
Trust principles
Private household context needs a careful operating model.
Security language on this page is intentionally plain and conservative. Homeflow does not replace emergency services, doctors, legal advice, payroll advice, or parent judgment.
Household scoping
Household data is designed to stay scoped to the active household and role.
Human approval
Sensitive AI-assisted actions are designed around confirmation instead of invisible automation.
Support boundaries
Support access is separated from daily household use and routed through scoped, audited controls.
Private-data care
Marketing, support, status, and public pages must not expose real household data, credentials, or private child details.
Emergency boundary: Homeflow is not an emergency dispatch service. In an immediate emergency, call 911 or your local emergency number first.
Questions about security or privacy?
Contact support without sending passwords, verification codes, private child details, OAuth tokens, or screenshots containing sensitive household data.