1. What we collect

Email address

When you create an account or sign in, your email address is sent to Google's Firebase Authentication service for the sole purpose of creating and identifying your account. Email/password sign-in requires email verification. Google sign-in uses Google's standard OAuth flow.
Authentication tokens

After sign-in, Firebase issues authentication tokens (an ID token and a refresh token) that are stored locally in your browser's IndexedDB so you stay signed in across browser restarts. These tokens never leave your device except when refreshing the session with Firebase.
Prompts and generated content URLs

Prompts you enter into the extension are typed into Magnific's UI on your behalf. The URLs of generated images and videos are read from Magnific's DOM so the extension can download the files to your local Downloads folder. Both prompts and URLs are kept in memory only during a session, and may be exported to a CSV file at your explicit request (the CSV is downloaded to your computer; it is not transmitted anywhere).

1. What we do NOT collect
   
   Browsing history outside Magnific
   Form input on any other site
   Personal information beyond the email you provide for sign-in
   Health, financial, location, or biometric data
   Click tracking, mouse movement, keystroke logging, or any analytics / telemetry
   Your Magnific account credentials (the extension uses your existing Magnific browser session — it never asks for or sees your Magnific password)
2. Third-party services
   
   Firebase Authentication (Google) — handles your sign-in and email verification. See Firebase's privacy notice.
   Cloudflare Pages serves a small compatibility configuration file that helps the extension stay aligned with Magnific UI changes. No user data is sent to this endpoint.
   jsdelivr CDN — serves a public list of disposable / temporary email domains, fetched lazily only when a user attempts to sign up. No user data is sent.
   Magnific (magnific.com) — the third-party site the extension automates. Your prompts are submitted to Magnific through Magnific's own normal UI flow, just as if you typed them yourself.
3. Data storage and retention

All extension data lives in your own browser:

chrome.storage.local — settings (concurrency, delay, toggles), the cached disposable-email blocklist (refreshed daily)
IndexedDB — Firebase Auth tokens (cleared on sign-out)
localStorage — small UI state like resume offset


We do not run a backend server that stores your prompts, generated content, or usage data. If you sign out or uninstall the extension, all locally-stored data is removed.
5. Security

The extension communicates with Firebase and Magnific over HTTPS only. Authentication tokens are stored using Firebase's standard IndexedDB persistence. We do not transmit any of your data over unencrypted channels.
6. Children

The extension is not directed at children under 13. We do not knowingly collect data from children. If you believe a child has used the extension, please contact us and we will delete the associated Firebase account.
7. Your rights

Access & export: all locally-stored data is accessible via your browser's developer tools; CSV export is available in the extension UI.
Deletion: sign out (clears local tokens) and contact us to delete your Firebase account record (email address).


1. Changes to this policy

If this policy changes, the "Last updated" date at the top will be revised. Material changes will also be announced in the extension's Web Store listing notes.
9. Contact

Questions about this policy or data deletion requests: thapadeepak726@gmail.com