Privacy Policy

Your privacy is our top priority

Last Updated: May 13, 2026

TL;DR - Your Privacy by Default

MarkView does NOT collect, store, or share your personal data. The extension has no servers of its own - your markdown files and settings stay on your device by default.


The one feature that can transmit a portion of your document off your device is PlantUML diagram rendering, which sends the source code of plantuml fenced blocks to a public diagram server so it can return the rendered image. This feature is off by default and requires your explicit consent - see section 5.3 for details.

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, 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

The extension has no servers and no databases of its own - there is no central place where your data could be collected. The only document-content transmission anywhere in the extension is the optional, consent-gated PlantUML rendering described in section 5.3, and even that goes directly from your browser to the diagram server you choose, never through us.

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.)
Important: All this data remains on your device and is never transmitted anywhere. You can clear this data anytime through Chrome's extension settings or by uninstalling the extension.

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 Downloads Permission (downloads)

Purpose: To export rendered markdown to HTML and DOCX file formats.

Data Access: Only the markdown content you are currently viewing. Exported files are saved directly to your browser's download location.

Scope: Only activated when you explicitly click export buttons. Files contain only the content you choose to export.

User Control: You initiate all downloads. No automatic or background downloads occur.

4.4 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.5 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 PlantUML Diagram Rendering Server

MarkView can render plantuml fenced code blocks by sending their source code to a public PlantUML diagram server, which returns an SVG image that the extension displays inline. This is the only feature in MarkView that transmits any part of your document off your device.

What this means:

  • This feature is off by default. PlantUML fenced blocks are shown as plain source code until you opt in.
  • Opting in requires explicit consent through a one-time dialog that names the diagram server you're allowing the extension to use. You can decline or postpone the decision at any time.
  • The default server is https://www.plantuml.com/plantuml. You can configure a different server (for example, a self-hosted instance) in Settings → PlantUML.
  • Only the source of plantuml fenced code blocks is sent - nothing else from your document, settings, or browsing activity.
  • The request goes directly from your browser to the configured diagram server. MarkView does not proxy, log, or store these requests.
  • The diagram server you choose may log the request (URL, timestamp, IP address) as part of standard server operations. The community-run default server publishes its own policy at plantuml.com.

How to revoke or change: Open Settings → PlantUML and toggle the feature off, or click "Revoke consent" to clear the consent flag entirely. Already-rendered diagrams will revert to showing their source code on the next render.

5.4 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

You can export your settings as a JSON file from Settings → Import / Export. The exported file contains only the preference values listed in section 3, never any of your document content. You can import the same file later to restore those preferences on the same device or any other.

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. MarkView's role under GDPR is intentionally minimal:

  • MarkView has no servers and no databases - there is no central place where personal data is collected, processed, or stored.
  • No central data controller relationship exists between MarkView and its users for ordinary use of the extension.
  • Local preferences (see section 3) are processed entirely on your device.

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

Legal basis for PlantUML rendering: When you enable PlantUML diagram rendering (see section 5.3), the source of plantuml fenced blocks is sent directly from your browser to the diagram server you have configured. This processing is performed under your explicit consent, obtained through the in-product consent dialog. You can withdraw consent at any time in Settings → PlantUML, which prevents any further transmission. The diagram server you choose is the data recipient for that request; MarkView neither proxies nor stores it.

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:

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)

Privacy Summary

MarkView respects your privacy completely. We don't collect your data. We don't track you. We don't sell anything. We don't have servers. We're just here to make your markdown files look beautiful.

Your files, your settings, your privacy – all stay with you.