Privacy notice · Version 2026-10-15-privacy2

Your privacy
in Vault.

Vault has no advertising or marketing analytics. Operating encrypted messaging still requires account, delivery and security information.

Effective October 14, 2026. This notice covers Vault’s messaging service, support website and support correspondence.

Who is responsible

The operator of Vault Messenger is responsible for the processing described in this notice. Vault Messenger is an independently operated service based in Switzerland and is the product name, not a separate company.

Contact privacy@vaultmsg.ch about personal data or support@vaultmsg.ch for app support. You do not need to give Vault your legal name, postal address or identity document to register; a display name may be a nickname.

Accounts & contacts

Vault processes your account and device identifiers, registration phone number or eligible username, display name, public keys, recovery and authorization information, profile and subscription status. This information supports sign-in, recovery, contact discovery and secure connections. Account information is not all end-to-end encrypted.

Phone registration uses Google Firebase to send a verification SMS. Google also receives and stores authentication phone numbers for spam and abuse prevention across its services, as explained in its phone authentication information. Your carrier’s messaging charges may apply.

With Contacts permission, Vault reads contact phone numbers into a local cache. It does not bulk-upload your address book. Looking up a particular phone number sends that normalized number to the Firebase directory; username lookup similarly queries a username. Contact requests, public profile information and connection permissions are processed to let people connect. Sharing a profile with a contact is separate from reading your address book.

Messages & notifications

Message and attachment payloads are encrypted before transmission. Local history is stored encrypted. Participating phones and the central relay may hold encrypted delivery payloads for eligible delivery modes. Strict conversations do not use those payload mailboxes.

Delivery requires account and device identifiers, public keys and message-routing information. Infrastructure and connected peers also process network addresses, connection timing and data sizes. Message encryption does not hide all connection information.

Apple and Google process device notification tokens and routing information to deliver alerts. Push payloads exclude message text, attachments and message keys. Notification permission and device settings affect delivery.

Support & security

Vault has no advertising or marketing analytics. Service providers process technical request information and security records to operate the service, prevent abuse and investigate failures. Firebase Authentication and Firestore also declare SDK diagnostic collection for technical analytics in their supplied privacy manifests. This is separate from advertising or marketing analytics.

An optional in-app report sends the text you enter, its category, platform and app version. Authentication and abuse controls protect report submission. Reports contain the information you submit and the app information described above.

If you contact support or privacy by email, we process your address, message and any attachments to respond. Email is separate from Vault’s encrypted messaging; do not send passwords, recovery secrets or unnecessary personal details.

Providers & locations

  • Google/Firebase: authentication, account and routing data, backend processing and Android notifications. The account database is in Europe; authentication and backend processing also take place in the United States. See Firebase privacy information.
  • Cloudflare: website hosting and network services, including technical request information such as network addresses and browser headers.
  • Email service providers: process support and privacy correspondence.
  • Apple: iOS notifications and app distribution.
  • Delivery and connectivity providers and participating devices: process encrypted payloads and the connection information needed for delivery.

Processing is not confined to Switzerland. Providers may process data in Europe, the United States and other countries where they operate; legal protections can differ. Provider terms and international-transfer arrangements apply to their services. You can contact us for information about the providers and arrangements relevant to your data.

We use information to provide the requested service, protect it, respond to voluntary requests and meet applicable legal obligations. Where applicable law requires a legal basis, these purposes rely on providing the service, legitimate operational and security interests, legal obligations or consent where required. Optional permissions are not blanket consent to unrelated uses.

Payments & membership

If you use hosted Pro checkout, Vault processes the selected plan, price, currency, checkout reference, payment status, membership period, accepted terms and automatic-renewal choice. Provider customer, mandate, payment and subscription references connect verified payments and cancellation to your account. These records remain personal data when linked to you.

Mollie handles supported cards and wallets; CoinPayments handles supported cryptocurrency invoices. You enter payment information on the provider’s page. Depending on the method, the provider may process your name, contact or billing details, payment method, transaction and network information for payment, fraud prevention and legal obligations. Vault can access payment and payer information made available through its merchant tools. Blockchain transaction information may be publicly visible. Hosted checkout does not make a payment anonymous.

The return page uses a secure cookie lasting up to 30 minutes to retrieve payment status for the same checkout. It does not authorize another purchase or subscription cancellation. The payment page does not load advertising or analytics scripts.

Billing records support membership, reconciliation, cancellation, refunds, disputes and applicable accounting obligations. Deleting a messaging account does not automatically erase records still needed for those purposes. See Mollie’s privacy notice and CoinPayments’ privacy information for their processing.

Retention & deletion

  • Account and profile data: used while the account operates. In-app deletion removes active account and directory records and local account data; authentication and some connection cleanup may finish through backend retries.
  • Encrypted central delivery records: expire no later than 30 days after their record timestamp. Expired records cannot be retrieved and are removed by housekeeping. Local history, independent recipient copies and backups have separate lifecycles.
  • Notifications: backend requests expire within 24 hours and are then eligible for cleanup. Apple or Google may retain notification requests for up to 72 hours.
  • Optional bug reports: become eligible for deletion around 90 days after submission. Temporary abuse-control records expire within two days.
  • Acceptance and security records: records of policy acceptance and account security can remain after account deletion to demonstrate the agreement, reject obsolete credentials and handle security or legal issues. They currently have no fixed automatic expiry.

Automatic expiry does not guarantee immediate erasure from every backup or provider system. Google states that Firebase Authentication deletion from live and backup systems can take up to 180 days after account deletion is requested.

For correspondence, technical logs, backups and records without a fixed expiry, retention depends on resolving the request, investigating incidents, preventing replay or abuse, applicable legal needs and provider retention settings. Contact us to request a review or deletion of information no longer needed for those purposes.

Account deletion does not erase copies already received by other people or promise that every retained record disappears simultaneously.

Your choices & rights

You can manage optional device permissions in your phone’s settings and choose whether to send reports or email. Some features require their associated account or connection information to work. This notice does not require an additional personal-information form.

To delete an account, use Settings → Account management → Delete account and all local data, complete both confirmations and keep the app connected until it finishes. Uninstalling alone does not delete backend records. Contact privacy@vaultmsg.ch if you cannot use the app.

Depending on applicable law, you may request access, correction, deletion or a copy of your data, object to or restrict processing, and withdraw consent for optional processing. We may need proportionate proof that a request concerns your account; do not send passwords or recovery secrets. You may also complain to your competent data-protection authority. These rights are not reduced by accepting the terms.

Material changes receive a new version and are communicated through the app, support site or distribution notes. Earlier notices can be requested from our privacy contact.