How PocketKit handles local files, network requests, usage statistics and community content.
1. Data we process
We may process basic visit data, tool slugs, submitted community content and parameters required for networked queries. PocketKit does not require accounts or intentionally collect names, addresses or payment details.
2. Browser-local file processing
Core PDF, image, text, JSON and cryptographic tools generally process input in your browser using JavaScript, WebAssembly, Canvas or Web Crypto and do not upload selected files, text or keys to the PocketKit API.
3. Networked tools
Exchange rates, exit-IP checks, DNS, email checks and download parsing require network access. Parameters may go to the PocketKit API, Cloudflare or an identified service; do not submit unrelated sensitive information.
4. Usage statistics, community and abuse prevention
Tool-use counts send only a tool slug, not tool input. Community comments, names, timestamps and votes are stored in Cloudflare D1; rate limiting and vote deduplication use digests rather than raw IP addresses.
5. Local storage, analytics and advertising
LocalStorage may store theme, language, bookmarks and fallback data. Enabled analytics or advertising may process cookies, IP addresses, device data and web beacons under their policies. PocketKit does not sell personal data.
6. Retention and security
Local data can be removed by clearing site data. Community content and abuse-prevention digests remain until deletion or database maintenance. We use access controls, validation and rate limits, but no internet service can promise absolute security.
7. Your choices and contact
You may disable cookies, clear local storage or avoid networked features. For privacy requests, community-content action or security reports, email us through the contact page with the relevant URL.