Privacy Policy

1. How this product handles data

Vault is primarily designed to keep financial records on the device instead of relying on a central account system for core use. That means your portfolio entries, transaction history, goals, tags, and reminder settings are intended to live first in local storage on your phone.

Your portfolio records and transaction history are stored on your device.
Vault does not currently offer active cloud sync.
The core app does not require a central portfolio account for basic use.

2. What technical data may still be sent by default

Vault may keep anonymous usage metrics and anonymous crash reporting enabled by default. That means the app should not be described as fully offline or as a zero-transfer system. Limited technical data may still be sent to understand product usage and diagnose failures.

Anonymous usage and crash telemetry may be sent unless the user disables it.
These settings can be turned off in the app.
Because they may be on by default, technical data transfer can happen until the user changes that choice.

3. What we aim not to share

Vault's current design aims not to collect the contents of your portfolio as analytics input. Even so, no technical system should be described as risk-free. This page should not be read as an absolute promise of perfect isolation or perfect anonymity.

Portfolio values and gold quantities are not intended to be analytics payloads.
Personal notes and record contents are not intended to be telemetry targets.
Technical crash context and device-level diagnostics may still reach third-party infrastructure.

4. Third-party infrastructure and data transfer

The app may use third-party infrastructure for analytics and crash diagnostics. This means some limited technical data can leave the app and be processed by outside service providers. Even in a user-favoring reading, that transfer should not be ignored.

Anonymous usage and crash data may be routed to third-party systems.
That means the product is not literally 'device-only' in every technical sense.
Third-party providers may also apply their own retention and security policies.

5. User controls and user rights

Vault aims to expose the controls that currently exist in the product, but those controls are still limited. There is no active self-serve export flow, no central backup, and no developer-side restore promise for your full portfolio. The user-first commitment here is that the sharing settings that do exist should remain visible and changeable.

The usage-sharing setting can be turned off.
The crash-report setting can be turned off.
Privacy Mode can hide visible portfolio amounts on screen.
If the app is removed, local data may be deleted from the device.

6. Retention, data-loss risk, and practical limits

A local-first model may improve privacy, but it also shifts a large part of backup risk to the device itself. If the phone is reset, replaced, damaged, or the app is uninstalled, records may be lost. Vault does not currently promise a developer-side backup copy that can always be restored later.

Local records depend on the life cycle of the device and app installation.
Uninstalling the app or resetting the device may cause data loss.
Because there is no active cloud copy, recovery may not always be possible.

7. Transparency and future updates

This page is meant to reflect the app's current technical behavior as clearly as possible. If new data flows, new third-party services, or sync features are added, this page should be updated without delay. Before launch, the formal operator identity and legal contact details should also be completed.

The legal text should stay aligned with the technical product behavior.
New data collection paths should be disclosed separately.
Formal controller identity and legal contact details should be completed before publication.