Skip to main content

Legal

Sub-processors

The third parties LifeWyn relies on to run the Service — and, under the zero-knowledge model, the strict limit on what each one can actually see.

Last updated: August 28, 2026

Template notice. This list is maintained in good faith and describes the categories of sub-processors a zero-knowledge platform like LifeWyn uses. It is not legal advice. Before you rely on it, qualified counsel and your operator should confirm the exact named vendors and regions for your deployment.

A sub-processor is a third party that processes data on our behalf. Because LifeWyn is zero-knowledge, vault content and the keys that open it never leave your devices in plaintext — so the sub-processors below handle ciphertext, routing metadata, and notifications only, never the contents of your vault.

Infrastructure

Sub-processorPurposeData processedLocation
Oracle Cloud Infrastructure (OCI)Application hosting, managed Postgres, and encrypted object storage for ciphertext blobs.Encrypted vault blobs, ciphertext document objects, account metadata. No plaintext content or keys.Region configured per deployment

Operational

Sub-processorPurposeData processedLocation
Transactional email providerDelivery of verification, security, and inheritance-workflow emails.Recipient email address and message content (notifications only — never vault content).Configured per deployment
SMS / WhatsApp providerOne-time codes and critical alive-signal / release notifications.Recipient phone number and message content (codes and notifications only).Configured per deployment
Payment processor(s)Subscription billing. Card/UPI via the web checkout gateway; in-app purchases via the mobile app stores.Billing identifiers and payment tokens handled by the processor. LifeWyn stores no card numbers.Per gateway / app store

Changes to this list

We will update this page before adding a new sub-processor that handles account or notification data. The Data Processing Addendum explains your right to object; see the DPA.