Security & data handling
Your money data, handled with care
Vloxyde is built around a simple idea: your financial history is yours, it should be verifiable, and it should never be trapped. Here’s what that means in practice.
We never connect to your bank
Vloxyde has no integration with any bank, card network, or account-aggregation provider. We never ask for, receive, or store your online-banking login, and there is no third-party data pipe to your financial institutions. You add data yourself — by hand or by importing a CSV file you control. The tradeoff is honest: a little more manual entry, in exchange for no standing connection to breach.
How you sign in
You authenticate with Google sign-in or an email-and-password account. Sessions are server-side and scoped to you. Vloxyde sends no email of any kind — no marketing, no notifications — so your address is used only to identify your account.
Your data is scoped to you
Every request that touches money is authorized against the specific object it acts on, and identity is taken only from your authenticated session — never from anything a request can claim about itself. When two people share an expense, each sees only their own side of it. There are no organizations, teams, or shared ledgers to leak across.
In transit and at rest
All traffic between your browser and Vloxyde travels over HTTPS (TLS). Your ledger is stored in a managed PostgreSQL database. We publish specific infrastructure and encryption details, attributed to the providers that actually hold any certification, as our production hosting is finalized — and we will not claim a certification that Vloxyde itself does not hold.
History is non-destructive
Vloxyde never silently overwrites a financial record. Mistakes are fixed with a linked reversal or correction that preserves the original, and merges and other consequential actions are written to an audit trail. Your balances are always rebuildable from the underlying entries.