Contact Us
Have a question, suggestion, or want to list your software? Messages go to Dimitris Mitsios, who runs the site.
The QHSE Standard is a personal project, not a company. Tekmon pays for sponsored placements here, and Dimitris works at Tekmon (ownership and funding).
For a correction, include the page URL, the disputed statement and a supporting source (corrections policy).
Get in Touch
Request a factual correction
Send the exact qhsetech.com URL, quote the statement that needs attention and link to the best available primary source. For product details, useful evidence includes the vendor's current product documentation, pricing page, release notes or help centre. Explain what changed and, if relevant, the country, product edition or date to which the correction applies.
Correction requests are assessed against the site's corrections policy and research standards. A vendor request does not automatically change an editorial conclusion, comparison position or published recommendation.
Software listings and commercial questions
Software providers can use the listing submission form to share a product for review. Submission does not guarantee inclusion, a particular ranking or a positive assessment. Editorial listings and sponsored placements are separate; paid placements are labelled and do not replace the documented matching rules used elsewhere on the site.
For questions about authorship, research methods or commercial relationships, review who is responsible for the content, the methodology and the commercial disclosure before sending your message.
Before you send
Do not include passwords, access tokens, employee records, incident records, medical information or other confidential or personal data. A public documentation link is usually more useful than an attachment for verifying a product claim. If your question concerns a purchase, contract, implementation or support issue, contact the software provider directly; qhsetech.com is a directory, not a vendor's support channel: it cannot access vendor accounts or provide vendor support.
What the form needs and keeps
The form asks for a name of up to 100 characters, an email address, a subject of up to 200 characters and a message of between 10 and 2,000 characters. All four fields are required, and the form checks them before it sends anything. If a correction needs more room than that, write the essentials in the message and add links to the evidence rather than pasting long extracts.
A submitted message is saved with the site's back-end service so the editor can read it, and your email address is used to reply. The privacy policy sets out how contact details are used and the rights you have to ask for access, correction or deletion of what you have sent. Use this form for such a request as well, and say which of those rights you want to exercise.
Which route fits your message
- A statement about a product looks wrong: use this form and follow the correction steps above. The page address and a primary source let the record be checked quickly.
- You are a vendor with a new or changed product: use the listing form, which collects the product details in a structured way.
- You use the data or the embeds: read the API documentation, its changelog and the widgets page first, then write if a response or a figure differs from what they describe. Include the request identifier returned by the API where you have one.
- You want to know how a ranking or list was produced: the ordering rules are published, and a question that quotes the list and the rule you do not understand is easiest to answer.
No response time is promised. A message that identifies the page and the evidence is easier to act on than a general enquiry.