Get help
How to reach the transglot team and what to include so we can help quickly.
Check the docs first
- Troubleshooting covers the problems people run into most, with the fix for each.
- Frequently asked questions answers questions about plans, data and setup.
- The Trust Center answers security and procurement questions: subprocessors, retention, and the documents a reviewer asks for.
Contact us
When you are signed in, the chat button in the corner of the console opens a conversation with the team. The team sees the account you are signed in with, so name the workspace and project and leave out your email address.
To write by email instead, use the address that fits. There is no ticket form.
| What you need | Write to |
|---|---|
| Support, billing, plans, invoices and product questions | hello@transglot.ai |
| A security vulnerability | security@transglot.ai. See the vulnerability disclosure policy. |
| Access, export or deletion of personal data, or a signed Data Processing Addendum | privacy@transglot.ai. See the DPA. |
When you are not sure which address fits, use hello@transglot.ai and a person moves it to the right place. To see the product run on your own content first, book a walkthrough.
Business and Enterprise plans carry a contractual support response target, set out in the service level agreement.
What to include
A precise report gets a precise answer:
- Where it happened: the workspace and project name, or the address of the page in the console.
- What you did and what you expected, in a sentence each.
- The exact message, copied as text, or a screenshot.
- For the CLI: the command you ran, the CLI version (run the same
npxcommand with--version), the exit code and the output. Remove any token from it first. - For the API: the endpoint, the HTTP status and the response body. Never send a deploy token or CDN key.
- For a translation: the key name, the language, and what is wrong with it.
Send from the email address on your transglot login, so we can find your account.
Product updates
The changelog lists what changed in the product, and the API changelog lists changes to the API.