Kleos

Privacy Policy

Effective 12 September 2026

Kleos is a private personal application used by its owner to consolidate personal evidence, including financial account information. It is not offered as a public banking, payment, or financial-advice service.

Financial data access

When the owner chooses to connect a bank account, Kleos uses Enable Banking to facilitate read-only Open Banking access. The owner is redirected through the bank's authorization flow and explicitly approves access. Kleos does not receive or store the owner's bank password or other bank-login credentials, and it does not initiate payments through this integration.

Data Kleos stores

For connected financial accounts, Kleos may store provider connection metadata, normalized account metadata, masked account identifiers, account balances, transaction dates, amounts, currencies, descriptions, counterparties, transaction status, and provider response data needed for synchronization and auditability. Full IBAN or BBAN values are not intentionally persisted; account identifiers are reduced to a masked form for display and storage in the normalized account record.

Purpose

The data is used only to operate the owner's private Kleos workspace: displaying current financial state, maintaining historical evidence, and supporting the owner's personal analysis and Kleos evaluations. It is not sold, used for advertising, or made available to unrelated third parties.

Service providers

Kleos relies on infrastructure providers required to operate the application, including Supabase for authentication, database, and server-side functions; GitHub Pages for the static web interface; and Enable Banking for Open Banking connectivity. Those providers process data according to their own terms and privacy obligations.

Security

Financial synchronization credentials and the Enable Banking application private key are kept on the server side and are not embedded in the browser application. Kleos uses authenticated access controls and row-level security for private financial records.

Retention, revocation, and deletion

Open Banking authorization may be revoked or allowed to expire at any time through the relevant bank or provider flow. Revoking access stops future retrieval but does not automatically erase financial evidence already stored in Kleos. Stored Kleos data can be deleted by the application owner from the underlying private data store when it is no longer required.

Changes

This policy may be updated when Kleos changes how it processes personal data or changes service providers. The effective date above identifies the current version.

Return to Kleos