Privacy policy

Version 2026-10-11

In short

  • Your JSON and queries stay in your browser.
  • Nothing is stored about you until you choose a setting.
  • We never sell your data. There are no ad networks: the ads are our own.

1. What this policy covers

The website jsonquery.dev: the query playground, the formatter, merge, diff, patch and validate pages, and the lessons. The site has no accounts and no sign-in, and it saves nothing of yours on its server. The jsonquery desktop app is a separate program with a privacy policy of its own.

2. Your JSON stays in your browser

What you type, paste or open in the tools is worked on in your browser, by the program that came with the page. It is not sent to us: we cannot see it, and we do not keep it.

Please still keep secrets out. Do not paste passwords, keys and tokens, payment or health data, other people’s personal data that you have no right to put here, or anything else that is secret or regulated: use made-up or anonymised data instead. If you make a share link, the page first looks for the common shapes of secrets and tells you, but that check is a help, not a guarantee, and anyone who gets the link can read what it holds.

3. What we collect, and why

What our server sees

Nothing is stored about you, and no cookie is set. The pages ask the site’s server for its own files, and for /site.json (the site’s public settings: a notice if there is one, and the ads that are running). To run the site and to see that it works, the server keeps:

  • counters: how many requests came for each kind of page, and how many failed;
  • an estimate of how many different visitors came each day. It is made from a scrambled form of the network address and the browser, with a key that exists for that day only; the scrambled values stay in the server’s memory, never on a disk, and are emptied at midnight, when only their number is written down;
  • a short log of errors and of calls to the site’s own API, which names the route and the kind of answer: no network address, no query, no body, no cookie.

None of it says who a visitor is. The basis is our interest in running the site and seeing that it works (Art. 6(1)(f) GDPR).

If you write to us

The contact form sends what you write, the topic you chose and, if you give one, your email address, to our mailbox as one email. The site itself keeps nothing of it: it is in no database, file or log of the server. Our mail provider carries the message to us. Your address is used only to answer you. We keep a conversation until the matter is closed, and delete it at the latest 12 months after the last message, unless the law makes us keep it longer. The basis is our interest in answering (Art. 6(1)(f)), or, when you ask about your own data or an agreement with us, taking a step you asked for (Art. 6(1)(b)). To keep the form from being used to send spam, the messages from one network address are counted for an hour, in the server’s memory only, and then forgotten.

4. Cookies and storage in your browser

No cookie is set. What the site keeps in your browser is below.

NameWhat it is forHow longNeeds your consent?
jq.theme, jq.suggest, jq.panel, jq.view (local storage)Your theme, whether suggestions pop up, which panels you opened, how the panes are set. Only once you choose them.Until you clear themNo: settings you asked for

5. How long we keep it

  • The daily counters: numbers in a table that describe nobody. Kept: 25 months.
  • The server’s own log: The route and the kind of answer for each request to the API, and errors (no address, no query, no body, no cookie). Kept: 14 days.
  • Our mailbox, for what you send through the contact form: Your message, the topic, and the address you gave for an answer if you gave one (the server itself keeps nothing of it). Kept: Until the matter is closed, at most 12 months after the last message.
  • Your browser’s storage: Your theme, panels and layout choices, only after you make them. Kept: Until you clear them.

6. Your rights, and where to use them

You have the rights the GDPR gives you: to know what we hold about you, to have it corrected or deleted, to restrict or object to its use, and to receive it in a usable form. The site holds nothing about a visitor that it could look up: we cannot tell who a visitor is, and we do not try to find out. What there can be is a conversation that you began through the contact form.

  • See, correct or delete a message you sent, object, restrict, or ask something else: use the contact form (choose “My data”) or write to [email protected]. We answer within one month.

No decision about you is made by a machine alone. If you are not satisfied, write to us first and we will try to put it right. You may also complain to the data protection authority where you live or work.

7. Children

The site is not directed at children.

The small box marked Ad in the side panel is the site’s own: a few words, a picture that is a file of this site, and a link that goes through the site’s own address, which counts the click and sets no cookie. There is no ad network, and no one else’s code runs for it.

9. Changes to this policy

If we change how we handle your information, this page changes first, and the version at the top with it. The versions so far:

  • 2026-10-11: The first version for a site without accounts: nothing of yours is saved on the server. It covers what is left: that your JSON stays in your browser, what the server counts and logs, the contact form, what your browser keeps, for how long, and your rights.

10. How to reach us

Questions about your data, and requests to use your rights (choose “My data” in the form):

Both are private; please use them rather than a public issue tracker. We answer within one month.

About jsonquery

Query, format and learn JSON with jq, JSONPath, JMESPath and JSON Pointer. It is the engine of the desktop app, run in your browser.

Engine
The desktop app’s, compiled to WebAssembly
Licence
MIT (the engine and the app)
Source
GitHub
Contact
The contact form (private)
Public issues
GitHub
Legal
Privacy policy

Known limitations: a file over 10 MB opens read-only and one over 512 MB does not open here; the desktop app has no such limit.