Your files. Understand the boundaries.

What this page covers

This explanation covers Web2Markdown Capture and the Web2Markdown desktop editor as currently prepared for public release. The software works with local captures and documents without a GDK product account or cloud document service.

This marketing website is separate from the software. Its website analytics, contact handling, and cookies are described in the GDK Digital Privacy Policy and Cookie Policy.

Pages and files you choose to capture

The extension reads page content for the capture action you request. Output can include page text, title, source URL, author information when available, capture metadata, and images. Optional evidence files can include headings, links, image details, and structured-data observations from the page.

Capturing an authenticated page can save private content you can see while signed in. Access to a page is not permission to redistribute it. Review captures before sharing them.

Local image downloads contact the source image servers. Site Tree and sitemap actions contact the requested site and applicable discovery URLs. Remote-image output retains external URLs. Local processing does not mean these network requests are absent.

What stays on this computer

Saved captures and edited documents stay in the folders you choose. Extension settings, drafts, capture recovery data, and chosen-folder access information use local browser storage. Desktop settings and session state support reopening your working environment.

Desktop recovery and session data, recently closed tabs, local snapshots, and batch rollback records can retain document text, including older versions of a document. Deleting a capture, an export, or its source file does not necessarily remove these other local copies.

Preview recovery keeps one draft within a bounded local budget for up to 24 hours. Site Tree recovery retains bounded job history for up to 7 days. Expired data is cleaned when the storage is next accessed, not while Chrome is closed.

Use Clear draft and Clear inactive history to remove retained extension recovery data. These actions do not remove desktop recovery records or captures already saved on disk. Delete unwanted capture files separately using your operating system. If you need to remove sensitive desktop recovery data, contact support for guidance appropriate to your installed version; this page does not promise a single erase-all control.

Folders managed by another backup or sync service may be copied by that service. Web2Markdown does not control your operating system, employer policies, or third-party storage tools.

Why the extension requests access

Page and tab access

Used to read selected page content and support the capture and crawl actions you request.

Downloads and selected folders

Used to write Markdown, assets, and receipts. A custom folder requires permission from the browser; you can change the destination in Settings.

Local storage

Used for preferences and bounded preview/job recovery.

Clipboard, menus, and side panel

Support explicit copy actions, page context actions, and the persistent capture interface.

Optional native messaging

Supports the local agent bridge when you enable and configure it. Ordinary capture does not require the bridge.

The eventual Chrome Web Store listing will describe the permissions in the submitted build. Store disclosure review is part of release preparation, not yet a completed approval.

Optional agent and native bridge

Agent access is opt-in. It allows a configured local agent to request captures and receive completion information through the supported local workflow. Enable it only for tools and workflows you intend to trust.

An agent can separately process or transmit files it can access. Web2Markdown cannot govern a third-party agent's privacy policy or your agent configuration. Turning off page-control visibility hides the control; review the connection settings separately when you want to disable agent access.

Diagnostics, support, and external links

Diagnostics and local crash information help explain failures. They are not automatically submitted as a support request. Review any diagnostic export, screenshot, or example before sending it to GDK Digital.

Opening website, support, or release links leaves the local application and contacts that destination. Emailing support sends the information you include to GDK Digital and your email provider. A future GitHub issue will be public unless explicitly submitted through a private channel.

Do not share API keys, passwords, or sensitive configuration files. For a privacy question or deletion request relating to information you sent us, contact support@gdkdigital.com.

Your practical choices

• Preview sensitive captures before saving or sharing.
• Choose local assets if you want saved images rather than ongoing remote references.
• Use a folder appropriate to your document sensitivity and backup policy.
• Clear retained drafts and inactive crawl history when you no longer need recovery.
• Keep optional agent access disabled unless your workflow needs it.
• Review local diagnostic exports before sending them anywhere.

See the workflow guide for folder and recovery behavior, or contact support for a specific question.