Tell us what happened, not just that something failed.

The fastest way to improve a tool or article is a reproducible report. You do not need to send the source file unless it is genuinely necessary, and you should never email passwords, account numbers, private messages, confidential business records, or other sensitive material.

For a broken tool

Include the page URL, browser, device type, what you expected, what actually happened, and any visible error message. If the problem depends on a file, describe its format, approximate size, dimensions/page count, and whether the same file opens normally elsewhere. A small non-sensitive sample is more useful than a private original.

For an outdated marketplace or trade requirement

Send the OpenFileTools page and the first-party source that contradicts it. Requirements can change without notice, so a current official marketplace, government, standards-body, carrier, or platform link is the most useful evidence. We prefer correcting the shared source data rather than patching one paragraph.

For an article correction

Point to the exact sentence or section and explain what is unclear, incomplete, or wrong. If the issue is factual, include the source you are relying on. If the issue is usability, explain what question you still had after reading the article.

For privacy questions

Tell us which feature you used. Most file-processing workflows run locally in the browser, while a small number of features use clearly identified server or external-reference requests. The Privacy Policy explains those boundaries in detail.

What we do not offer by email

OpenFileTools cannot make customs rulings, guarantee marketplace acceptance, provide individualized legal or tax advice, recover passwords, or verify a third party's identity from an email request. Trade Studio can organize evidence and calculations, but final regulatory and commercial decisions remain with the relevant professionals and official systems.