Getting help, and what to include

Before you write

Refresh the page. When the extension updates, the script in every already-open tab is orphaned — saving fails, panels come up empty, and the popup says it cannot reach the tab, all while the extension looks fine. It is by a wide margin the most common cause of a support email.

After that, troubleshooting lists the exact messages the product can print and what each one means.

What to include

• Your Chrome version, from chrome://version.
• The language pair you are learning and translating into.
• The site, and whether the video had captions switched on.
• The exact message you saw, copied rather than described.
• What you expected to happen instead.

Billing and licences

Include your transaction id and the email address you paid with. The transaction id is also your licence key, so if you have mislaid it, the receipt from Paddle is where to look. See activating a licence.

Response times, honestly

A few working days. This is a single-person project rather than a support desk, and pretending otherwise would only make the wait feel worse. Reproducible bug reports get looked at first, because those are the ones that help everybody.

Security reports

Same address, but see the security page first for what to expect. Please do not post a vulnerability publicly before we have had a chance to respond.

Corrections to this site

If a fact here is wrong — about NoaLingua or about a competitor — we would rather hear it. Everything on this site carries a source and a date, and a correction updates both.