Privacy Policy

Last updated: May 2026

1. Introduction

This Privacy Policy describes how the HTML Deployer Chrome extension ("we", "our", or "the Extension") collects, uses, and protects your information when you use our service. HTML Deployer helps you export or deploy HTML from web pages (for example as ZIP download or to cloud hosts such as Netlify, Vercel, or GitHub Pages).

2. Information We Collect

The Extension and our backend may process the following information:

Email address: If you sign in with Google, we access your Google account email for authentication and account association. It may be stored on our servers together with your extension instance identifier.
Extension / device identifier: A stable identifier derived from the extension context is used to register your account, enforce free-tier limits, and associate deploy history with your usage.
License key: If you enter a license key, it is stored locally in the extension and sent to our servers to validate your plan and quotas.
HTML and page content: When you deploy or download, the HTML you choose (or that the Extension reads from the active page) is processed in your browser and may be sent to our API server to perform the deploy action you requested (for example uploading to a host you configured). We use this data only to complete that operation and related logging.
Host credentials (local only): API tokens or settings for Netlify, Vercel, GitHub, FTP, or similar targets that you provide are stored in Chrome local storage on your device. They are sent to third-party APIs or our relay only when you initiate a deploy or connection test—not stored on our servers as a permanent "password vault" unless required for a specific feature you enable.
Deploy metadata: Our servers may log deploy outcomes (target, filename, URL, timestamps, approximate size, and error messages) for quota enforcement, support, and abuse prevention.

3. How We Use Your Information

We use the information solely for:

Authenticating you when you use Google sign-in
Registering your extension instance and managing free or paid quotas
Validating license keys and plan entitlements
Relaying deploy requests to the hosting or export targets you selected
Providing support, security monitoring, and improving reliability of the service
Service-related email: We may use your email for license delivery, receipts, security notices, or responses to support requests. We do not send unrelated bulk marketing without a separate opt-in where required by law.

        Email privacy commitment:
        We use your email for account and service-related purposes as described above
We do not sell your email address
We do not share it with third parties for their independent marketing
You may contact us to ask about data we hold or to request deletion where applicable

    

4. Data Storage and Processing

Important:

Local storage: Preferences, tokens you paste, and similar settings are kept in Chrome's storage on your device.
Our API server: May store account records, license state, and deploy logs in a database (for example SQLite on the server) to operate quotas and support. HTML payloads are processed for the deploy transaction and are not intended for long-term retention as a document archive.
Third-party hosts: When you deploy to Netlify, Vercel, GitHub, FTP, or other services, those providers process data under their own terms and privacy policies.

Deploy relay:

Deploy actions you trigger may send HTML and configuration from the Extension through our server to the target you chose
Use the Extension only with content and accounts you are allowed to publish
Revoke tokens at the provider if you stop using a given integration

5. Third-Party Services

The Extension may interact with:

Google (OAuth): For sign-in. Your use of Google services is subject to Google's Privacy Policy.
Netlify, Vercel, GitHub: When you connect tokens, API calls go to those providers under their policies.
Our backend (Backrun / publisher API): For registration, license checks, deploy relay, and history as implemented in your deployment.

6. Permissions

The Extension may request permissions such as (see your manifest for the exact list):

Identity / Google sign-in: To authenticate and obtain your email when you choose Google login
Storage: To save settings and tokens locally
Tabs / scripting: To read HTML from pages you use with the Extension
Host access: To call our API and third-party deploy APIs you configure
Downloads: If ZIP or file download is offered

7. Data Security

We implement reasonable technical and organizational measures to protect information handled by our service. No method of transmission over the Internet is 100% secure; use strong, unique tokens and revoke access when no longer needed.

8. Your Rights

Depending on your region, you may have the right to:

Access or correct certain account information we hold
Request deletion of personal data where applicable and not required for legal or operational retention
Disconnect Google sign-in or uninstall the Extension (local data may be removed with uninstall, subject to browser behavior)
Revoke API tokens at Netlify, Vercel, GitHub, or other providers directly in their dashboards

9. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will post changes on this page and update the "Last updated" date.

10. Contact Us & Support

If you have questions about this Privacy Policy or need support:

Email: hi@backrun.co
Website: Backrun
Contact form: Contact Support
Help: Documentation

11. Consent

By using the HTML Deployer Chrome extension, you consent to this Privacy Policy and agree to its terms.