Privacy Policy

1. Introduction

Welcome to ToolKnit ("we", "us", "our"). We are committed to protecting your privacy. This Privacy Policy explains what data we collect, what we don't collect, and how we handle information when you use the ToolKnit web app at toolknit.com.

This Policy applies only to the ToolKnit web app at toolknit.com and ToolKnit Desktop distributed through its official GitHub repository at github.com/ZihangDong/toolknit-desktop. It does not apply to any browser extension, store listing, mirror, or third-party service claiming to represent ToolKnit.

2. No Account Required

The web tools do not require a ToolKnit account, registration, or login. We do not ask for your name, email address, or account password to use them. This does not mean that no data is processed: the site receives technical request and analytics data, and network-assisted features send the content described below. If you email us, we receive the address and information you choose to include.

3. File Processing & Privacy

The local PDF, image, video, and audio conversion and editing tools process selected files inside your browser using technologies such as WebAssembly, Canvas, Web Audio, and PDF.js. Their conversion workflows do not upload those files to ToolKnit for processing.

AI requests have two connection modes. Browser direct is the default: keys and relevant text go directly to the configured provider. If you select ToolKnit server relay, your key, text and response pass through ToolKnit and its CDN to a fixed supported endpoint over HTTPS. The relay does not save keys or conversation content, log request/response bodies, or retry requests automatically. It uses temporary in-memory pseudonymous IP/key counters for rate limits. Ordinary CDN traffic/security metadata and provider retention policies still apply. Closing or stopping a request cannot undo processing already performed by a provider. Files and screenshot OCR are still parsed locally; only relevant text selected for AI processing is sent. API keys are not saved in browser storage; non-secret provider and connection preferences may be saved locally.

Server-backed Text to Speech sends the text and voice settings you choose to ToolKnit's speech endpoint, which forwards the synthesis request to an external speech service. Do not put sensitive information into an AI or speech request unless you are comfortable with the applicable processing. Network-assisted features are not covered by a blanket promise that all input stays on your device.

4. Local Storage

Depending on the tool, browser storage holds:

• Daily usage count —The tk_usage localStorage record tracks a shared allowance of 500 uses per day in that browser, not 500 separate uses for each tool. It resets when the local calendar date changes.
• Tool preferences —Settings like personal bests in the CPS Test, Aim Trainer scores, and similar per-tool state.
• Cached resources —The service worker uses the browser's Cache Storage for downloaded pages and assets. Some tools also cache larger runtimes or models. This is separate from localStorage and does not make every feature available offline.

Optional BMI history — BMI measurements are not saved automatically or sent as analytics events. Choosing Save stores up to 90 height/weight records in this browser. Remove individual records or all BMI records from the calculator; exported CSV files remain on your device until you delete them.

Saved color palettes — Color Picker stores only colors you choose to save, up to 100 in this browser. Images are processed locally and are not saved. Remove individual colors or clear the palette in the tool; exported CSS, JSON and PNG files remain on your device.

The usage counter and saved preferences are local records, not a ToolKnit account. You can clear site data through your browser settings; doing so can remove preferences, saved tool data, and cached resources. Information you explicitly submit to a network-assisted feature is handled as described in section 3.

5. Analytics

We use first-party visit statistics and third-party analytics to understand site traffic:

• ToolKnit visit statistics —The web tracker sends a page-load event with the page address, referrer, and tk_uid browser identifier to our server. We remove query strings from page addresses and keep only the external referrer's origin. The server uses a private key to derive daily and monthly pseudonymous identifiers for counting visits and distinct browsers across pages. Monthly identifiers change each calendar month. When a browser identifier is unavailable, a combination of IP information and user agent is used as a less reliable fallback. Recent-visit records do not store an IP address. These identifiers are not a guarantee of anonymity, and distinct browsers are not the same as distinct people. Private daily email reports contain aggregate counts and server health, not individual visitor identifiers or selected files. The tracking payload does not include selected file contents or conversion output.
• Google Analytics (gtag.js) —Measures page views and sessions under Google's Privacy Policy.
• Ahrefs Analytics —Measures page views under Ahrefs' Privacy Policy.

The public Status page exposes aggregate tool-page visits, not individual visitor records or successful-conversion counts. Separately, web hosting, CDN, and security services receive technical request information such as IP addresses and user agents; application-level hashing does not mean those systems never receive or log an IP address.

6. Third-Party CDN & Libraries

ToolKnit serves many tool libraries from its own domain and also loads some resources, such as Google Fonts, from external providers. A library name alone does not identify which host receives a request. When a resource is requested from an external provider, that provider may receive and log standard HTTP request data such as IP address and user agent, subject to its own privacy policy.

7. Cookies

ToolKnit's first-party tracker sets a cookie named tk_uid, with an expiry of up to 365 days, to provide a visitor identifier for visit counting. It is not an account or a record of your files. Third-party analytics may use their own cookies or similar technologies. You can delete or block cookies through your browser; this changes analytics identification, and clearing all site data also removes local preferences and caches.

8. Data Sharing

Third-party processing occurs for the analytics, resource delivery, AI, and speech features described above. AI content is sent to the endpoint you configure; server-backed speech requests pass through ToolKnit. Review the relevant provider's policy before sending sensitive content. A local file-conversion workflow is different from choosing a feature that makes a network request.

9. Children's Privacy

Our services are not directed to children under 13. If you believe a child has supplied personal information through a ToolKnit feature or by contacting us, please contact us so we can review the situation.

10. Your Rights

There is no ToolKnit web account to delete. You can remove cookies, local tool data, and cached resources through your browser's site-data settings. That action does not delete server-side analytics records or information already submitted to a third-party provider. Contact us about data handled by ToolKnit, and contact the relevant provider about requests sent to that provider.

If you have specific questions or concerns, contact us at info@toolknit.com.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated date. Continued use of the site after changes constitutes acceptance.

12. Contact Us

If you have any questions about this Privacy Policy, please contact us at info@toolknit.com.