Privacy Policy
This policy covers the Chrome extensions published by Legendary Solutions LLC - Pretty Payload and Window Namer - and the prettypayload.com website. Where a section applies to only one extension, it says so.
Summary
Pretty Payload is a Chrome extension that inspects JSON entirely on your device. We do not collect, transmit, sell, or share the content you inspect. The only personal information involved in the product is the email address you provide to our payment providers when starting a free trial or subscribing.
What the extension does with your data (Pretty Payload)
All JSON processing (viewing, formatting, repairing, searching) happens locally in your browser. Inspected content - payloads, webpage text, clipboard text - is not uploaded for processing or stored remotely by Pretty Payload. It is not shared with us or anyone else for inspection.
Your settings and an optional history of your last five documents are stored locally in your browser using Chrome's extension storage. History can be cleared or turned off at any time in the extension's settings, and all locally stored data is removed when you uninstall the extension.
Billing information (Pretty Payload only)
Free trials and subscriptions are managed by our payment providers, ExtensionPay and Stripe. When you start a trial or subscribe, your email address and payment details are collected and processed by those providers to manage your license. We do not sell or share this information, and we never see your full payment card details. See the ExtensionPay and Stripe privacy policies for how they handle data.
The extension contacts extensionpay.com only to check your license and trial status. No inspected content is ever included in those requests.
This website
As of this policy update, the production website build does not load Google Tag Manager, Google Analytics, advertising pixels, or similar marketing tags. There is no site analytics container configured in the current deploy. If that changes, this section will be updated to describe the tools in use. The Chrome extension contains no analytics, tracking, or advertising of any kind, and the website cannot access anything you inspect in the extension.
JSON pasted into the free web tool at /try/ is processed locally in your browser. Inspected payloads are not uploaded for processing. The page may use ordinary browser session storage so you can reload a pasted payload in the same tab; it is not a remote store of your JSON. Prefer the extension when you want the clipboard and page-scanning workflow with local history controls.
Data we do not collect
We do not collect personally identifiable information beyond the billing email described above, and we do not collect health information, financial or payment information (beyond what our payment providers process), authentication information, personal communications, location data, web history, user activity, or website content.
Window Namer
Window Namer prepends a name you choose to the title of the tab you are viewing, so external time-tracking software can attribute browser activity to the correct client. It runs entirely on your device.
What it stores. One value: the profile name you type. It is saved in Chrome's local extension storage on your own machine and is never transmitted anywhere. Clearing the name in the extension popup deletes it.
What it accesses. Window Namer runs on every site you visit, because the tab title has to be prefixed wherever you happen to be working. On each page it does exactly one thing: read the page's current title and write a new title with your chosen name in front of it. It does not read, collect, store, or transmit page content, form input, credentials, cookies, browsing history, or the addresses of the sites you visit.
Network activity. None. Window Namer contacts no servers - ours or anyone else's. It contains no analytics, no license check, and no telemetry. The only network activity associated with it is Chrome's own extension update mechanism, which is operated by Google, not by us.
Billing. Window Namer is free. The billing and payment-processor section of this policy applies only to Pretty Payload.
Changes to this policy
Window Namer was added to this policy on August 30, 2026.
On September 15, 2026, the website analytics paragraph was aligned with the current production build (no GTM/ad pixels configured) and the free web-tool wording was clarified.
If this policy changes, the updated version will be posted at this address with a new effective date.
Contact
Questions about this policy: [email protected]