FIRST7 STEWARD

Your Data

How First7 Steward stores, protects, and lets you manage your financial data.

Your Data

Your financial records belong to you

First7 Steward is designed around a simple principle:

Your financial records should remain under your control.

Steward is built as a local-first application.

The current version stores your working financial records locally in your browser rather than requiring a central cloud database for your financial ledger.

This approach is intentional.

Steward is designed to help you keep your records without requiring you to place your financial history inside a centralized financial platform.


Where your data is stored

The current version of Steward stores its working data in your web browser using IndexedDB.

IndexedDB is a storage system provided by modern web browsers for storing structured application data locally.

Your Steward installation can contain records such as:

  • Transactions
  • Funds
  • Categories
  • Accounts
  • Transfers
  • Settings
  • Steward metadata

These records belong to the local Steward installation in the browser and site where you use the application.


Local-first means local financial records

The basic model is:

You → Steward → Your browser

rather than:

You → Steward → Central financial database

The Steward application is delivered through the web, but your financial ledger does not require a central cloud database to perform its core record-keeping functions.

This distinction is important.

Being a web application does not mean that your financial records must be stored on a remote financial server.


First7 does not require your financial ledger

The current version of Steward does not require:

  • A First7 user account
  • A financial account with First7
  • A cloud financial database
  • A bank connection
  • Automatic bank imports
  • Payment processing
  • Real-world money transfers

Steward is a record-keeping application.

It does not hold your money.

It does not move your money.

It does not act as a bank.


What Steward records

Steward records financial information that you enter into the application.

This can include:

  • Accounts
  • Money In
  • Contributions
  • Money Out
  • Transfers
  • Transaction dates
  • Categories
  • Notes
  • Settings
  • Other information required by the Steward application

The ledger is the source of truth for the financial history recorded in Steward.

Balances and summaries are calculated from that recorded history.


Transfers are records, not bank movements

When you create a transfer in Steward, you are recording that money moved from one Steward account to another.

For example:

Bank → Cash

A ₹5,000 transfer records:

  • ₹5,000 leaving the Bank account
  • ₹5,000 entering the Cash account

Steward does not actually move ₹5,000 between your real-world accounts.

The transfer exists inside your Steward financial record.

Transfers are therefore kept separate from income and expenses so that moving money between your own accounts does not create artificial income or spending.


Your browser is part of your data environment

Because Steward is local-first, the browser and device you use become part of the environment where your working records are stored.

This has an important consequence:

Your local Steward data is not automatically available everywhere.

For example, using Steward on another computer or another browser does not automatically give that installation access to the records stored in your original browser.

That is intentional in the current version.

Use Steward’s backup and restore system when you need to move your records.


Automatic local protection and backups

Steward now keeps an automatic local snapshot of your records as you make changes. This protection stays on your device and is not uploaded to a Steward server.

Automatic local protection is designed to help with ordinary application or local-data problems, but it is not a replacement for a portable backup.

If your browser’s site data is cleared, your device is lost, or you move to another device, the local snapshot may not be available.

For important financial records:

Do not rely on local browser storage as your only copy.

Use Steward’s Export Backup function regularly and keep the .steward file somewhere safe. Steward also shows a gentle reminder when you have not downloaded a backup recently.

For particularly important records, consider keeping more than one backup copy.


Steward backup files

Steward provides its own backup format using the .steward file extension.

A Steward backup is intended to contain the stored data needed to restore your local Steward dataset.

Backups can help you:

  • Preserve your financial records
  • Recover from loss of local browser data
  • Move to another computer
  • Keep an additional copy of your records
  • Prepare for future migration

Your backup file is an important part of your data ownership.


Restoring your data

Steward follows the principle:

Validate first. Restore second.

When you import a backup, Steward validates the backup before changing the current local dataset.

An invalid, malformed, or otherwise unacceptable backup is rejected rather than partially imported.

When a valid backup is restored, it replaces the current local Steward dataset.

Because of this, create a backup of your current data before restoring another backup.


Moving to another computer

To move your Steward records:

  1. Open Steward on your original computer.
  2. Export a Steward backup.
  3. Keep the backup file somewhere safe.
  4. Open Steward on the new computer.
  5. Choose Import Backup.
  6. Select your .steward file.
  7. Review the restore information.
  8. Confirm the restore.
  9. Check that your records are present and correct.

Keep the original backup until you have confirmed that the new installation has been restored successfully.


Protecting financial history

Steward is designed to preserve financial history rather than make it easy to erase.

For example, transactions can be voided when they should no longer be treated as active records.

An account that has never been used can be deleted.

An account that has financial history is treated differently because deleting it could remove part of the story of your financial records.

Where appropriate, used accounts can be archived rather than deleted.

This approach is intended to make financial history easier to understand and harder to erase accidentally.


Data ownership and portability

Steward is designed around data ownership and portability.

Your financial records should not become trapped inside a service simply because you used that service to record them.

The .steward backup format gives you a portable copy of your Steward data that can be restored when needed.

Backup and restore are therefore not secondary features.

They are part of Steward’s approach to data ownership.


What Steward does not currently do

The current version of Steward does not:

  • Connect directly to your bank
  • Automatically import bank transactions
  • Process payments
  • Move real-world money
  • Hold money
  • Maintain a central cloud financial ledger
  • Automatically synchronize your records between devices
  • Provide financial advice
  • Provide tax advice
  • Provide investment advice
  • Provide legal advice

Steward is focused on simple financial record-keeping and stewardship.


Privacy

Steward is designed with privacy as a foundational principle.

The current application does not require you to create an account before recording transactions.

Your financial records are not intended to become a public profile or public financial history.

The core financial ledger is designed to remain local to your Steward installation rather than being stored in a central financial database.

Anonymous usage measurement

If analytics is enabled for the deployed site, Cloudflare Web Analytics measures website visits. Steward may also send a small set of anonymous event names to count app opens, standalone app launches, and browser-reported installation completions. These are aggregate event counts, not a count of unique people or guaranteed unique installations.

The custom tracker does not read or send transactions, balances, accounts, categories, notes, backups, or other financial records. It does not create a Steward user account or use a stable device identifier. Events are best-effort: when the device is offline or tracking is unavailable, the event may not be counted. Analytics never needs to succeed for Steward to open or work.

Cloudflare processes request metadata to provide its services. Review Cloudflare’s applicable privacy and logging settings for the deployed configuration.


A note about browser storage

Browser storage is convenient, but it is not the same thing as a traditional file stored in your Documents folder.

Your local Steward data can be affected by browser actions such as clearing site data.

Browser storage can also be affected by events outside the Steward application itself.

For this reason, Steward’s backup system is an important part of using the application responsibly.

If your financial records matter, keep a backup.


Current version

This page describes the data behavior of the current Steward release.

Steward is under active development, and some technical details may change as the application’s architecture develops.

When the data architecture changes in a meaningful way, this page will be updated.

Last updated: 2026-10-21