This CLI processes personal financial data and authenticates against an unofficial Spendee integration.

The CLI keeps fetched data in memory and does not create a database, cache, raw response dump, credential file, or token file. Console and JSON output can still contain merchant names, wallet names, transaction IDs, and categories; protect logs produced by VPS jobs.

Provide credentials through SPENDEE_EMAIL and either SPENDEE_PASSWORD or SPENDEE_PASSWORD_FILE. Do not put credentials in YAML or command-line arguments.

• Commands are read-only unless --commit is supplied.
• Correct existing categories are not rewritten.
• Category writes carry the Firestore update time read during the run, preventing stale data from being silently overwritten.
• Transfer pairs are written atomically.
• Ambiguous transfer pairs are never committed automatically.

Always inspect a dry-run before the first committed run or after upgrading.

Do not open a public issue containing credentials, tokens, wallet IDs, transaction IDs, or financial data. Use GitHub's private vulnerability reporting feature when available.

If a credential or token is exposed, revoke or rotate it immediately.