Security / Built on restraint

Trust is a feature.
Not a footnote.

Financial information deserves deliberate access, transparent controls and careful boundaries. Saldio is designed around those principles.

◇

Read-only banking

Supported bank connections read account and transaction information. Saldio cannot send payments, transfer funds or edit bank records.

◈

Your workspace stays yours

Authenticated account records are designed to remain separated. Sharing a Household plan does not automatically share private personal transactions.

✦

Consent before action

Financial suggestions do not move money. In-app changes require relevant permissions and, for sensitive actions, additional verification.

⌁

PIN and biometrics

Supported signed-in app sessions use a six-digit app PIN, with optional device biometrics where available. These require native-device verification before release.

◎

Clear provider roles

Infrastructure, bank connectivity and subscription processors support different functions. Our privacy policy explains what information may be involved.

✳

Deletion and control

You can request removal of your Saldio account and associated personal information, subject to legal retention and verification requirements.

Important accuracy note. These are the security principles and product architecture, not a claim of third-party certification or a completed independent audit. Live OAuth, Supabase, store and device security flows must be tested before public launch.

Simple boundaries

Your bank stays your bank.

Saldio is a budgeting and financial organization tool. It is not a bank, brokerage or money transmitter. Changes within Saldio do not change external bank balances.

What happens when you connect a bank?

  • You authorize a supported connectivity provider
  • Saldio receives permitted read-only data
  • Original bank records remain separate from local edits
  • You can manage or disconnect supported connections
  • No bank-side payment initiation is offered