Contact Us

1. How to reach us

Email is currently the only channel we operate: connorlin072@gmail.com

This site is run by one individual. There is no support team, no live chat widget, no phone number and no office address. Please write to the address above. To help us deal with your message efficiently, put a short subject line on it — for example "reading correction", "feature request" or "privacy request" — so that we can tell at a glance what it concerns.

One thing worth knowing up front: because all text processing happens locally in your browser, we cannot see or retrieve anything you have worked on in the page. If you describe a problem in an email, please include the relevant text yourself, otherwise we have no way to reproduce it.

2. What people usually write to us about

These are the most common reasons people get in touch, and how we normally handle them:

1. Reading corrections and content errata. If a character or word is annotated with the wrong pinyin, or if a rule, example or wording in the Tutorials hub is incorrect, tell us. After verifying it we will correct it in a later update; where the difference reflects established usage or a variant textbook standard, we will add a note to the page instead.
2. Feature requests. This covers new export formats, interface changes, better polyphonic character handling and similar suggestions. We assess how feasible and how necessary each one is, and accepted ideas appear in later releases. Please understand that this is a one-person project and not every suggestion can be built.
3. Usage problems. Exported files that will not open, pinyin that gets cut off when printing, unusual behaviour with traditional characters, and so on. These usually come down to the browser version, the fonts available or the print settings, so please tell us your operating system and browser, and walk us through the exact steps. Many common questions are already answered in How to use and the Tutorials.
4. Licensing and permissions. If you would like to republish or quote our content, or use the site in a school, institution or publishing context, write to us first with the intended use and scope, and wait for confirmation. The tool is free to use, but the site's code and page content have their own ownership, as set out in the intellectual property section of the Terms of Service.
5. Privacy requests. If you want to know how we handle data, or to exercise rights such as access, rectification, erasure or withdrawal of consent, contact us. Since no text is retained on any server, such requests normally concern only cookie and advertising data; the Privacy Policy explains this in detail, and you can change your cookie choice at any time using "Cookie settings" in the footer.

3. What to include in a report

Pinyin problems depend heavily on context: the same character can be read in completely different ways depending on the word it appears in, and it is hard to judge a reading in isolation. To let us find the issue quickly, please include as much of the following as you can:

• The page URL — the address where the problem occurred, whether that is the tool itself or a page in the Tutorials hub;
• The exact text — the full sentence or passage you entered or pasted, ideally with the surrounding context;
• What you got — the reading the tool currently shows;
• What you expected — the reading you believe is correct, and your source for it, such as a dictionary, textbook edition or dictionary entry;
• Your environment — operating system and browser version, plus anything about your export or print settings if the problem relates to those.

A screenshot is also very welcome and is often clearer than a written description. The more complete the information, the faster we can verify the issue and fix it.

4. How long a reply takes

This site is maintained in someone's spare time, so we cannot guarantee a quick reply. As a rule, we look at incoming mail within a few working days. Requests that involve checking readings and adjusting the dictionaries can take longer, because each one has to be verified before anything is changed.

We do not reply to every message either. Repeated questions, mail unrelated to the site, and messages that are mainly promotional may not receive an individual answer. Reports that identify a genuine error and include the details above will normally get a definite response, and we will let you know once the fix is live. Thank you for your patience.

5. Check these pages first

Many questions are already answered somewhere on the site, so it is worth looking here before you write:

• How to use — step-by-step instructions for each feature, plus common questions;
• Tutorials — tool workflows, pinyin fundamentals, polyphonic characters, how-to guides and classroom material, all in one place;
• Picture Book Studio — write a story, annotate it with pinyin, add your own illustrations and export a print-ready multi-page PDF;
• Privacy Policy — how your text is handled, and how cookies and third-party advertising work;
• Terms of Service — the licence to use the site, content responsibility and intellectual property.

If none of that covers your question, feel free to email us at any time.