Contact, Legal Notice, and Support Routing: Which Official Entry to Use
Technical, legal, privacy, and feedback questions should use different on-site paths.
1 Route the question before sending it
Translation Input Method has contact, legal, privacy, FAQ, and guide pages. Each one serves a different job, so not every question needs to start with email.
For install failures, input switching, missing candidates, or unclear download sources, the FAQ and guide pages are usually faster. Email is more useful when the on-site guides do not cover your case or when you can provide a clear reproduction.
For copyright, trademark, legal notice, or rights questions, use the legal entry instead of the technical support path. The legal page already lists the relevant email entry.
2 What to include before contacting
If you do send an email, be specific: system platform, current version, where the issue appears, whether it happens only in one app or text field, and which on-site guide you already checked.
Avoid sending sensitive input content. If a short neutral sentence can reproduce the issue, use that. For managed devices, mention whether administrator policy may be involved.
3 Why this belongs in news
As the site grows, routing matters. Explaining where to go is more useful than repeating another install tutorial.
Search users also look for official contact, legal notice, and feedback paths. A form alone is not always enough; users need to know which page fits the question.
Continue Checking
FAQ
Should every technical issue be sent by email first?
Not always. For install, switching, candidate display, and download-source questions, check the FAQ and matching guide first. Use contact when the site does not already cover the issue.
Where should legal or copyright questions go?
Use the legal notice page. Legal, copyright, and trademark questions should follow the legal contact information shown there.
Is the contact page a ticket system?
The contact form opens the local email client. This article does not assume a phone line, ticket portal, or hidden support backend.
Verify the current version before installing
If you are ready to install or update, return to the download page and verify the current public version, platform notes, and on-site release information.