Privacy Policy

Purpose and scope

Markup Desk is a browser-extension workspace for writing, reading, cleaning, and converting HTML, Markdown, and BBCode. The product is intended to work with text that the user deliberately enters, pastes, imports, edits, or creates inside the extension itself.

This policy applies to Markup Desk version 1.0.0 and the packaged editor, conversion engine, safe preview, document outline, Link Builder, snippet library, import workflow, export workflow, and local draft persistence included with that version.

This policy does not govern Google Chrome, the Chrome Web Store, the operating system, websites that a user later visits through a hyperlink, external image hosts that a user explicitly loads, or other software running on the same device.

Local-first architecture

The primary Markup Desk workflow runs inside a packaged extension page. Parsing, sanitization, syntax conversion, document statistics, outline generation, Link Builder output, and snippet insertion are performed by JavaScript bundled with the extension.

Version 1.0.0 does not require a Markup Desk account and does not depend on a developer-operated document-processing server. The document source is not uploaded to the developer in order to generate the preview or perform a conversion.

Markup Desk is therefore able to provide its core editing features without sending the current draft to an online conversion API, remote artificial-intelligence service, or hosted synchronization database.

Document information processed

Markup Desk processes the document information necessary to provide the workspace. Depending on how the product is used, this may include raw HTML, Markdown, BBCode, plain text contained inside those formats, URLs, headings, tables, quotes, code samples, image references, and other markup intentionally entered by the user.

The editor also processes a document title, the selected source format, the selected Write, Split, or Read layout, source length, line count, word count, link count, and heading structure. These values support the visible editing interface and are not used to create a developer-side behavioral profile.

Because the extension is a general text editor, document text can contain personal, confidential, or otherwise sensitive information if the user chooses to enter such information. Markup Desk does not need to understand the real-world meaning of the text in order to provide conversion and preview features.

Local draft storage

The current draft is stored locally in the browser profile using the extension page's local storage context. The version 1.0.0 draft record uses the key markupDeskDocumentV1.

That local record can include the current source text, document title, active source format, and active workspace view. The purpose of the record is to reopen the workspace with the user's most recent local draft after the editor page is closed or reloaded.

Markup Desk does not use chrome.storage.sync in version 1.0.0 and does not intentionally synchronize the current document through a developer cloud account.

Browser-profile backups, operating-system backups, enterprise management software, or other device-level tools may copy browser files independently of Markup Desk. Those systems are governed by their own behavior and policies.

Safe preview and HTML sanitization

Markup Desk renders a reading view from the current source. Before HTML reaches that reading view, the product applies a sanitizer and an allowlist of supported document elements.

Version 1.0.0 is designed to remove or neutralize active and unsafe material such as script elements, style elements, iframes, object and embed elements, executable SVG or MathML content, HTML event handler attributes, unsupported element attributes, and javascript: URLs.

Unsupported structural wrappers can be unwrapped so their readable text remains available where this can be done safely. Elements that represent active or embedded content can be removed instead of being executed.

Sanitization reduces risk when reading unfamiliar markup, but it is not a promise that arbitrary HTML is suitable for every security or compliance context. Users should still avoid treating untrusted markup as executable code.

External images are guarded by default

A document can contain an image reference. Markup Desk does not automatically request an external HTTP or HTTPS image merely because its URL appears in the source or sanitized preview.

Instead, an external image is replaced in the reading view with a guarded placeholder showing the image description and source URL. The user can explicitly choose to load an absolute external image.

If the user chooses to load that image, the browser sends a normal network request directly to the image host. The external host can receive information normally associated with a web request, such as the user's network address and technical request metadata. That request is to the image provider, not to a Markup Desk server.

Relative image URLs cannot be reliably resolved in a standalone markup workspace because there is no original webpage base URL. Markup Desk therefore leaves those references guarded rather than guessing a remote location.

File imports

The Import control lets the user choose a local text-based markup file. Version 1.0.0 accepts common HTML, Markdown, BBCode, and text file extensions exposed by the file chooser.

The selected file is read with the browser's local FileReader API. The imported content is placed into the Markup Desk editor and is not uploaded to a developer server as part of the import process.

Version 1.0.0 limits an individual imported document to 2 MB. The limit is intended to keep the browser workspace responsive and to avoid unexpectedly filling the extension's local draft storage.

Markup Desk does not receive arbitrary access to the user's file system. It only receives the file that the user deliberately selects through the browser file picker.

Local exports

The Export control creates a text file from the current source in the selected syntax. HTML documents use an HTML file extension, Markdown documents use a Markdown extension, and BBCode documents use a BBCode extension.

The export is created locally with a browser Blob and a temporary object URL. Markup Desk does not require the Chrome downloads permission for this workflow and does not send the exported file to a remote storage provider.

The browser and operating system control the final download location, download history behavior, backup behavior, and any subsequent sharing performed by the user.

Snippets

Markup Desk contains packaged starter snippets for common document structures and also lets users save selected source as reusable local snippets.

User-created snippets can contain any text intentionally selected by the user. Version 1.0.0 stores those snippets locally under the key markupDeskSnippetsV1 and retains a bounded list of local snippet entries.

A custom snippet retains its local name, original source syntax, and saved source. When a snippet is inserted into a document using a different syntax, conversion is performed locally.

Users should avoid saving passwords, authentication tokens, payment card data, private keys, or other secrets as snippets because local snippet storage is not an encrypted credential vault.

Chrome permissions

Markup Desk version 1.0.0 requests no Chrome permissions and no host permissions in its manifest.

It does not request activeTab, scripting, tabs, history, bookmarks, downloads, clipboardRead, broad website access, or access to all URLs.

The packaged background service worker exists only so a click on the extension toolbar icon can open the packaged Markup Desk editor in a new tab. Chrome allows that action without granting the extension general tab-reading permission.

No webpage inspection or content scripts

Markup Desk does not inject a content script into ordinary websites in version 1.0.0. It does not automatically read the DOM, text, forms, cookies, or page content of websites the user visits.

A URL inside a document is treated as markup data until the user deliberately activates a rendered hyperlink or chooses to load a guarded external image.

If a user copies content from a webpage and pastes that text into Markup Desk, the pasted content becomes part of the local document because the user explicitly provided it to the editor.

Clipboard behavior

Version 1.0.0 does not request Chrome's clipboard-reading permission and does not monitor the clipboard in the background.

Text reaches the editor through normal user-driven browser actions, including typing and paste operations performed while the Markup Desk source editor is focused.

The extension cannot use the current version's manifest to silently harvest unrelated clipboard contents while the user is browsing other pages.

Network activity

The Markup Desk conversion engine, sanitizer, document outline, snippets, Link Builder, import logic, and export logic do not depend on a developer backend in version 1.0.0.

The packaged production source does not need to send the current document to a remote conversion service in order to produce HTML, Markdown, or BBCode output.

User-initiated actions can still cause ordinary external network activity. Clicking an external hyperlink opens its destination, and explicitly loading a guarded external image requests that image from its host.

Those destination websites and image providers are independent third parties and can apply their own privacy, logging, cookie, and security practices after a user chooses to contact them.

No analytics, ads, or remote AI

Markup Desk version 1.0.0 does not include a third-party analytics SDK such as Google Analytics, Firebase Analytics, Mixpanel, Amplitude, Segment, PostHog, or an equivalent usage-tracking service.

It does not contain an advertising network, behavioral advertising profile, retargeting pixel, cross-site marketing identifier, or developer-side history of which documents a user edits.

The current document is not sent to a remote AI model for writing, conversion, classification, summarization, or profiling in version 1.0.0.

Sale and sharing of local document data

The developer does not sell, rent, trade, or provide the local Markup Desk draft or snippet library to advertisers, data brokers, marketing companies, or analytics providers.

Under the normal version 1.0.0 workflow, the developer does not receive a hosted copy of the user's current draft or local snippets, so there is no developer-side Markup Desk document database to sell or disclose as part of normal product operation.

A user can independently share an exported file, paste source into another service, click a link, or load an external image. Those are user-controlled actions outside the local draft storage workflow.

Security model and limitations

Markup Desk reduces exposure by using packaged conversion code, avoiding broad website permissions, sanitizing active HTML before preview, guarding external images, and keeping the working document local by default.

Local browser storage is not equivalent to end-to-end encrypted storage. A person or process with sufficient access to the same unlocked device, browser profile, backup files, or operating-system account may potentially access local extension data.

Users handling highly sensitive material should use security tools designed for that class of data and should consider exporting and removing drafts when they no longer need local persistence.

Sanitization is intended for a document preview, not for proving that arbitrary HTML is safe to deploy on a production website. Developers remain responsible for the security requirements of the environments where exported markup is eventually published.

User control

Users decide what text is typed, pasted, imported, converted, cleaned, saved as a snippet, exported, or opened through a link.

The New command can replace the current local document with a fresh workspace after confirmation when source is present. Custom snippets are managed separately from the current document.

Custom snippets can be removed from the snippet interface. Users can also remove the extension through Chrome, subject to Chrome's own handling of extension-local data during uninstall.

Before intentionally clearing important local material, users should export any document or snippet content they want to retain elsewhere.

Retention

The current draft is retained locally so the workspace can reopen with the most recent saved state. Version 1.0.0 does not impose an automatic short expiration period on that current local draft.

Custom snippets remain in the browser profile until removed by the user, displaced by product limits, or removed as part of browser or extension data management.

Exported files are outside Markup Desk's local draft store and remain wherever the browser or user saves them until the user or another system deletes them.

Children

Markup Desk is a general-purpose text and markup utility. It does not provide public profiles, social messaging, targeted advertising, or a developer account system specifically directed at children.

The developer does not knowingly maintain a remote database of children's Markup Desk documents because the normal local document workflow does not upload those documents to a developer server.

Legal requests and information actually possessed

If the developer receives a legally valid request for information, the developer can only provide information that is actually in the developer's possession and subject to the request.

Markup Desk's normal local draft and snippet records are stored in the user's browser profile rather than a developer-hosted document database. The developer therefore generally does not possess those local records merely because the extension is installed.

Future product and policy changes

This policy may be updated to improve clarity, reflect changes in browser-platform requirements, or describe changes in the product's actual data-handling behavior.

If a future Markup Desk version introduces cloud synchronization, accounts, analytics, remote AI, broader website access, additional Chrome permissions, automatic external-resource loading, or other materially different processing, the privacy policy and applicable Chrome Web Store disclosures should be updated before or alongside that behavior.

The effective date and reviewed product version appear at the top of this document so the policy can be compared with the installed extension version.

Contact

For privacy questions about Markup Desk, use the developer contact information displayed on the Chrome Web Store listing from which the extension was obtained.

When contacting the developer, avoid sending passwords, private keys, authentication tokens, payment-card information, confidential documents, or other sensitive source unless the information is strictly necessary to explain the privacy request.