Privacy and data handling.

JSON processing

Your JSON and jq filter are sent over HTTPS to Cloudflare Workers and processed there. Results are returned to the caller. The application does not write submitted JSON, filters, or results to its database or application logs.

The service receives the data you submit, not access to your computer. It does not read local files, fetch external JSON URLs, execute shell commands, or connect to your accounts. Use local processing for data that must stay on your device.

Usage records and retention

For daily rate limiting, the application stores an IP address or supplied UUID, the UTC date, and a request counter in Cloudflare D1. A UUID is a quota identifier, not proof of identity or an account login.

Identifying quota records are used for the current UTC day. Expired records are converted to daily totals and removed during scheduled cleanup, which runs every five minutes, and before subsequent processing requests. A delayed or failed cleanup can delay deletion; the next successful cleanup catches up.

Daily totals, unique-client counts, and aggregate REST, MCP, and Zapier request counts are retained for approximately one year. These historical totals contain no IP addresses or UUIDs.

Hosting, logs, and backups

Cloudflare provides hosting, traffic handling, database storage, operational logs, and backups. Cloudflare can process request metadata, such as timestamps, network information, and error or security events. Removing records from the active database does not immediately remove copies in provider-managed backups or existing platform logs; those follow the provider’s retention settings.

See D1 backup documentation and Cloudflare’s privacy policy. The application’s payload-handling statement is not a claim of zero retention throughout every hosting system.

Website analytics and public monitoring

The homepage and API documentation use Google Analytics to measure website visits and interactions. The Analytics tag is not included in MCP or REST responses, this privacy page, or the status page. See how Google uses information from sites that use its services.

Public MCP monitoring runs a fixed example containing {"name":"Alice"} from GitHub Actions. Its checks and run history are public; customer payloads and usage records are not included. The status page links to that evidence.

Questions and changes

Email contact@thejqapi.com with privacy questions or requests. Share only the minimum information needed to explain the issue. Public issue reports should use sample data rather than private payloads or credentials.

Updates to this notice will be published here with an updated effective date. The hosted implementation is private. Public documentation, examples, release notes, and issue reporting are available in the documentation repository.