TR EN

Privacy Policy

Last updated: 25 October 2026

1. Client-Side Cryptographic Privacy

All cryptographic operations (Password Generation, Hash Calculations, Base64/Hex Conversions, JWT Parsing) are performed strictly within your web browser using modern Web Crypto APIs. Your sensitive credentials and plaintexts are never logged, stored, or transmitted over the network.

2. Server-Side Diagnostic Requests

Diagnostic utilities such as DNS lookups, SSL certificate audits, and IP routing inspections query public internet routing tables and nameservers. No user identity or tracking profiles are created.

IP geolocation queries send the queried IP address to ip-api.com using its current free HTTP endpoint; responses are approximate and can be unavailable. This third-party lookup is separate from our aggregate usage counters.

3. Usage measurement

We use Google Analytics 4 to understand page visits, referral sources and deliberate tool interactions. Google Analytics uses browser identifiers and may use cookies. Our custom events contain a tool name, language and an outcome category; they do not include the text you enter, generated passwords, tokens, hashes, queried targets or webhook contents. Page URLs sent by our tag omit query strings and fragments. Advertising personalization and Google signals are disabled in our tag.

To stop this site's Analytics tag, use . This preference is stored locally. Blocking analytics does not prevent tool use.

4. API and agent counters

The server keeps daily aggregate counters by endpoint, response category and declared client category in private storage. These counters contain no IP addresses, raw user agents, request arguments or response contents. A declared AI user agent is not verified identity. Hosting access logs are separate from these product counters.

5. Webhook testing

New webhook endpoints expire after 24 hours and keep up to 50 requests, with a 64 KiB body limit per request. Requests are stored in private server storage for inspection. IP addresses are masked; common authorization headers and secret query keys are redacted, but request bodies and other fields are not automatically anonymized. Use synthetic test data only. Reading history, streaming, changing responses and clearing history require a separate management token, which this browser stores locally. Keep that token private. The receiver URL alone cannot read a new endpoint’s history. Expired new records are removed when accessed or during bounded cleanup triggered by endpoint creation; physical deletion at exactly 24 hours is not guaranteed. Legacy endpoints retain their older link-based access and have no automatic expiry; create a new endpoint to use the improved controls. You can clear request history with the Clear action.