Legal

Privacy Policy

Last updated: June 12, 2026

01What pushd is

pushd is a Chrome extension that deploys HTML pages — usually ones you've made with an AI chat — to hosting providers you connect, such as Netlify, Vercel, Cloudflare, GitHub Pages, Tiiny.host, or your own cPanel hosting. pushd is the deploy button, not the host.

02What we collect

Nothing, by default. pushd has no servers and no analytics. We cannot see what you deploy, where you deploy it, or how often.

Everything the extension needs lives in your browser's local extension storage:

  • Hosting provider tokens you connect (e.g. a Netlify or Vercel personal access token)
  • Your deploy history and rollback snapshots
  • Your settings and preferences

Uninstalling the extension deletes all of it. Your deployed sites stay up — they live on the host, not in pushd.

03Where your data goes

When you hit ↑ Push, your page is uploaded over HTTPS directly from your browser to the hosting provider you chose. Each token is sent only to the provider it belongs to — your Netlify token only ever talks to Netlify's API, and so on.

What each provider does with your site after that is governed by their own privacy policy.

04Payments

If you buy pushd Pro, the purchase is handled by Lemon Squeezy, our merchant of record. They process your payment details and email address under their own privacy policy. We receive a license key and the email it was issued to — nothing more — and use it only to validate your license.

05Permissions the extension asks for

Chrome will show you the permissions pushd requests at install. Here's why each exists:

  • Access to AI chat sites — to add the Push button next to pages your AI builds
  • Storage — to keep your tokens, history, and settings on your device
  • Hosting provider domains — to upload your site to the provider you connected

pushd reads the page your AI built only when you push it. It does not read your conversations.

06Changes to this policy

If this policy changes in any meaningful way, we'll update the date at the top of this page and note the change in the extension's release notes.