Skip to main content
FFiscal Vitals
PrivacyTermsHome

Prelaunch support

Support

Fiscal Vitals is coming soon. This page explains the support the app is expected to need, but no dedicated Fiscal Vitals support channel has been verified yet.

ON THIS PAGE

Current statusBasic checksData and citationsAssistant helpPurchasesPrivacy and deletionFuture bug reportsContact gap
01

Current status

The app is in development and this website provides prelaunch information. There are no App Store or Google Play download links on this page, no website email list, and no live website support form. “Coming soon” is not a promise of a release date.

02

Basic troubleshooting

For a submitted app build, the first checks should be:

  • Confirm the device has a working internet connection for fresh public data and any enabled online feature.
  • Check the source date shown in the app. A published government record may update less often than a continuously moving clock.
  • Close and reopen the app if a screen is stuck. Avoid deleting the app if you still need locally saved questions or explanations.
  • Install the latest store version when one exists. Device, operating-system, and regional feature availability can differ.
  • If the app shows a short support reference after a failure, preserve that reference; do not send the full question, payment details, or a password.
03

Public data, freshness, and citations

Fiscal Vitals is intended to show the record date or period and source for supported figures. Different services can show different numbers because one uses the latest published government record while another estimates between releases, or because definitions and units differ. Public data can also be revised.

Before reporting a suspected data problem, compare the source name, date or period, units, revision status, and cited record—not only the headline number. The app is informational and is not financial, legal, tax, accounting, or investment advice.

04

Assistant and saved-work issues

Deterministic answers should remain available without cloud AI for supported questions. On-device AI depends on compatible Apple hardware and software. The separate external cloud-AI path is marked unavailable in the reviewed settings. Apple Private Cloud Compute, if used, is off-device and must not be confused with processing entirely on the phone. Route availability must be verified in the submitted build.

Saved questions and source-bound explanations can be held in bounded local app storage. Storage can become unavailable or full, and expired records may be pruned. Clearing app storage or uninstalling can remove local work. Export anything important before taking a destructive troubleshooting step when an export feature is available.

05

Purchases, restore, and cancellation

Subscriptions are not advertised as live on this website. The source contains a prepared native purchase-and-restore path, but production products, pricing, trials, legal links, and provider configuration have not been confirmed active.

If billing is activated later:

  • Use the price, billing period, renewal, and trial eligibility shown by the Apple or Google payment sheet.
  • Use Restore Purchases for an eligible purchase associated with the same store account.
  • Manage or cancel an active subscription in the relevant Apple or Google subscription settings. Uninstalling the app or deleting local data does not cancel it.
  • For a charge or refund issue, retain the store receipt or order identifier but never publish it or enter payment-card information into a support message.

No response-time or refund promise is made here. Final support procedures must match the store's rules and applicable law before billing is enabled.

06

Privacy and data deletion

Read the privacy policy draft for the current data map and launch gaps. The reviewed app architecture has no user-facing Fiscal Vitals account. Local app data and potentially service-held anonymous data require different deletion steps; see the data deletion page.

07

What a future bug report should include

Once a verified support channel exists, a useful report should include the platform, device model, operating-system version, Fiscal Vitals app version, the screen or feature involved, what happened, what was expected, and a short support reference if shown.

Do not include passwords, authentication tokens, payment-card details, a full store receipt, personal financial information, confidential documents, or the complete text of a sensitive assistant question. Screenshots should be reviewed and cropped to remove private information before sending.

08

Support contact is a launch blocker

A dedicated, tested Fiscal Vitals support mailbox or request form has not been verified. This page intentionally does not publish the historical unverified address or point to a general form as if Fiscal Vitals delivery were confirmed.

Before store submission, the owner must provide and test a public support URL and reachable support contact, define who monitors it, and establish procedures for privacy, billing, safety, and urgent store inquiries. Until then, this page is useful guidance but not a complete store support destination.

Fiscal Vitals is coming soon

FFiscal Vitals

Coming soon

PrivacyTermsSupportData deletion