📊Data Collection

Healthify does NOT collect, store, or transmit any user data.

We do not:

• Collect personal information
• Track your browsing history
• Store analyzed website data
• Send data to external servers
• Use cookies for tracking
• Share data with third parties
• Use analytics or tracking tools

⚙️How Healthify Works

All website analysis is performed locally in your browser:

• Local Analysis: When you click the extension icon, JavaScript code runs directly in your browser to analyze the current webpage
• No Server Communication: Results are displayed immediately without any data leaving your device
• No Storage: Analysis results are temporary and not saved anywhere
• 100% Private: Only you can see the health check results

🔐Permissions Explained

Healthify requests the following Chrome permissions. Here's why each is needed:

1. activeTab

Why we need it: To read and analyze the content of the webpage you're currently viewing.

What we do with it: Access the page's HTML, CSS, and JavaScript to perform health checks (SEO, performance, accessibility, etc.).

What we DON'T do: We don't access tabs you're not actively using, and we don't store or transmit the page content.

2. scripting

Why we need it: To inject the analysis code into the current webpage.

What we do with it: Run JavaScript code that analyzes the page structure, performance metrics, and accessibility features.

What we DON'T do: We don't modify the webpage, inject ads, or track your behavior.

3. storage

Why we need it: To save your preferences locally on your device.

What we do with it: Store settings like notification preferences or display options (if you customize the extension in the future).

What we DON'T do: We don't store personal information, browsing history, or analyzed website data.

🌐Third-Party Services

Healthify does not use any third-party services, including:

• No analytics tools (Google Analytics, Mixpanel, etc.)
• No advertising networks
• No tracking pixels
• No external APIs or cloud services
• No crash reporting tools

🔒Data Security

Since Healthify doesn't collect or transmit any data, there is no data to secure or protect on our end. All analysis happens locally in your browser, which means:

• Your data never leaves your device
• No risk of data breaches from our servers (we don't have any!)
• Complete privacy and security

👤User Rights

Since we don't collect any personal data, there is no data to:

• Request access to
• Request deletion of
• Request correction of
• Port to another service

You have complete control over the extension at all times. You can:

• Disable the extension anytime from Chrome settings
• Uninstall the extension without leaving any trace
• Use the extension without creating any account

👶Children's Privacy

Healthify does not knowingly collect any information from anyone, including children under 13. Since we don't collect any data at all, the extension is safe for users of all ages.

🌍International Users

Healthify works entirely in your local browser, regardless of your location. No data crosses international borders because no data leaves your device.

📝Changes to This Policy

We may update this privacy policy from time to time to reflect changes in:

• The extension's functionality
• Legal requirements
• Privacy best practices

When we make changes, we will:

• Update the "Last Updated" date at the top of this page
• Notify users through the extension if changes are significant
• Continue to maintain our commitment to privacy

Current version: 1.0.0
Last updated: January 25, 2026

⚖️Legal Compliance

This privacy policy complies with:

• GDPR (General Data Protection Regulation) - EU
• CCPA (California Consumer Privacy Act) - USA
• Chrome Web Store Policies

Since we don't collect any personal data, most data protection regulations don't apply. However, we've designed Healthify with privacy-first principles to ensure compliance with all privacy laws.

💡Open Source

Healthify's code is transparent and can be audited. Users and security researchers can verify that we don't collect any data by:

• Inspecting the extension source code
• Reviewing the Chrome Web Store listing
• Monitoring network traffic (you'll see no outgoing requests)