Private · local-first · human-controlled

Household operations, without surrendering control.

HomeOps helps its owner notice obligations in email, compare proposed events with Google Calendar, and review the next action through a private Telegram interface.

Operating model

The computer remains the authority.

The authoritative database and security controls run on the owner's Windows computer. Incoming content is treated as untrusted evidence, and proposed actions remain pending until policy and human approval requirements are satisfied.

Read narrowly

Email and calendar access use separate least-privilege OAuth permissions.

Review explicitly

HomeOps presents proposals for review instead of silently applying them.

Verify changes

Calendar writes require an exact request, local confirmation, and a read-back check.

Google permissions

Why HomeOps requests access

Gmail read-only

Reads authorized mailbox content to identify possible household tasks and deadlines. HomeOps cannot send, delete, or modify Gmail messages.

Calendar read-only

Compares a proposed event with existing calendar state so duplicate or already-completed work can be suppressed.

Owned calendar events

Creates or updates only events owned by the authorizing user, after explicit approval and local Windows Hello confirmation. HomeOps does not delete calendar events.

For details about processing, retention, external providers, and deletion controls, read the Privacy Policy.