Privacy Policy

1. Scope

This policy applies to Vercel Env Exporter, a Chrome extension developed by UBEE Digital Technology Co., Ltd. The extension exports environment variables from the Vercel project page currently opened by the user into a local .env file when the user clicks the extension.

2. Data the extension handles

During a user-requested export on a supported Vercel Environment Variables page, the extension handles:

• Website content from that page, including environment-variable names, values, deployment targets, and comments.
• Authentication information that may be stored inside environment-variable values, such as API keys, access tokens, or passwords.
• The current Vercel project URL, used only to identify the selected project and confirm that the extension is running on a supported page.

3. How data is used

The extension uses this data only to create the .env file requested by the user. It may make same-origin HTTPS requests to Vercel using the user's existing Vercel session to retrieve environment variables for the project currently open in the browser. If that method is unavailable, it may read values shown on the current page. The extension operates only after the user clicks its toolbar icon.

4. Data sharing and storage

UBEE does not receive or collect the user's environment variables or browsing data on a developer-controlled server, and does not sell or share that data. The generated file is saved locally through Chrome's download functionality. The extension does not retain a separate copy after the export finishes.

Vercel may process requests made to its own service under Vercel's terms and privacy policy. The extension does not send user data to advertising, analytics, or other third-party services.

5. Limited Use

Use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. User data is used only to provide the extension's single user-facing export feature and is not used for advertising, creditworthiness, lending, or any unrelated purpose.

6. Permissions

The extension uses these permissions:

• Scripting: runs the packaged export script on the active Vercel project page after the user clicks the extension.
• Downloads: saves the generated .env file to the user's computer.
• Active tab: provides temporary access to the current tab after a user action.
• Vercel site access: limits site access to https://vercel.com/* for the export workflow.

7. Security notice

Exported .env files can contain secrets in plaintext. Users should store exported files securely and must not commit them to source control or share them publicly.

8. Changes to this policy

This policy may be updated when the extension's functionality or data-handling practices change. The latest version and its effective date will be published at this page.

9. Contact