Back to sign in

KiraSaku

Beta Preview

Privacy Policy

How the current beta handles account data, financial records, and sign-in information.

Beta preview

This policy covers the current beta preview.

It reflects the product as it exists today and will be tightened further before broader public launch, billing, and full support operations.

What we collect

KiraSaku stores the information you add to manage your finances, including loans, bills, receivables, income sources, properties, payment history, and account email details.

When Google sign-in is enabled in production, KiraSaku also receives basic identity information from Google, such as your name, email address, and provider user ID.

Why we collect it

We use this data to show what is due this month, track payments, calculate balances, and keep your account accessible across sign-in sessions.

We do not use your financial records for advertising or third-party behavioral tracking.

How it is stored

Production data is stored on KiraSaku-controlled infrastructure, including persistent application storage for the database and uploaded files. Local development data stays on the developer's own machine.

Session cookies are used to keep you signed in. KiraSaku does not currently use third-party analytics or ad trackers.

Passwords and sign-in

Local development may still use email and password for testing. Production is intended to use Google OAuth so KiraSaku does not need to store new production passwords.

If legacy password-based accounts exist, password hashes are stored using Rails secure password hashing and are not stored in plain text.

Retention and deletion

Your data is kept for as long as your account remains active or until deletion is requested. Backup retention may temporarily preserve deleted data for operational recovery windows.

You may request account and data deletion. Deletion tooling and support procedures are being finalized before public launch.

Contact

Questions about privacy, data handling, or account deletion can be directed to KiraSaku support through the official support channel used for your deployment.

Effective date: 2026-03-04. This policy will be updated as KiraSaku moves from internal use to public launch and adds production OAuth and billing.

Questions before trying the beta? Return to sign in or review the Terms of Service.