Privacy Policy

Overview

whome is self-hosted household software. Your operator (typically a family member who runs the server) controls the instance, data storage, and who may sign in. This policy describes what the application stores and how optional third-party services are used.

Information we store

• Account identifiers (email, username, display name, profile photo)
• Household content you create (calendar events, lists, notes, expenses, school work, drive files)
• Session and authentication tokens (HTTP-only cookies on your domain)
• Optional push notification subscription endpoints if you enable Web Push

Google sign-in and Calendar (optional)

If your operator enables Google OAuth, you may sign in with Google or connect Google Calendar. Google receives standard OAuth requests according to Google's Privacy Policy. Calendar sync exchanges event data between your household database and Google Calendar when configured. OAuth tokens are encrypted at rest on your server.

Third-party services

• Weather — dashboard forecasts may call Open-Meteo using coordinates you provide; no account is required.
• Object storage — file uploads use S3-compatible storage configured by your operator (e.g. MinIO on the same server).
• Web Push — browser vendors (Google, Apple, Mozilla, etc.) deliver notifications when enabled; subscription keys are stored on your server.

Data sharing

Household members with access to your instance can see household-visible content per module permissions. Private notes and drive objects are visible only to owners and members you explicitly share with. The whome project does not operate a central cloud database for self-hosted deployments.

Your choices

Contact your household operator to update profile data, revoke calendar connections, or request account removal. Operators can export or delete data by managing the PostgreSQL database and object storage directly.

Contact

For privacy questions about a specific whome instance, contact the person who administers your household server.