Choose the right request
A descriptive subject helps route your message and keeps the relevant details together.
What to include in a calculator report
A reproducible report lets us compare the expected method with the implemented behavior.
- The exact calculator page URL.
- Every value entered and the selected units, mode, or date options.
- The result shown and the result you expected.
- Your browser and device type if the issue is visual or interactive.
- A screenshot if useful, with personal information removed.
Privacy requests
Describe the information or right your request concerns and, when relevant, write from the same email address used in an earlier conversation. We may request proportionate verification before disclosing or deleting personal information. Calculator values processed locally are not available for us to retrieve.
What support can and cannot cover
We can review site behavior, calculation methods, accessibility issues, correction requests, and policy questions. We cannot act as your bank, lender, employer, school, doctor, lawyer, accountant, or tax adviser.
- We cannot recommend a specific loan, treatment, investment, tax position, or legal action.
- We cannot access accounts because calculators do not require accounts.
- We cannot provide emergency or time-critical support.
- We cannot verify a result without enough information to reproduce it.
Response expectations
Messages are reviewed according to relevance, completeness, and potential user impact. Reproducible calculation errors and broken interactions receive priority. Response times vary, and duplicate, promotional, abusive, or vague messages may not receive an individual reply.
Keep sensitive information out of email
Send only what is needed to explain the issue.
- Do not send passwords, government identification, full bank details, tax documents, or medical records.
- Redact names, addresses, account numbers, and other identifiers from screenshots.
- For a calculation issue, sample values are usually enough to reproduce the behavior.
What happens after a valid correction
We reproduce the issue, compare the implementation with the documented method, update the shared source when a correction is needed, and run automated and browser checks before publication. This keeps the fix consistent across the live page and future builds.