Contact

FinCalc is a small project maintained in spare time, so response times are best-effort rather than guaranteed. The fastest way to get a useful answer is to open a public issue; the slowest is a generic email with no context.

Issues and feature requests

The clearest path for any bug report, feature request, or usage question is to open an issue on the GitHub repository:

• Repository: github.com/zx9597446/fincalc
• New issue: github.com/zx9597446/fincalc/issues/new

Before opening an issue, please check the existing issues list — your bug may already be tracked. If you do open a new one, include:

• What you typed into each input.
• What you expected to happen.
• What actually happened (a screenshot is helpful).
• Your browser and operating system (e.g. Chrome 120 on Windows 11).

Security disclosures

Please report security issues by email rather than filing a public issue. Send details, proof-of-concept code, and a way to reproduce to the address listed in the repository's SECURITY.md file (or, if no such file exists, open a public issue and request a private channel).

Other contact

For everything else — general feedback, suggestions, partnerships — GitHub issues are still the best option. There is no support inbox, no live chat, and no DM channel. This keeps the maintenance burden low and ensures every conversation is searchable for the next person with the same question.

Response time

Issues are typically triaged within a few days. A fix or follow-up question follows in one to three weeks depending on complexity. Critical bugs (calculator returns wrong number) are prioritised over feature requests and cosmetic tweaks.

Frequently asked questions

How do I report a bug or request a feature?

Open an issue on the GitHub repository at github.com/zx9597446/fincalc/issues/new. Check the existing issues list first — your bug may already be tracked. Include what you typed into each input, what you expected to happen, what actually happened, and your browser and operating system.

How do I report a security issue?

By email rather than a public issue. Send details, proof-of-concept code, and a way to reproduce to the address listed in the repository's SECURITY.md file.

Is there an email address or live chat?

No. There is no support inbox, no live chat, and no DM channel. GitHub issues are the channel for everything — feedback, suggestions, and partnerships included — so every conversation stays searchable for the next person with the same question.

How fast do you respond?

Issues are typically triaged within a few days, with a fix or follow-up question in one to three weeks depending on complexity. Critical bugs (a calculator returning a wrong number) are prioritized over feature requests and cosmetic tweaks.