Finance apps ask for trust. Few earn it in plain words.
Kasho is built around data minimisation, secure access, clear system boundaries, and transparent practices — described precisely, without vague promises.
Sign-in stays separate from your money records
Identity and financial records do not share the same responsibility boundary.
Sweyam Auth handles sign-in. Kasho checks access before serving account data, while passwords and authentication secrets remain outside your financial records.
- Separate sign-in service
- Access checks on protected requests
- Passwords are not stored with your money data
Protected while it moves
Production browser traffic uses HTTPS.
Encrypted transport protects information between your browser and Kasho. API access is scoped to the signed-in account so financial records are not exposed as a shared public dataset.
- HTTPS for production browser traffic
- Authenticated access to financial APIs
- Ownership checks across your records
We say what we do — and what we do not
We describe controls precisely and avoid claiming certifications Kasho has not earned.
Kasho maintains a documented inventory of identity, contact, and financial data. Free plans may show Google ads using standard ad-request technical data only — never your money records. Security and privacy requirements are reviewed as the service evolves.
- No bank-password scraping
- No advertising use of your financial records
- Published privacy, terms, cookies, and subprocessors pages
