This is information for developers so that they can restrict Nuenki on their website.

Nuenki activates on all sites by default. It will disable on:
- Sentences, should a keyword be in a block list. This uses bloom filters; false positives may occur.
- Websites, should a term be in the domain or path be in the blocklist. I can provide this list upon request.
- Websites, should an aspect of the domain be in the blocklist. This uses bloom filters; false positives my occur. The domain is progressively stripped of subdomains, with each one checked against the filter, e.g. hello.thing.flagged.site will have
hello.thing.flagged.site checked (negative)
thing.flagged.site checked (negative)
flagged.site checked (positive; extension disabled)

this check is done on initial page load and when the href changes

If you want to disable nuenki on your website, or on part of your website, there are two ways.

The first is with the data-nuenkiignore='true' attribute. Place this on an element and it will not be translated.

You can see this in use in the demo on the landing page in order to prevent Nuenki from translating the demo twice.

Alternatively, if this isn't possible with your setup, you can contact me via developers@nuenki.app and I'll add your site to the exemptions list.

If you believe a site should be on the blocklist, please contact me even if it isn't your website. The goal is to prevent anything the average user wouldn't want shared from being shared, erring on the side of caution.