Browser-local tools
Inputs and outputs for Base64, JWT, Kubernetes Secret, URL, timestamp, cron, hash, and other marked local tools are processed in browser memory. They are not sent to ParseNest or included in analytics events.
Named tasks retain input and supported options in browser storage only when you click Save. Optional local history can also retain input and results when enabled. Cross-tool transfers use temporary session storage. These records are not synchronized across devices; deleting a saved task or clearing site data removes it.
Server-side tools
Tools explicitly marked as server-side transmit the submitted configuration for processing. Temporary workspaces are deleted after the request. Request bodies are not written to application logs.
Trusted certificate requests
For the trusted SSL tool, the private key is generated in your browser and is not sent to ParseNest. The public CSR, requested DNS names, and temporary ACME order state are processed by ParseNest and Let's Encrypt to validate control and issue the certificate. Issued certificates are public information and may be submitted to public Certificate Transparency logs. Temporary order state expires automatically.
Temporary webhook inboxes
A webhook inbox retains request methods, query values, selected headers, source addresses, content types, and bodies in the running server's memory for up to 30 minutes. Common credential headers are redacted, inbox data is not written to SQLite or application logs, and a restart may remove it earlier. Use test data only.
Temporary Mock APIs and direct GraphQL requests
Mock response configuration and the creator IP used for rate limits remain in server memory for at most 30 minutes. Anyone with the generated URL can retrieve the configured response. Request bodies are not retained, and restarting the service clears endpoints. Use test data only.
GraphQL requests, variables and headers go directly from your browser to the endpoint you choose, without a ParseNest proxy. They are not automatically saved; the target service applies its own data policy.
Service data
We process basic request metadata, error counts, performance information, and coarse tool-action totals to operate and improve the service. Usage aggregates contain only the UTC date, tool name, page language, a fixed source category (such as Bing, another website, or direct), action, and count. They do not contain search queries, referring URLs, tool inputs or outputs, IP addresses, or visitor identifiers. A source category and expiry time may be held in this tab’s session storage to retain attribution across internal navigation for up to 30 minutes of inactivity. Account and billing data will be described before those features launch.
Cookies and advertising
Essential cookies may support security and sessions. If advertising or optional analytics is enabled, consent controls will be provided where required.
Contact
Questions or deletion requests can be sent through the contact page.