Bug reports
Share the page, the steps that caused the problem, and what you expected to happen instead.
Contact
WorthItCheck does not run customer accounts or a staffed support desk. For now, the best public contact route is the project issue tracker.
WorthItCheck
The strongest contact messages are practical: something broken, something unclear, or a decision edge case worth improving.
Share the page, the steps that caused the problem, and what you expected to happen instead.
If a tool needs another input, a clearer explanation, or a stronger comparison mode, say what decision it would help with.
Do not post private account details, passwords, or confidential documents. WorthItCheck is not set up for private case handling.
Current public route
Use the public project issue tracker for bugs, broken links, and product suggestions.
Visit the public issue tracker to report bugs or suggest improvements.
Include the page URL, what you entered, what happened, and what you expected instead.
Because the route is public, do not include personal data or anything confidential.
Best use of contact
WorthItCheck is strongest when feedback stays tied to product quality and decision clarity.
Missing assets, layout issues, share-link failures, or outdated text are all good things to report.
If a verdict missed an important real-world factor, explain the factor and which tool it affects.
Requests like advanced rent-vs-buy inputs, broader repair categories, or stronger UK assumptions are ideal product feedback.
Not a personal support desk
WorthItCheck is a public tool site, not a case-by-case advisory service.
There is no login-based account support workflow.
Do not send contracts, mortgage documents, or personal files expecting a private review.
Public feedback is best when it helps improve the product for many users at once.
FAQ
The current public route is the project issue tracker: https://github.com/SamJest/worthitcheck/issues.
No. Do not send private financial, personal, or confidential information through a public issue tracker.
Reproducible bugs, unclear result wording, broken links, and feature suggestions tied to a real decision problem are the most useful.