Security
Security that matches what you’re trusting us with.
Our Life Pack is in development. This page explains the security principles it is being designed around — not finished guarantees.
Our Life Pack is in development. The measures below are design requirements and plans. Some are not yet built. We will update this page as they ship rather than describe them as complete in advance.
Secure sign-in
Secure authentication is planned, with sign-in options designed around Apple, Google, and email-based accounts, including passkey support in the architecture.
Encryption in transit
Connections between the app, the website, and our services are required to use transport encryption.
Encryption in the cloud
Server-side encryption is a baseline requirement for account data and for any media you choose to back up.
Sessions and devices
You should be able to see where you’re signed in, sign out remotely, and receive security login alerts.
App lock and hidden Life Packs
Biometric or device-passcode app lock, plus the ability to lock or hide individual Life Packs.
Revocable share links
Every share link can be revoked. Paid plans add optional PINs, expiration dates, and limited-use links.
Support without snooping
Support tools are designed to show technical and account state — not your private photos or Life Pack content. Any exceptional access in the future would require least-privilege roles, audit logging, and an explicit policy.
Threat modeling first
Before cloud media backup launches, we will complete a threat model covering account takeover, lost devices, link leakage, server compromise, shared-permission edge cases, account recovery, and support access.
Plainly stated
On end-to-end encryption
End-to-end encryption for cloud-backed content may be evaluated, but Our Life Pack does not offer or claim it today. We won’t market it until it is implemented, verified, and supported by a sound account-recovery model.
Responsible disclosure
Found a security issue?
Please email security@ourlifepack.com with a description of the issue, steps to reproduce it, and any relevant details. Please don’t access or modify other people’s data, and give us a reasonable chance to fix the issue before sharing it publicly.