Privacy Policy

Last updated: August 19, 2026

This policy explains how DivMagic collects, uses, handles, stores, and shares user data for the browser extension and the website (divmagic.com, including Studio, dashboard, and API). Those products share an account, but they do not collect the same data.

Contact: team@divmagic.com

Browser extension

The Chrome / Firefox extension copies page elements into HTML, CSS, React/JSX, or Tailwind on your device. Most copy output stays on your device unless you sign in, save, or export.

Collection

  • Email and one-time login code, to sign you in
  • User ID and subscription status, to check that your plan is active
  • Settings you choose (copy format, style format, DevTools panel, language), stored in the browser
  • Copied component code and an optional thumbnail, only if you save to your library or export to Studio / WordPress
  • Product metrics (feature used, user ID, browser type; email on login)

The extension does not collect your Google account name or photo. It does not collect payment card numbers.

Use, handling, and storage

  • Use: authenticate you, provide copy/save/export, remember settings, improve the product
  • Handling: copy generation runs locally; login, subscription, save/export, and metrics go to our APIs over HTTPS
  • Storage: settings on your device; account, saved components, and metrics on AWS

Sharing

Vendors below process data for us to run the product. We do not sell it or give it to other apps. All of this goes over HTTPS.

  • Amazon Web Services — hosting and storage
  • SendGrid — login emails

Website

divmagic.com is the account, billing, Studio, docs, and marketing site. Data below is collected on the website, not by the extension unless noted.

Collection

  • Email, password, and account ID
  • Name and profile photo — only if you sign in with Google on the website
  • Onboarding answers (role, use case, output format)
  • Studio projects and saved library components you create on the site
  • API keys you create in the dashboard
  • Cookies and similar tech for login, preferences, and analytics
  • If you paste your own OpenAI API key into Studio chat, that key stays in your browser and is sent to OpenAI for that chat

Use, handling, and storage

  • Use: accounts, Studio, billing, support, analytics, and marketing measurement
  • Handling: processed on our servers over HTTPS; Google sign-in is handled by Google
  • Storage: AWS (accounts and content); Stripe (payments); analytics providers below

Payments go through Stripe. We receive plan, subscription status, and invoice metadata. We do not store full card numbers.

Sharing

Vendors below process data for us to run the product. We do not sell it or give it to other apps. All of this goes over HTTPS.

  • Amazon Web Services — hosting and storage
  • Stripe — payments
  • SendGrid — transactional email
  • Google — sign-in if you use it; Analytics and Ads on the website
  • PostHog — product analytics
  • Microsoft Clarity — website session analytics
  • OpenAI — only if you supply your own API key in Studio

Google sign-in is website-only. If you use it, we receive the email, name, and photo Google sends for that login. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Retention and requests

We keep account and saved-component data while your account is active, and as needed for billing, security, and law. Email team@divmagic.com to access, correct, or delete your data.

Changes

Updates are posted at https://divmagic.com/privacy.