Terms of Use

1. Nature and scope of the service

Vault is a mobile record-keeping and summary tool designed to help users track physical gold savings for personal use. It is not investment advice, not a custody service, not a bank, not a broker, not a portfolio management platform, and not a trade-execution system. Even under a user-favoring reading, the product should be understood as a personal tracking utility only.

The app does not execute trades for the user.
The app does not hold, transfer, or safeguard the user's physical assets.
The app is provided for personal tracking and organization.

2. The accuracy of entered data remains the user's responsibility

Portfolio summaries in Vault depend on the records entered by the user. If the user enters an incorrect amount, date, price, or incomplete transaction history, the resulting totals may also be incorrect. The app does not guarantee the factual correctness of user-entered data and does not independently audit it like a formal accounting system.

The user is responsible for accurate transaction entry.
Incomplete or incorrect entries directly affect totals and insights.
The app does not verify user data as an official ledger.

3. Price data is informational and may be wrong

Prices shown in Vault and the portfolio values derived from them depend on external data sources, cached values, and in-app calculation rules. Those values may be delayed, incomplete, inaccurate, or unavailable. In a user-first reading, the app should not be treated as the sole source for a financial decision.

Price feeds may lag or differ from real-time market conditions.
Portfolio totals may not fully reflect the current market at every moment.
Users should independently verify important pricing information.

4. Reminders, notifications, and beta features are not guaranteed

Reminders and notifications depend on device permissions, operating-system rules, battery optimization, local scheduling, and app version behavior. Reminder functionality may be marked beta and may not work consistently on every device. Users should not rely on this feature alone for critical or time-sensitive decisions.

Notifications may arrive late or fail to arrive.
Beta features may behave inconsistently or be removed.
No reimbursement or make-good promise is implied for missed reminder events.

5. A local-only model means data-loss risk is real

Vault does not currently provide active cloud sync or a developer-side central backup copy of the portfolio. If the phone is lost, reset, damaged, replaced, or the app is deleted, records may be lost. A user-favoring terms page should state this risk plainly.

Local records do not come with guaranteed long-term recovery.
Developer-side recovery cannot be promised in every case.
Data loss is a practical consequence of the current product architecture.

6. Features may change and service may not be uninterrupted

Vault's features, design, supported screens, and integrations may change over time. Features may be renamed, removed, temporarily disabled, delayed, or reworked. Even under a user-friendly interpretation, the product should not promise uninterrupted operation or an unchanging feature set.

Features may change for technical, legal, or product reasons.
Temporary outages, maintenance windows, or data-source interruptions can happen.
Old versions may not retain every behavior forever.

7. Liability limits should not override mandatory consumer rights

Vault's purpose is to provide records and visibility, not to guarantee profit, pricing accuracy, or a financial outcome. Decisions made by the user based on app totals, prices, reminders, or missing data remain the user's own judgment. At the same time, any non-waivable consumer rights and mandatory legal protections remain reserved and should not be read down by this page.

This app does not provide investment advice.
This app does not guarantee gains, price accuracy, or on-time alerts.
Any non-waivable consumer rights remain reserved.

8. Legal text must be updated when the product changes

These terms should be revised as the product's technical behavior changes. A user-favoring approach means updating this page promptly when new data flows, new service providers, new sync features, or major architectural changes are introduced. Before public launch, formal operator details and local legal review should also be completed.

The legal text should not conflict with the actual product behavior.
Technical changes should trigger a legal review of this page.
Formal operator details and local counsel review should be completed before publication.