Last updated: March 19, 2026

Security

1. Our Security Approach

WhenYouOpen is built around deeply personal content, future delivery workflows, account trust, and long-term preservation of meaningful digital memories. Because of that, we treat security as a product responsibility, not just a technical checkbox.

Our security approach is designed to protect:

• user accounts,
• capsule content,
• recipient details,
• scheduled delivery workflows,
• subscription and entitlement integrity,
• platform availability,
• operational trust.

While no internet-based platform can guarantee absolute security, we aim to use appropriate safeguards across application design, hosting, storage, authentication, monitoring, and operational controls.

2. Security Principles

We design our systems around a number of core principles:

• least-privilege access,
• authenticated access to protected resources,
• verification for high-risk actions,
• separation of responsibilities where practical,
• storage and delivery control based on account entitlement,
• auditability of key account and delivery actions,
• controlled handling of uploads and media,
• secure cloud-hosted infrastructure,
• ongoing operational review and improvement.

3. Account Security

To help protect accounts, WhenYouOpen may use measures such as:

• secure registration and login workflows,
• authenticated session handling,
• password-based authentication,
• OTP verification for sensitive operations,
• password reset controls,
• request validation,
• logging of authentication events,
• access restrictions on protected endpoints.

Users are responsible for choosing strong passwords and maintaining the security of their registered email account and phone number, since those channels may be used for verification and recovery.

4. OTP and Sensitive Actions

For higher-risk actions, additional verification may be required. This can include actions such as:

• account recovery,
• deletion of an account,
• decisions affecting scheduled capsule delivery,
• changes that materially impact delivery or identity assurance.

Where implemented, OTP verification may be sent to the registered email address, registered phone number, or both.

5. Capsule and Media Protection

WhenYouOpen stores capsule content and associated metadata in a controlled environment intended to support secure retrieval, entitlement enforcement, and scheduled delivery.

Depending on the feature and plan level, content may include:

• text messages,
• images,
• audio,
• video.

Current product rules distinguish content support by plan. For example:

• free-tier usage supports text and images,
• paid plans may support text, images, audio, and video,
• media attachments are subject to plan validation and entitlement enforcement.

We apply application-level checks to ensure content use aligns with plan permissions and associated storage rules.

6. Media Upload Handling

The platform architecture supports staged handling of media before association with a specific capsule. This is intended to reduce direct exposure and allow validation before content becomes part of a user's capsule record.

In general terms, media-related handling may include:

• temporary staging,
• content validation,
• association with the correct user and capsule,
• controlled movement into capsule-scoped storage,
• entitlement tracking,
• cleanup or purge handling for unused or invalid staged content.

7. Access Control

Protected platform functions are intended to require authenticated access. Authorization may be enforced based on identity, account ownership, resource association, and entitlement state.

Access control principles include:

• users should access only their own data unless a delivery workflow intentionally shares content with a recipient,
• protected APIs should validate identity and ownership,
• administrative or operational access should be restricted,
• sensitive changes should be auditable.

8. Infrastructure and Hosting

WhenYouOpen is designed to run on cloud infrastructure with platform-level protections such as managed hosting, secure network boundaries, monitored environments, and controlled service access.

Depending on the environment, security practices may include:

• HTTPS/TLS for in-transit protection,
• secured application hosting,
• managed storage services,
• environment isolation,
• secret/configuration protection,
• platform diagnostics and operational monitoring.

9. Data in Transit and at Rest

We aim to protect data in transit using HTTPS/TLS. We also rely on storage-layer and infrastructure-layer protections offered by the cloud environment for data at rest where applicable.

Some data may also be protected through controlled access patterns, application-level validation, and service-level security configuration.

10. Logging and Monitoring

We may maintain logs and monitoring data to support:

• login and authentication tracking,
• error diagnosis,
• performance monitoring,
• suspicious activity detection,
• operational troubleshooting,
• audit and integrity review for key events.

Logs are used to support platform security and reliability and are accessed only as needed for operational, support, compliance, or security purposes.

11. Subscription, Entitlement, and Data Lifecycle Controls

Because WhenYouOpen operates with subscription-based feature access and one-time add-on capsules, security and integrity also include entitlement controls.

This means the platform may enforce:

• whether a user can upload certain media types,
• how many capsules a user can create,
• what storage is permitted,
• how downgrade and lapse events affect access,
• reminder and grace workflows before premium data is purged,
• retention of individually purchased add-on capsules where applicable.

These controls help ensure users receive the service level they purchased while preserving consistent system behavior.

12. Deletion, Downgrade, and Purge Security

Where accounts or premium entitlements are deleted, expired, or downgraded, associated workflows may trigger export reminders, grace periods, restricted access, or purge operations.

For account deletion with scheduled capsules pending, the platform is intended to prompt the user regarding whether to:

• keep all scheduled deliveries,
• cancel selected deliveries,
• cancel all pending deliveries,

with OTP verification required before destructive action is finalized.

These controls are designed to reduce accidental or unauthorized loss of meaningful future deliveries.

13. Third-Party Providers

We may use carefully selected third-party providers for infrastructure, communication delivery, authentication support, payment processing, monitoring, or storage. While these vendors provide important security capabilities, their systems are governed by their own practices and policies.

14. User Responsibilities

Users also play an important role in security. You should:

• use a strong, unique password,
• keep your email and phone secure,
• avoid sharing login credentials,
• verify recipient details carefully,
• review scheduled delivery information before saving,
• contact support if you suspect unauthorized activity.

15. Reporting Security Concerns

If you believe you have discovered a security vulnerability, account compromise, or suspicious issue affecting WhenYouOpen, please contact us promptly through the support or contact information listed on the website. Please include enough detail to help us investigate responsibly.

16. No Absolute Guarantee

Although we work to protect the platform and user data, no method of transmission, storage, or electronic processing is completely secure. For that reason, we cannot guarantee absolute security.

17. Updates

We may update this page from time to time to reflect changes in infrastructure, product design, security controls, or legal expectations.