How Vardon handles privacy and security

Vardon is a desktop app. Some financial records, settings, imports, exports, cached views, and workspace data may be stored on your device or in app-controlled local storage. Local storage can make the workspace faster and more useful, but local data can still be sensitive.

You are responsible for keeping your device, operating system account, backups, and exported files secure. That includes installing operating system updates, controlling device access, and treating exported finance files with the same care as statements or spreadsheets.

The Privacy Policy identifies account data, billing data, open banking data, support data, technical data, and limited analytics data. Account data can include email address, account status, verification state, subscription state, security metadata, and support identifiers. Billing data can include payment status, plan, invoice, renewal, cancellation, and provider references, while card details are handled by the payment provider.

Support data can include messages, screenshots or files you choose to send, issue descriptions, app version, device context, and diagnostics. Technical data can include IP address, request metadata, device and operating system information, app version, crash or error information, security logs, and update checks.

Open banking data is only accessed where you choose to connect a bank account. Connection status, selected accounts, sync windows, fetched transactions, balances, merchant details, and banking metadata may be involved, depending on the permissions, provider, and bank connection you approve.

The policy says limited product usage telemetry tracks product usage rather than your financial life. It says Vardon does not send transaction amounts, balances, merchant names, bank account names, budget names, report contents, or report scores as analytics. Website telemetry uses browser session storage for an anonymous session identifier for the current browser tab.

The Privacy Policy says Vardon uses technical and organisational measures designed to protect personal data, including access controls, validation, provider controls, restricted diagnostics, and security monitoring. Necessary cookies or local storage may be used for security, authentication, session continuity, preferences, diagnostics, or service operation.

No system is perfectly secure. You should protect your email account, install app updates, keep backups safe, and contact support promptly if you suspect unauthorised access. Vardon can reduce risk, but it cannot make an insecure device or exposed export file safe by itself.

Next, use the related links on this page to move from overview to implementation: read the security overview, read the full privacy policy, understand bank connections. Start with the page that matches your current job, then return to Features if you need wider product context. When comparing Vardon, remember that the marketing site is mobile-readable but the product remains a desktop app. Review pricing and the privacy policy before downloading, especially if you plan to import CSV files, connect a bank account, or keep long-term financial history in the workspace. Vardon is best evaluated as a system of records: each workflow becomes more valuable when transactions, budgets, funds, loans, and reports are kept current. If you only need a quick mobile balance glance, it may be more product than you need.