Our approach
- Encryption in transit using modern TLS.
- Access controls and role-based household permissions.
- Secure credential handling and session management.
- Logging, monitoring, backups and vulnerability management appropriate to the production environment.
- Restricted administrative access and support procedures.
Document protection
The final public claims about encryption at rest, client-side encryption, key management, backup location and administrator access must match the implemented architecture. Household OS should not describe the service as “end-to-end encrypted” unless technical testing confirms that the provider cannot access document plaintext.
Your responsibilities
- Use a unique password and enable multifactor authentication when available.
- Keep invite links private and regularly review household members.
- Protect devices with a passcode, biometrics and current operating-system updates.
- Report lost devices and suspicious access promptly.
Report a concern
Email security@householdosapp.com. Do not publicly disclose personal data or active credentials.
Legal review notice: This operational draft should be reviewed by a UK-qualified solicitor and checked against the final app, payment, analytics, hosting and data-processing configuration before public launch.