Privacy Policy

1. Introduction

Welcome to MarkView. This Privacy Policy explains how MarkView ("we", "us", "our", or "Extension") handles information when you use our Chrome browser extension.

MarkView is designed with privacy as a core principle. We believe your markdown files and browsing habits are your business, not ours.

2. Information We Do NOT Collect

MarkView does NOT collect, store, transmit, or share any of the following:

• Your markdown file contents or data
• Your browsing history or URLs visited
• Personal identification information (name, email, address, etc.)
• Usage statistics, analytics, or telemetry
• IP addresses or device identifiers
• Location data
• Cookies or tracking data
• Any form of behavioral or user activity data

We have no servers, no databases, and no way to access your data. Period.

3. Local Data Storage

MarkView uses Chrome's local storage API (chrome.storage.local) to save your preferences on your device only. This locally stored data includes:

• Theme preference (dark/light/auto)
• Font family selection
• Font size and line height preferences
• Layout settings (centered mode, max width)
• Sidebar visibility preferences
• Feature toggles (syntax highlighting, auto-refresh, etc.)

4. Chrome Permissions Explained

MarkView requests specific Chrome permissions to function. Here's exactly why each permission is needed and what data we access:

4.1 Storage Permission (storage)

Purpose: To save your preferences locally on your device.

Data Access: Only reads and writes your settings (theme, font, etc.) to local storage. No external transmission occurs.

Scope: Limited to extension settings only.

4.2 ActiveTab Permission (activeTab)

Purpose: To access markdown file content in the currently active tab for rendering.

Data Access: Only reads the markdown file content you're viewing. All processing happens entirely in your browser.

Scope: Limited to active tab when extension is invoked.

4.3 File URL Access (file:///*)

Purpose: To read and render local markdown files (.md files) from your computer.

Data Access: Only accesses local files when you explicitly open them in Chrome.

User Control: This permission is disabled by default and must be manually enabled by you in chrome://extensions → MarkView → Details → "Allow access to file URLs".

4.4 Host Permissions (<all_urls>)

Purpose: To render markdown files from any website (GitHub, GitLab, documentation sites, etc.).

Data Access: Only reads markdown content from URLs you visit. Processing is local.

Note: We don't intercept or modify other web pages. The extension only activates on markdown files.

5. Third-Party Services

MarkView uses minimal third-party services. Here's what you should know:

5.1 Google Fonts CDN

When you select a custom font (other than "Default"), MarkView loads font files from Google Fonts CDN (fonts.googleapis.com).

What this means:

• Your browser makes a request to Google's servers to download font files
• Google may log this request (IP address, timestamp) as part of standard CDN operations
• This is a standard service used by millions of websites worldwide
• Google's privacy policy applies: https://policies.google.com/privacy

How to avoid: Select the "Default" font option to prevent any external font requests.

5.2 External Markdown Sources

When you view markdown files from external websites (GitHub, GitLab, etc.):

• Your browser fetches the file directly from that website
• MarkView does not proxy, cache, or store these files
• The privacy policies of those platforms apply
• MarkView does not send any information about your viewing to those platforms

5.3 No Analytics or Tracking Services

MarkView does NOT use:

• Google Analytics
• Facebook Pixel
• Crash reporting services (Sentry, Bugsnag, etc.)
• User behavior tracking
• A/B testing tools
• Any other third-party analytics or tracking services

6. Data Security

Since MarkView doesn't collect or transmit your data, there's no central database or server that could be compromised. Your data security is as strong as your device's security.

Security measures:

• All processing happens locally in your browser
• Settings are encrypted by Chrome's built-in storage encryption
• No network transmission of personal data
• Extension code is reviewed by Google before publication
• Regular security updates through Chrome Web Store

7. Children's Privacy (COPPA Compliance)

MarkView does not collect any information from anyone, including children under 13 years of age. The extension is safe for users of all ages and complies with the Children's Online Privacy Protection Act (COPPA).

8. Data Retention

Since we don't collect data, we don't retain data. Your locally stored preferences remain on your device until:

• You clear Chrome's extension data
• You uninstall the extension
• You manually reset settings in the extension popup

9. Your Rights and Control

You have complete control over your data:

9.1 Access Your Data

All your settings are stored locally. You can view them:

• In the extension popup (click the extension icon)
• In Chrome DevTools: chrome.storage.local.get()

9.2 Delete Your Data

You can delete all extension data by:

• Uninstalling the extension (right-click icon → Remove from Chrome)
• Clearing site data in Chrome settings
• Using the "Reset to Defaults" button in extension settings

9.3 Export Your Settings

Your settings are not currently exportable, but they're simple preference values you can reconfigure easily.

9.4 Opt-Out

Simply don't use the extension, or disable specific features in the settings popup.

10. California Privacy Rights (CCPA)

Under the California Consumer Privacy Act (CCPA), California residents have rights regarding their personal information. However, since MarkView does not collect personal information, these rights are not applicable. There is no personal data to:

• Access or download
• Delete
• Opt-out of sale (we don't sell any data)
• Correct or update

11. European Privacy Rights (GDPR)

Under the General Data Protection Regulation (GDPR), European users have specific rights regarding their personal data. However, since MarkView does not collect, process, or store personal data:

• There is no data controller or processor
• No data processing agreements are needed
• No data transfer occurs
• GDPR obligations regarding data collection don't apply

Legal Basis: The local storage of preferences operates under "Legitimate Interest" to provide extension functionality, with implicit consent through installation and use.

12. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect:

• Changes in extension features or functionality
• Changes in legal or regulatory requirements
• Industry best practices

When we make changes:

• We will update the "Last Updated" date at the top of this page
• Significant changes will be communicated through extension update notes
• Continued use after changes constitutes acceptance

We encourage you to review this Privacy Policy periodically.

13. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or MarkView's privacy practices, please contact us:

• Email: markview.app@gmail.com
• Support Page: MarkView Support

We will respond to privacy-related inquiries within 30 days.

14. Compliance Certifications

MarkView is compliant with:

• Chrome Web Store Policies: All required permissions are justified and minimal
• GDPR: No personal data collection
• CCPA: No personal data collection or sale
• COPPA: Safe for children (no data collection)

15. Disclaimer

MarkView is provided "as-is". While we take privacy seriously, users are responsible for:

• Securing their own devices and browsers
• Understanding what markdown files they open
• Being aware that external markdown sources have their own privacy policies
• Reviewing privacy implications of third-party fonts (if used)