Privacy Policy

Last Updated: July 14, 2026

This Privacy Policy describes how CodePrettify ("we", "us", or "our") handles your information when you use our desktop application and browser extension.

Summary: CodePrettify handles supported page content, resource URLs, and related response metadata locally on your device so it can format, inspect, compare, and export raw-code resources. We do not transmit that content or metadata to our servers. In limited encoding-recovery cases described below, the extension may re-request the same URL directly from the site you are already visiting. If you explicitly use the HTTP Client, your browser sends the request you compose directly to the target URL; CodePrettify does not proxy it.
Marketplace disclosure: CodePrettify uses access to supported raw-code pages only to provide the viewer features that are described in its browser extension marketplace listings and in the product UI. We do not sell the data, use it for advertising, or let humans read it unless you explicitly choose to share information with us for support.

1. Data Handling

CodePrettify handles supported page content and resource metadata locally to deliver its viewer features, but it does not collect or transmit that information to our servers.

To determine whether the extension should activate, a lightweight loader checks the current page's protocol, URL path, and browser-reported content type locally in your browser. Full viewer assets are injected only when the page appears to be a supported raw-code resource.

When you open a supported raw-code resource in your browser, the extension reads the content of that specific tab to apply formatting, syntax highlighting, search, code folding, diagnostics, compare tools, statistics, exports, and other viewer features. Supported content includes JavaScript, TypeScript, Markdown, JSON, JSON with Comments (JSONC), JSONL/NDJSON, TOML, YAML, CSS, XML, and RSS/Atom feeds, including resources detected by content type even when the URL has no matching file extension. You can also open a file you explicitly pick or drag onto the extension's launcher or welcome page; that file is read in your browser and shown in the viewer. This handling happens locally within your browser on your device.

To provide request metadata inside Statistics & Diagnostics, the extension reads locally available metadata for the active resource, such as the resource URL, browser-reported content type and character encoding, response-size estimates, transfer-size hints, and browser timing metrics. The extension does not capture request headers, response headers, cookies, or request bodies for this viewer surface.

In limited cases, when a JavaScript file appears to have been decoded with a legacy character set and may contain mojibake, the extension may re-fetch the same URL from the original website to recover the correct UTF-8 text. That request goes directly from your browser to the website you are already visiting and may include your normal browser credentials for that site. The fetched data is processed locally and is not transmitted to CodePrettify or our servers.

The extension's HTTP Client sends a request only after you choose Send. The method, target URL, headers, body, and any credentials you provide are sent directly from your browser to that target service and are subject to the target service's privacy policy. CodePrettify does not proxy, inspect, or receive those requests or responses on our servers.

Clipboard features are user initiated. The extension writes text to your clipboard only when you use a copy or share action, and the compare tool uses text you paste manually instead of reading clipboard contents automatically.

2. Local Storage

We use browser extension storage to save preferences such as:

Viewer preferences and counts used to arrange frequently used actions may use chrome.storage.sync when it is available, so they can follow browser profiles signed into the same browser account. The browser vendor operates that sync service; CodePrettify does not receive the data. Synced settings do not include viewed document content, resource URLs, per-URL view state, HTTP Client requests, responses, or credentials. Local storage is used as a fallback when sync is unavailable.

To show an occasional, dismissible prompt asking whether you are enjoying CodePrettify, the extension also keeps two local counters — when it was first installed and how many times it has been used — and the date on which you responded to or dismissed that prompt. These values stay in your browser's local storage, are never transmitted to us, and are used only to decide whether and when to show the one-time prompt.

The extension may also store recent per-URL view state locally so it can restore your previous view for the same resource. This may include search text, selected JSON path, highlighted line, fold state, and whether you were viewing the original or formatted output.

HTTP Client saved requests, environments, secret variables, and privacy-sanitized replay history are stored only in chrome.storage.local. The current version migrates saved requests and environments written to sync storage by an older release back to local storage and removes the synced copy. Replay history omits request bodies, credential headers, URL credentials, and sensitive query parameters. CodePrettify does not separately encrypt saved local request or environment values, so access to your browser profile should be protected. JavaScript Playground state and Regex Playground history are also kept locally because they may contain text you entered. Custom test text in Regex Playground is different: it remains only in the active viewer session and is not written to history, settings, or extension storage.

If you choose to copy a shareable URL, the URL hash may include view state such as search text, selected path, highlighted line, fold state, and some viewer settings. That information stays in the copied link and is only shared if you choose to share the URL.

3. Application Behavior

The CodePrettify desktop application operates entirely locally on your device. It does not transmit any data to external servers and does not collect telemetry. Custom Regex Playground test text remains only in the active tab session and is not saved to application settings or Regex Playground history.

CodePrettify does not require an internet connection to perform its core functionality.

4. Third-Party Services

The extension utilizes open-source libraries such as CodeMirror 6 and js-beautify that are bundled directly within the extension. No external CDNs or third-party tracking scripts are loaded by the browser extension itself.

If you choose to open external links from the extension, such as changelog or issue-report pages, your browser connects directly to those websites under their own policies. The extension website may also load standard website assets such as hosted fonts.

If you use the HTTP Client, the API or website you select is a third-party service and receives the request directly from your browser. Review that service's policy before sending credentials or sensitive data.

5. Your Rights

CodePrettify does not maintain a server-side database of the supported page content or viewer metadata that it handles locally in your browser. If you have questions about the extension's local data handling or settings storage, you may contact us using the information below.

6. Changes to This Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

7. Contact Us

If you have any questions about this Privacy Policy, please contact us here:

Contact: CodePrettify Support
Publisher: FixQuotes