// legal · njectify
Privacy Policy — Njectify
Effective date: June 18, 2026 · Last updated: August 23, 2026
Summary
Njectify does not collect personal data. Everything is processed locally in your browser, and the extension has no servers receiving or storing your information. Google Drive sync is optional and uses your own account.
1. Who is responsible?
Controller: Diego Dias
Contact: contato@newlevel.com.br
2. What data do we collect?
2.1. Data we DO NOT collect
- ❌ Your IP address
- ❌ Browser or device identifiers
- ❌ Content of scripts or styles you inject
- ❌ Browsing history
- ❌ Clicks, mouse movement, or behavior
2.2. What is stored on your machine
None of this is sent to any server. It lives in your browser's local storage:
- Your projects, folders, CSS and JavaScript files, in
IndexedDB - File version history, in
localStorage, with automatic pruning of the oldest snapshots - Settings, language and theme preferences, and your API keys, in
chrome.storage.local
None of this data leaves your browser, unless you turn on Google Drive sync.
3. Extension permissions
If a permission is in the manifest, it is because a feature depends on it. Nothing is requested "just in case".
| Permission | Why it is requested |
|---|---|
<all_urls> (access to all sites) | The broadest permission, and the scariest one. Njectify needs to run on any address because the whole point is letting you customize whichever site you want, with no pre-approved list. In practice, it only acts on a page when there is a rule you created for that URL. With no rule, it stays inert. |
scripting and userScripts | The heart of the tool: they let it inject your scripts and styles into the page. userScripts is what enables isolated mode, where your code runs in a context separate from the page's. |
activeTab and tabs | Knowing which tab you are on, applying changes to the right page, and refreshing tabs when you turn a rule on or off. |
storage | Keeping your settings, API keys, and preferences in the browser itself. Projects and files live in IndexedDB, and none of it leaves your machine through here. |
identity | Only for the optional Google Drive sync. The scope requested is drive.appdata, a private app folder: Njectify never sees or touches the rest of your Drive files. If you do not enable sync, it does nothing. |
alarms | A daily internal cleanup: it deletes old deletion records used by sync, so they do not pile up forever for people who never enable Drive. |
4. API keys and secrets
The keys you store in your projects live in the extension's local storage. They are never written into the injected code and never travel through the page's window.
- In isolated mode, your script requests the secret over the extension's own channel and receives the value without the page having access to it.
- In fallback mode, where the script shares the page's context, that request is deliberately refused and returns empty. Better for the feature not to work there than to expose your key to the site.
6. Data retention
- Local data: kept until you delete it in the extension, clear your browser data, or uninstall
- Google Drive: kept in your own account, under Google's policy, until you remove it
7. Your rights (LGPD)
In accordance with the General Data Protection Law (Lei nº 13.709/2018), you have the right to:
- Access your data (it's all in your browser — export via backup)
- Rectify incorrect data (edit directly in the extension)
- Delete data (uninstall the extension or clear local data)
- Data portability (export in
.njectifyformat) - Withdraw consent for synchronizations (anytime via SettingsModal)
To exercise these rights, contact: contato@newlevel.com.br
8. Security
- Local data lives in your browser's storage, isolated by origin like any web application
- Any external communication, when it happens, goes over HTTPS
- Njectify does not encrypt data before sending it to Google Drive: the protection is that of your own Google account
- The extension went through the Chrome Web Store review process, where every permission had to be justified
9. Changes to this policy
This policy may be updated as the extension evolves. When that happens, the last-updated date at the top and bottom of this page changes with it.
10. Contact
Privacy questions?
Version: 1.1 · Last updated: August 23, 2026