homie.
Help centerPrivacy and memory

Privacy and permissions

Personal stays personal. Shared stays shared. Risky actions wait for approval.

Updated en11 sections
Read inENDESV

Personal stays personal. Shared stays shared. Risky actions wait for approval.

Homie is designed around a local household system. Most household information stays on the home machine and is used by the features you turn on.

Some website and sign-in pieces use cloud services, but the manual rule is simple: personal content should stay with the right person, and household content should stay under household control.

Homie can use local household context, connected services, and model providers according to the features you enable.

- Trusted device identity

- Configured accounts and connectors

- Local memory, calendar, reminders, and skill data

- Approval cards for actions that need a human decision

Homie should not silently cross privacy or action boundaries.

- It will not show private personal chats on the shared iPad.

- It will not send, call, book, or start risky future actions without approval.

- It will not treat email content as trusted instructions.

Device trust, member profiles, connected accounts, mail routing, microphone access, and optional skills each have their own setup steps.

Saved household information is changed only by Homie on the household Mac. Other background work may read what it needs, but it is not allowed to quietly edit those records.

Read the privacy boundary before trying to fix behavior. Homie often behaves differently on a shared screen than on a claimed personal phone.

- Claim personal phones during setup.

- Review connected accounts in settings.

- Use approvals as the audit point before Homie reaches outside the household.

Most Homie issues come from setup, identity, or approval state. Work through these checks before assuming Homie ignored the request.

- Check whether you are on a shared household surface or a claimed personal phone.

- Ask Homie what it can see from this device before assuming memory is missing.

- Use explicit language such as keep this private, share this, remember this, or forget that.

What stays private: If Homie cannot identify the speaker or device, it should default away from confidential member memory.

Good to know: Approvals are blocking interrupts, not quiet pending items. They render as action cards on the relevant device or chat.

- Claim personal phones during setup.

- Review connected accounts in settings.

- Use approvals as the audit point before Homie reaches outside the household.

- What can you see from this device?

- Show me what is pending approval.

- Keep this private to my phone.

Back to help