Ask for help without sharing your finances.
Use the public GitHub issue tracker for reproducible product and engineering problems. Never paste a real bank alert, import address, email address, account suffix, balance, API key, or Firebase token into a public issue.
Product & bugs
Open an issue.
Describe the screen, build flavor, expected behavior, actual behavior, and safe reproduction steps. Replace all financial values and identifiers with fictional examples.
Open GitHub Issues ↗Security & privacy
Keep sensitive reports private.
Do not disclose a suspected vulnerability publicly. Use the repository’s private security-reporting path when enabled, or contact the project owner through an already trusted private channel.
View security policy ↗Use fictional bank names, merchants, amounts, dates, senders, addresses, tokens, and account identifiers. Screenshots often contain more personal information than the visible bug.