No user-facing Fiscal Vitals account
The reviewed source uses opaque anonymous sessions for optional online services and can use anonymous billing state, but it does not provide registration, username/password login, or a cross-device Fiscal Vitals profile. On that architecture there is no user-facing app account for a user to close.
Before submission, the operator must confirm that an anonymous session is not implemented or classified as an automatically created guest account. If account creation is added—or a store treats the release architecture as account creation—this statement will no longer be sufficient. The app and website would need clear account-deletion paths and deletion of associated data, and the store declarations would need to be updated.
Delete local app data
The app can store source-bound questions and explanations, public-data snapshots, operation status, preferences, and usage counters in its local app storage. A submitted build should expose any available item-level or clear-data controls accurately.
Clearing Fiscal Vitals app storage in the operating system or uninstalling the app ordinarily removes app-managed local records from that device. This is destructive and may remove saved work that cannot be recovered. Device backups, store backups, or later restore behavior are controlled in part by Apple, Google, or the device owner and may preserve or restore some data.
Removing local data does not delete a record already sent to an enabled provider and does not cancel a store subscription.
Possible service-held data
If production services are enabled, separate systems may hold:
- ordinary hosting and security logs;
- an opaque anonymous session or bounded online request record;
- allowlisted PostHog analytics events and opaque SDK identifiers;
- redacted Sentry crash diagnostics and a short support reference;
- anonymous RevenueCat purchase and entitlement records linked to a store transaction; or
- question/evidence request content processed by an enabled off-device AI route.
Whether any category exists for a particular user depends on the submitted build and which features were used. Anonymous data may not be reasonably searchable by name or email. A production deletion process must specify what reference can safely identify a record, how requests are verified without over-collecting identity, which providers receive deletion instructions, and what legal exceptions apply.
Subscriptions and store records
Billing is not confirmed active. If it is activated, Apple or Google maintains the store account and payment records under its own terms. Deleting Fiscal Vitals data or uninstalling the app does not cancel a subscription. Manage or cancel through the store's subscription settings.
Some transaction, tax, fraud-prevention, chargeback, and accounting records may need to be retained by the store, billing provider, or operator where lawfully required. The final policy must identify applicable retention rather than promise deletion of records the operator does not control.
This website collects no email signup data
The current website has no email list, newsletter integration, contact form, or account. It does not ask for or store an email address. There is therefore no website signup record to delete.
The hosting provider may maintain ordinary infrastructure or security logs. Final host behavior and retention must be verified before a production privacy policy takes effect.
No verified remote deletion channel yet
A dedicated Fiscal Vitals privacy mailbox, deletion form, or authenticated deletion endpoint has not been verified. This draft intentionally does not publish a placeholder address or imply that a general form is monitored for Fiscal Vitals requests.
This is a launch blocker for service-held data and privacy-rights requests. Before public release, the owner must establish and test a request route, safe verification steps, provider escalation, response ownership, and user-facing expectations. The final URL must be public, stable, and consistent with the submitted store declarations.
Retention and required disclosures
Local journals and online assistant operations are designed to be bounded and to expire or prune under source-defined rules. Production retention for provider systems, support records, and hosting logs is not yet verified. The final operator must document actual periods or objective criteria, deletion behavior, backup handling, legal exceptions, and provider responsibilities.
Google Play requires every developer to answer Data safety deletion questions. A web account-deletion resource is required when an app allows users to create an account; the currently reviewed architecture does not. Apple likewise requires in-app account deletion when an app supports account creation. Those conclusions must be retested against the exact release build—this page cannot substitute for an accurate store declaration or an in-app control.