LAUNCHGUARD PRIVACY POLICY
Last updated: 4 October 2026
1. About LaunchGuard
LaunchGuard is a local-first Chrome extension for user-requested website pre-launch quality assurance (QA). LaunchGuard is independently developed and operated from Pakistan.
Privacy and support contact: bilujee512@gmail.com
This policy explains how LaunchGuard processes information when you use website scanning features, LaunchGuard Pro, subscription management, Restore Pro, or customer support.
2. Website data processed by the extension
LaunchGuard processes website information only when you use its QA features.
Depending on the feature, this may include:
- page URL and title;
- metadata and headings;
- links, image and resource URLs;
- form and page structure;
- accessibility and technical information;
- selected visible page text;
- performance measurements;
- runtime error type and source location; and
- visible-viewport screenshots that you explicitly capture.
LaunchGuard does not intentionally collect passwords, payment-card field values, cookies, browser history, keystrokes, or values entered into normal form fields.
Website scans, projects, screenshots, comparisons, custom rules and report branding are stored locally in your browser unless you export them yourself.
LaunchGuard does not upload ordinary website scan content, screenshots or project data to the LaunchGuard backend.
3. Local storage
LaunchGuard uses Chrome local storage and IndexedDB to store information such as:
- settings;
- Free feature-trial counters;
- saved scans and projects;
- comparison results;
- screenshots;
- custom rules;
- report branding; and
- subscription-related local state.
LaunchGuard does not use Chrome Sync for this information.
You can delete saved scans, projects, captures and other local data through LaunchGuard controls. Uninstalling the extension normally removes its extension-local data, but exported files remain wherever you saved them.
4. Pro subscription and installation verification
Each LaunchGuard installation creates:
- a random public installation ID; and
- a separate random private installation secret.
These values do not intentionally contain your name, email address or browsing history. LaunchGuard uses them to verify paid Pro access and prevent simple unauthorized sharing or local modification of subscription status. Subscription-related requests are sent over HTTPS to the LaunchGuard backend hosted on Vercel.
The backend may store limited records in a Neon database, including:
- installation ID;
- a cryptographic hash derived from the installation secret;
- Paddle customer and subscription IDs;
- subscription status;
- product and price IDs;
- billing-period dates; and
- scheduled subscription changes.
The raw private installation secret is not intentionally stored in the backend database.
5. Payments and Paddle
LaunchGuard Pro payments are handled by Paddle. LaunchGuard does not receive or store your full payment-card number. Paddle may process billing, payment, tax, fraud-prevention, customer and subscription information under its own privacy policy and buyer terms. LaunchGuard receives only the subscription information needed to determine whether Pro access should be available. Subscription management, including invoices, payment-method updates and cancellation, is handled through Paddle's secure Customer Portal.
6. Restore Pro
If you reinstall LaunchGuard, use a new browser profile or move to another device, you may use Restore Pro. To restore a subscription, you provide the email address used for your Paddle purchase. The LaunchGuard backend uses that email address to locate an eligible Paddle subscription and sends a temporary verification code to the purchase email address. Restore verification emails are currently delivered using Gmail/Google email infrastructure.
Restore security records may include:
- installation ID;
- Paddle customer and subscription IDs;
- hashed email information;
- a hashed verification code;
- limited abuse-prevention information;
- attempt count; and
- expiry timestamps.
Verification codes are temporary and expire after a short period.
A successful restore transfers the subscription binding to the current LaunchGuard installation. The previously bound installation may lose Pro access after its next entitlement check.
7. Third-party services
LaunchGuard currently uses the following services for limited operational purposes:
- Google Chrome / Chrome Web Store: extension distribution and browser functionality;
- Paddle: checkout, payments, subscriptions and Customer Portal;
- Vercel: LaunchGuard subscription backend hosting;
- Neon: subscription and entitlement database hosting;
- Google/Gmail: Restore Pro verification emails and support email; and
- Flycricket or another public hosting provider: hosting public Privacy Policy or Terms pages.
LaunchGuard does not sell user data or provide website scan content to advertising networks or data brokers.
8. Analytics, advertising and Limited Use
LaunchGuard does not include advertising or a LaunchGuard analytics/tracking SDK.
LaunchGuard does not use website content or browsing information for:
- personalized advertising;
- sale to data brokers;
- unrelated profiling;
- credit decisions; or
- AI model training.
LaunchGuard only accesses and uses browser and website information as necessary to provide its disclosed QA functionality and related operational purposes such as security, subscription verification and support.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.**
9. Support, retention and your rights
If you email bilujee512@gmail.com, we receive your email address and anything you voluntarily include in your message or attachments. Do not send passwords, payment-card details, authentication tokens or unnecessary confidential website information. Local website data remains on your device until you delete it, Chrome removes it, or LaunchGuard is uninstalled. Backend subscription records may be retained as reasonably necessary to provide entitlement verification, Restore Pro, billing support, fraud prevention and legal or accounting requirements. Paddle separately retains billing and transaction records according to its own policies and applicable law.
You may contact bilujee512@gmail.com to request access, correction or deletion of information controlled by LaunchGuard where applicable. Some payment records may need to be handled by Paddle.
10. Security and changes
LaunchGuard uses HTTPS for backend communication, server-side subscription verification, Paddle webhook verification, random installation credentials and hashed restore credentials. No system can guarantee absolute security. We may update this Privacy Policy if LaunchGuard's features, service providers or legal requirements change. The "Last updated" date will be revised when changes are made.
For privacy or support questions, contact:
bilujee512@gmail.com