Privacy Policy for Escape Block Builder

Scope

This Privacy Policy applies to the Escape Block Builder Chrome extension and its Chrome Web Store listing. It does not apply to websites that users choose to visit or automate with their own scripts.

Data We Collect

Velarix Solutions does not collect personal information, authentication information, payment information, browsing history, website content, location data, health information, personal communications, or user activity data through Escape Block Builder.

The extension does not send user-created scripts, block maps, imported files, settings, clipboard output, active tab details, or page content to Velarix Solutions servers.

Local Browser Storage

Escape Block Builder uses Chrome storage on the user's device to save extension data locally, including:

• User-created scripts and visual block maps.
• Extension settings and draft state.
• Enablement and permission review records for scripts the user chooses to run.
• Module review records created by the user inside the extension.

This information remains in the user's browser storage unless the user exports it, deletes it, resets extension data, or removes the extension through Chrome.

Browser Permissions

Escape Block Builder requests only the Chrome permissions needed for its single purpose:

• activeTab: Used when the user chooses to create or run a script for the current tab.
• storage: Used to save scripts, block maps, settings, and enablement records locally.
• userScripts: Used to register user-enabled scripts through Chrome's Manifest V3 userScripts API on sites authorized by the user.
• clipboardWrite: Used only when the user requests copying exported script or block-map data.
• contextMenus: Used to show user-enabled script actions in Chrome context menus.
• notifications: Used to show completion or error notices for user-triggered actions.

Website Content and User Scripts

Scripts created or enabled by the user can interact with pages that match the user's configured site rules. This processing happens locally in Chrome to perform the action chosen by the user. Escape Block Builder does not collect or transmit the content of those pages to Velarix Solutions.

Remote Code

Escape Block Builder does not load or execute remote JavaScript or WebAssembly. Extension code is packaged with the extension submitted to the Chrome Web Store.

Third Parties

Escape Block Builder does not use advertising networks, analytics services, payment processors, external databases, or external account systems. The extension runs inside Chrome and is distributed through the Chrome Web Store, which is operated by Google under Google's own terms and privacy policy.

Data Sharing

Velarix Solutions does not sell, rent, transfer, or disclose Escape Block Builder user data to third parties. Velarix Solutions also does not use user data for purposes unrelated to the extension's single purpose, and does not use user data to determine creditworthiness or for lending purposes.

User Controls

Users can review, edit, export, disable, or delete their scripts and block maps inside Escape Block Builder. Users can also remove the extension in Chrome to stop all extension activity. Chrome controls how extension storage is removed when an extension is uninstalled.

Changes to This Policy

Velarix Solutions may update this Privacy Policy when the extension's behavior or legal requirements change. Updates will be posted on this page with a new last-updated date.

Contact

Questions about this Privacy Policy or Escape Block Builder can be sent to geeterskeeter12@gmail.com.