Security

Subify Security: Data, API Keys & Browser Permissions

See how Subify handles local data, Provider keys, browser permissions, and security reports without making unsupported security claims.

Install Subify ↗FAQ
ChromeChromeFirefoxFirefoxChrome & Firefox
01
subify
01Local Storage
SUBIFY

Local Storage

Extension settings and some required data are kept in the browser's local storage.

02
subify
02Provider Keys
SUBIFY

Provider Keys

In the current architecture, Provider keys are stored locally in the user's browser and should be protected like any other API key.

03
subify
03Browser Permissions
SUBIFY

Browser Permissions

Permissions should match the extension's functionality, and permission changes should be understandable to the user.

04
subify
04Vulnerability Reporting
SUBIFY

Vulnerability Reporting

Use a private support channel to report security issues and do not post sensitive information in a public issue.

FAQ

Before You Ask, The Answer Is Here

We collected common questions about security and using Subify in one place.

No. The extension sends translation and audio requests directly to the Provider you chose, without a Subify relay in between.
The API key is stored in the extension's local browser storage and sent only to the Provider you chose.
Each video's translation is cached in your browser, so watching it again does not cost another API call. Subtitle text and tab audio go to the Provider you chose. The translated subtitle lines of each video are also sent to Subify's translation cache on sub-ify.site. Tab audio and API keys are not sent to Subify. The Delete all data button in the advanced options removes local data.
Use the private support channels listed on the contact page.
No. The site loads no third-party analytics script. Page views are counted on Subify's own server without cookies, Do Not Track is respected, and you can opt out with ?sfy_off=1.
No. Third-party services have their own terms and security policies.