We build for trust inside the home, not surveillance around it.
Home Life Connected is meant to help households coordinate life together, not to quietly extract more from the people using it. This page is our plain-language commitment to how we treat personal, household, and shared information across the app.
We only want data that helps the product actually work. If a feature does not need something, it should not be collected just because it can be.
Shared features should behave like transparent collaboration tools. Personal features should stay personal unless you explicitly share them.
This statement is intended to stay readable by normal humans, not just satisfy a checkbox.
Our privacy promise
We aim to collect the least amount of data necessary to run the service well, give people understandable controls, and avoid surprising behavior. Household software should feel reliable and supportive, not manipulative.
If data is shared across a household, the product should make that obvious.
Personal-first features should not become hidden household broadcasts.
Defaults should favor clarity and restraint, especially around personal details.
If information moves between modules or providers, that movement should be intentional.
What we collect to operate the app
Depending on which features you use, Home Life Connected may store account details, household membership and role data, messages, calendar items, settings, profile photos, notifications, wellness preferences, and connected-provider tokens needed for services like calendar import.
Account and access data
Usernames, email addresses, display names, login sessions, trusted-device state, and platform or household roles are used to secure and organize access.
Household and coordination data
Shared planning items, chores, calendar items, invites, member lists, and settings are used to support collaboration inside a household.
Connected services
If you connect Google or Microsoft calendars, we store the credentials and imported event data needed to provide read-only sync. The current implementation is intentionally read-only.
How we use information
- To authenticate you and keep accounts secure.
- To show household-specific and personal-first information in the correct places.
- To power messaging, scheduling, weather, notifications, and connected calendar imports.
- To troubleshoot reliability, performance, and misuse of the service.
We are not trying to build an ad-targeting machine out of household data. The product is meant to help life run better, not to harvest behavioral profiles for unrelated purposes.
Your controls and expectations
Users should be able to understand what belongs to them, what belongs to the household, and what belongs to the system itself. We try to design features so people can make informed decisions without needing a microscope or a law degree.
- You can update or remove profile photos and personal profile details.
- Imported external calendar data stays read-only unless a future feature explicitly changes that.
- Some features are household-wide by design, while others are personal-first; the distinction matters.
- Administrative visibility should not silently become ordinary-user visibility.
Security and retention
We use reasonable technical measures to secure accounts, sessions, and stored credentials, including authenticated access controls and protected server-side handling for sensitive integration tokens. No system can honestly promise perfect security, so we also try to reduce risk by limiting unnecessary data flows.
We may retain operational data, logs, and history for reliability, support, abuse prevention, and continuity of service. Retention practices will continue to evolve as the product matures, and we intend to keep those decisions understandable and proportionate.