Last updated: 2026-10-31
The site has no support phone line or email address; all communication goes through GitHub Issues so that it stays publicly traceable and searchable.
Before posting, make sure the content contains no sensitive information; for privacy or security matters, read the notes below first.
GitHub Issues
Feature suggestions, bug reports and usage questions can all be submitted as GitHub Issues.
Please state your environment (browser and version), the reproduction steps and the expected result so that the problem can be located.
- Describe one problem per issue
- Include the smallest reproducible sample after removing sensitive values
Privacy and Data Requests
To learn which visit-related information is processed, or to request deletion of statistics, open a GitHub Issue.
Drafts and history kept in browser local storage can be cleared by you directly on the page or in browser settings, without contacting us.
- State the type of request and the pages involved
- We will verify the request and act according to the applicable rules
Reporting Security Issues
If you find a problem that may affect the security of the site or its users, report it through GitHub Issues and avoid describing directly exploitable details.
We will assess and fix the report as soon as possible; please do not publish full exploitation steps before a fix is available.
- Describe the impact and the conditions needed to reproduce
- Withhold complete exploitation steps until the issue is fixed
Corrections and Republishing
If an article, tool description or page text is inaccurate or incomplete, point out the exact location and the correct wording in an issue.
Permission is required before republishing or quoting site content, and the source and link must be attributed.
- Include the page link and the original passage when reporting a correction
- Explain the purpose, channel and scope in a republishing request
Business Enquiries
Advertising, sponsorship and co-branded content proposals can be described in a GitHub Issue, and we will reply after evaluation.
Please outline the form of cooperation, objectives and timeline in the first message.
- We do not accept cooperation that requires altering the neutrality of the tools
- Commercial use of user JSON content is out of scope
Notes on Public Issues
GitHub Issues are publicly visible, so anything posted there may be retained by search engines and third parties.
Do not paste real keys, tokens, identity numbers, phone numbers, addresses or other sensitive JSON data into a public issue.
- Replace sample data with fictitious values
- Use placeholders to describe field structure when necessary
- Revoke and rotate any leaked key on the relevant platform immediately