JSONifyPro / Trust & Legal
Privacy Policy
How browser-local payload processing, support correspondence, external assets, local history, and any future advertising affect your information.
Effective
Scope & responsibility
This policy applies to JSONifyPro's developer workspace and technical guides. JSONifyPro is the responsible site operator and the contact for questions about the processing described here. Contact support@jsonifypro.com for privacy inquiries or to exercise applicable rights.
Editor payloads, ordinary website delivery information, and messages you choose to send to support are different categories of information. The client-side guarantee below concerns editor processing; it does not mean that visiting a website makes no network requests.
100% client-side payload processing
No JSON payload is ever transmitted, logged, stored, or processed on our servers.
Formatting, validation, minification, conversion, comparison, and mock generation execute in your browser. The application does not submit pasted or locally opened documents to a JSONifyPro processing endpoint. We do not use editor contents for analytics or model training.
Local history is stored on your device. Exporting writes a file or uses your clipboard. A share link contains reversible Base64 data in the URL fragment. Fetch URL contacts the endpoint you enter; that endpoint receives the request and may keep its own logs. Do not place credentials in a fetch URL or send editor payloads in support messages. See share-link risks for the difference between local execution and safe disclosure.
Information categories & purposes
| Category | Location or recipient | Purpose & retention |
|---|---|---|
| Editor documents | Browser memory and automatically saved local history | Requested tool operations; history persists until removed, replaced, or cleared by the browser. |
| Site delivery metadata | Hosting and asset-delivery providers | Deliver and protect requests; may include IP address, path, user agent, and timestamps. Provider retention varies. |
| Contact draft | Current page memory | Local validation and drafting. The form does not store a draft in localStorage or submit it to a site endpoint. |
| Sent support email | Your mail provider, our mail provider, and support handling | Respond to your request; retained only while needed for follow-up, security, or applicable legal obligations. |
| Chosen remote endpoint | The URL provider you select | Retrieve its response under that provider's policies. |
| Advertising data | No ad tags are enabled in this release | Potential future handling is described below and requires separate controls before activation. |
We do not require an account for the workspace. Do not voluntarily send sensitive personal information or production secrets. We review the need to retain support correspondence when a request closes and when follow-up or legal needs end; provider backups may follow separate deletion schedules.
Cookies, local storage & external assets
The current application does not set advertising or analytics cookies. The workspace automatically saves recent processed payloads in jsonifypro.history.v2, retaining up to 10 entries; an older fallback may use jsonifypro.localHistory.v2. Local storage is not a cookie and is not automatically sent with HTTP requests, but it persists in the browser and is accessible to scripts running in the same origin. Clearing history removes existing entries but does not disable saving when you process another payload.
The page requests Tailwind CSS from cdn.tailwindcss.com and Lucide assets from unpkg.com. Those providers receive ordinary asset-request metadata. Third-party scripts execute in the page context; extensions, compromised dependencies, or a compromised device may access data available in that context. This site does not represent browser execution as an absolute security boundary.
Clear site data through your browser to remove local storage and cookies for this origin. This can also remove preferences and other site state. The targeted history control below removes only the workspace's history keys; it does not delete downloaded files, clipboard contents, mail, browser history, or recipients' copies of share links.
Google AdSense, DoubleClick & third-party advertising
No Google AdSense or third-party advertising tag is included in the current pages. An ads.txt placeholder does not activate advertising. The disclosures below describe the conditions that apply if advertising is introduced.
If enabled, Google AdSense and participating advertising providers may use cookies, local storage, device identifiers, IP addresses, page context, and ad-interaction information to deliver advertisements, measure performance, limit repetition, and prevent fraud. Google's advertising infrastructure, historically associated with DoubleClick, can use advertising cookies to recognize browsers across participating sites where permitted.
Personalized advertising may use activity from this and other sites, subject to consent, settings, and applicable law. Non-personalized advertising is not automatically cookie-free and may still involve measurement or fraud-prevention processing. Editor contents must never be supplied as ad targeting data, event parameters, or analytics fields.
Before activation, this policy and the live consent interface must identify the actual vendors, purposes, storage technologies, and relevant retention information. Optional advertising technologies must be held back where prior consent is required. Declining optional purposes must not prevent local formatting.
Read how Google handles partner-site information and Google's cookie documentation. Manage Google ad personalization in My Ad Center; changing personalization does not necessarily remove every advertisement or all non-personalization processing.
Consent & regional advertising requirements
Where European or UK data-protection and device-storage rules require consent, consent must be informed, specific, freely given, and withdrawable. Continuing to browse is not treated as consent to optional advertising. A future advertising deployment serving the EEA, UK, or Switzerland must implement the applicable Google-certified consent-management requirements before ad requests are enabled.
A simple local preference toggle is not a substitute for that consent platform. The current page does not claim to operate an advertising CMP. If optional tracking is introduced, visitors must be able to review purposes and vendors, reject optional processing, and revisit their choices. Withdrawal affects future processing and does not retroactively invalidate processing that was lawful before withdrawal.
GDPR & other applicable privacy rights
Where applicable, you may request access, correction, erasure, restriction, or portability of personal information, and object to processing based on legitimate interests. You may withdraw consent where it is the processing basis and complain to a competent data-protection authority. These rights have legal conditions and exceptions; we do not hold a server copy of your editor history to retrieve or erase.
Support correspondence is handled to respond to your request and maintain the service, generally on the basis of legitimate interests or steps necessary to provide a requested service where applicable. Security-related handling is limited to protecting the service; legal requirements may require specific records. Optional advertising relies on consent where required. Data minimization and the purpose of each request guide what information is needed.
Email support@jsonifypro.com with the right you wish to exercise and enough information to identify relevant correspondence. We may request proportionate verification without asking for your editor payload. Under the GDPR, responses are generally due within one month, with permitted extensions explained within that period. Our support acknowledgement commitment does not replace statutory response deadlines. See the European Commission's rights guidance.
California privacy choices
Where the CCPA, as amended by the CPRA, applies, eligible California residents may request to know or access covered information, correct inaccuracies, delete information, opt out of sale or sharing for cross-context behavioral advertising, and limit qualifying uses of sensitive personal information. Exercising a protected right must not result in unlawful discrimination.
In this release, we do not sell personal information or share it for cross-context behavioral advertising. We do not use editor payloads for advertising. If future ad integrations involve sale or sharing under applicable law, they must provide an effective opt-out and honor applicable Global Privacy Control signals before activation. No optional advertising runs on the current pages, regardless of signal state.
Send requests or authorized-agent inquiries to support@jsonifypro.com. Verification and authorized-agent requirements depend on the request; opt-outs are not conditioned on creating an account. Covered access, correction, and deletion requests generally have a 45-day response period, with extensions where legally permitted. See the California Attorney General's CCPA guidance.
Privacy controls
Optional advertising and analytics: not enabled. There is no active ad-consent choice to save on this release.
Global Privacy Control status is available when JavaScript is enabled.
History removal affects this browser and origin only. Use browser site-data settings for cookies and other storage. Do Not Track and Global Privacy Control are different signals; the current implementation loads no optional trackers under either setting.
Providers, transfers & disclosure
Hosting, asset delivery, and email providers may process information in countries different from yours. Where applicable law requires international-transfer safeguards, the arrangement must use an appropriate legal mechanism, such as an adequacy decision or contractual safeguards. Contact support for information about the arrangements relevant to your request; no claim of exclusively local-country hosting is made.
We may disclose information we actually hold when necessary to comply with lawful obligations, protect rights, or investigate abuse, subject to applicable law. This does not create a server copy of editor documents. External sites and endpoints have their own policies, and we cannot delete information already sent to them on your behalf.
Children, security & policy updates
The service is intended for developer use and is not directed to children under 13. Do not knowingly send us children's personal information. If you believe such information reached support, contact us so the request can be reviewed and handled appropriately.
No website or device can promise absolute security. Review the Data Security Disclaimer, keep credentials out of shared URLs, and use an approved isolated environment for sensitive production data. Material changes to this policy or the introduction of advertising should be disclosed before the changed processing begins, with an updated effective date and consent where required.