Privacy policy · Last updated 14 August 2026
JSON to Class Converter.
Turns a JSON sample into class or type definitions for TypeScript, C#, Java, Python and a dozen more targets — the conversion runs entirely inside the popup.
The short version
No account, no sign-in, no analytics, and no server of mine behind it. What this extension saves, it saves on your own computer, to remember how you like it set up.
What it stores on your device
Written with chrome.storage.local, readable only by the extension itself:
- One key, settings, holding the preferences you pick in the popup: target language, root class name, naming convention, access modifier, output format, editor font size, and the include-comments, nullable-types, auto-generate, auto-generate-on-fetch, include-imports and detect-formats toggles.
What it never collects
- The JSON you paste or fetch. It is parsed in memory and gone the moment the popup closes.
- The code it generates for you, and the URLs you fetch JSON from.
- No analytics, telemetry, tracking pixels, or advertising of any kind.
- No accounts, no sign-in, and no personally identifying information — not your name, email, IP address, or device fingerprint.
- Nothing is ever sold, rented, or shared with data brokers, advertisers, or any third party.
- No remote code. All logic ships inside the package Chrome reviewed; nothing is downloaded and executed at runtime.
Why it asks for each permission
storage- Saves the preferences above so the popup does not reset to defaults every time you open it.
activeTab- Reads the current tab's URL only when you use the fetch-from-URL feature, so it can pre-fill the address you are already looking at.
http://*/* · https://*/*optional- Requested at the moment you fetch JSON from an address, and only for that address's origin. Chrome shows you the prompt; declining simply cancels that one fetch. The extension never asks for broad access up front.
Optional permissions are requested at the moment a feature needs them — Chrome asks you first, and declining cancels that one action and nothing else.
Where your data goes
Nowhere. This extension sends nothing to any server — mine or anyone else’s.
Worth knowing
- The fetch-from-URL feature contacts exactly one server: the address you typed. That request goes straight from your browser to that server, carries no identifying data added by the extension, and its response is never stored.
- Storage uses chrome.storage.local, never chrome.storage.sync — so the data stays on the machine it was created on and is not copied to your Google account or across your devices.
- Removing the extension from Chrome deletes everything it stored. You can also clear it at any time from the extension's own controls.
What you control
- Clear the extension’s saved data from its own controls, whenever you like.
- Remove it from chrome://extensions and everything it stored is deleted with it.
- Revoke any optional permission from Chrome’s extension settings, without uninstalling.
If this ever changes
This policy is versioned alongside the extension. If a release starts storing or sending something new, this page changes in the same update and the date above moves with it. No silent revisions.
Questions, or something that looks wrong
Write to me and I’ll answer. If you find anything this policy does not describe accurately, I want to hear about it — that is a bug in the policy or in the extension, and either way it gets fixed.
Policies for my other extensions
All privacy policies