FortBudget

Plain-language policy

Privacy is built into the boundary.

This policy describes how the current FortBudget iPhone build is designed to handle information. FortBudget is under development and is not offered for download on this site.

Effective: July 23, 2026 Applies to FortBudget for iPhone and this website

1. The short version

FortBudget has no bank connection, account registration, advertising, analytics SDK, CloudKit sync, or developer application server for your budgeting data.

You manually add the financial information you want to track. The app is designed to keep that ledger on your iPhone. Data leaves the app only through actions you start—such as exporting a CSV file, saving an encrypted backup, contacting support, or using an Apple-managed StoreKit purchase.

2. Data stored on your device

FortBudget can store account labels, balances, transactions, categories, budget amounts, import history, and app settings needed to provide the budgeting experience. This is data you enter or import.

Local encryption

The local SQLite ledger is encrypted with SQLCipher. A random database key is protected by the iOS Keychain on the device. The app does not upload that database or key to a FortBudget server.

App lock

You can enable the app lock. When enabled, FortBudget can ask iOS to authenticate you with Face ID or the device passcode. FortBudget does not receive or store your Face ID data.

3. Exports, imports, and backups

These features are initiated by you and use the iOS file picker or share interface.

  • CSV files are readable and are not encrypted. Anyone with access to an exported CSV may be able to read its contents.
  • FortBudget backups are encrypted with a passphrase you choose. FortBudget does not know or recover that passphrase. If you lose it, the backup cannot be restored.
  • You choose where files go. A destination available through Apple’s Files or share interface may include a third-party cloud provider you enabled. That provider’s privacy practices then apply to the copy you save.
  • Imported files are selected by you. FortBudget reads a file you choose so it can preview and import supported transaction rows.

Delete All Data inside FortBudget does not delete CSV or backup files you previously saved elsewhere.

4. Apple and StoreKit

If an in-app purchase is offered, Apple processes the payment and maintains the purchase record. FortBudget receives the verified product and entitlement state needed to unlock the corresponding app features; it does not receive your complete payment-card details.

StoreKit communicates with Apple under Apple’s terms and privacy policy. Apple may keep purchase history independently of the budgeting data stored in FortBudget.

5. This website and support

Website

This is a static informational website. It contains no account signup, advertising, analytics script, tracking pixel, or contact form. Like most hosting providers, Cloudflare may process limited request information—such as IP address, time, requested page, and browser details—to deliver and protect the site under Cloudflare’s own privacy terms.

Email support

If you email support@gusdigitalsolutions.com, your email provider and ours process your address, message, and attachments. We use that information to respond, troubleshoot, and keep an appropriate support record. Do not email passwords, backup passphrases, bank credentials, or detailed financial records.

6. Delete your FortBudget data

FortBudget does not create a user account, so there is no server-side account to close. The in-app Delete All Data action clears the local budgeting database and returns the app to onboarding.

  1. Open FortBudget and select Settings.
  2. Open Privacy Center.
  3. Select Delete all FortBudget data.
  4. Type DELETE and confirm the permanent deletion.

This removes local accounts, transactions, categories, budget allocations, import history, and related ledger metadata. It does not delete files you exported, files you saved to another provider, or purchase records controlled by Apple.

See the complete data deletion guide.

7. Your choices

  • Choose what budgeting information to enter or import.
  • Choose whether to enable the app lock.
  • Choose whether, when, and where to export files.
  • Delete the local budgeting database from Privacy Center.
  • Delete exported copies from each location where you saved them.
  • Choose whether to email support.

8. Changes and contact

We may revise this policy as FortBudget changes. The effective date at the top will be updated when the policy changes.

Questions about this policy can be sent to support@gusdigitalsolutions.com.