Contact Z Tools
Bug reports, feature requests, security disclosures, partnership inquiries, or just a quick question — we read every message and usually reply within 1–2 business days.
Send us a message
The form below opens your default email client with your message pre-filled and addressed to our team inbox. If you prefer, you can also write to us directly at [email protected].
Other ways to reach us
🛡 Security issues
Use the Security disclosure subject. Please do not share the vulnerability publicly until we have had a chance to respond.
We aim to acknowledge within 48 hours.
💬 Press and partnerships
For media inquiries, integrations, or educational partnerships.
Use the Partnership / press subject.
🔍 Privacy requests
Access, correction, or deletion requests for any data you may have submitted. See our Privacy Policy.
We respond within 30 days.
Before you write — quick checklist
A lot of the messages we receive are answered by our existing documentation. Checking these first helps us respond faster to questions that need a human:
- Tool not behaving as expected? Refresh, try a different browser, and check the FAQ for known issues.
- Want to request a new tool? Tell us which file types or workflows it should support — the more specific the better.
- Looking for a code/API integration? All tools are client-side; the libraries are linked from each tool's "About" section.
- Need a quick answer to a privacy question? The Privacy Policy covers what we collect, what we do not, and retention.
- Found a typo or a broken link? Please tell us which page and (if possible) the exact text. We fix those the same day.
How we handle your message
The form opens your email client and routes through your personal account, so messages are not stored on our servers. If you write to us directly at [email protected], the message lands in a shared inbox hosted by a third-party email provider. We retain contact-form messages for up to 24 months to maintain a history of bug reports and feature requests. You can ask us to delete the record of our correspondence at any time by emailing us with the subject line "Privacy / data request" — we will confirm deletion within 30 days.
Response times vary by category. Security disclosures are acknowledged within 48 hours and triaged within 7 days. Bug reports typically get a first response within 1–2 business days, though fixes can take longer. Feature requests are read and considered, but we cannot promise a timeline; the more users that ask for the same feature, the faster it usually moves up our roadmap.
Response times and what to expect
Z Tools is run by one person, so our response times are realistic rather than corporate. We do not use chatbots, ticketing systems, or auto-responders — every reply is written by a human who has actually read your message.
Security disclosures
Acknowledged within 48 hours; triaged within 7 days. Responsible-disclosure practices; we credit reporters in release notes (unless you prefer anonymity).
Bug reports
First response within 1–2 business days. Reproduction steps speed this up dramatically.
Feature requests
Considered seriously; no fixed timeline. The more specific the use case, the higher it usually ranks.
Press and partnerships
Initial reply within 3–5 business days. We do not accept sponsored placements.
Privacy / data requests
Acknowledged within 5 business days; resolved within 30 days per our Privacy Policy.
General questions
Best-effort, usually within 2–3 business days. The FAQ covers most common questions.
How to write a bug report that gets fixed quickly
The bug reports that resolve fastest share five details:
- Tool and URL. Which tool failed and the exact URL where it happened. Include the input you used (redact personal data).
- Browser, OS, and device. Chrome 124 on macOS 14.4 / Safari 17 on iPhone 15 / Firefox 126 on Windows 11.
- Steps to reproduce. Numbered list, ideally 3–7 steps. The shorter, the faster we can fix.
- What you expected vs what happened. One sentence each is enough. Screenshots help for visual issues.
- Console output (if any). Open DevTools (F12), go to the Console tab, and copy red error messages.
Please do not include passwords, API keys, government IDs, credit-card numbers, or other secrets. If your bug requires sensitive data to reproduce, write "contains sensitive data" in the message and we will work out a safe reproduction path by email.
Languages and time zones
We are based in Hangzhou, China (UTC+8) and respond in English or Chinese, whichever you wrote in. If you write in another language, we will translate with help from machine translation and reply in your original language when our confidence is high enough; otherwise we will reply in English and note that translation is welcome. There are no business-hours restrictions — we read and reply across the working day and into the evening.
Holidays: we observe the official Chinese public holidays (Spring Festival, National Day, etc.). During a holiday week, expect response times to extend by 3–7 days. We will note holiday slowdowns on the homepage.