Privacy Policy
How The Tool Room guarantees your privacy through local, in-browser processing with zero remote uploads, zero retention, and zero account tracking.
The Tool Room is engineered with privacy and security at its core. Your PDF documents, images, and texts are processed 100% locally in your browser with zero server uploads. For speech-to-text tools, audio tracks are decoded in your browser memory and transcribed via OpenAI Whisper AI with zero data retention, no account tracking, and no AI model training on your recordings.
Document and image files are processed entirely in your computer's RAM. Audio transcription operates with zero retention and no persistent cloud storage.
No registration, email addresses, credit cards, or tracking cookies. Use all tools completely anonymously.
Transcribed with OpenAI Whisper AI. Your speech recordings are never retained, logged, or used to train AI models.
Optional Google Drive export communicates directly from your browser to Google API with zero server intermediaries.
1 Core Philosophy: Client-Side Computing
Traditional cloud web applications operate by receiving user files on remote server clusters, processing the media on server infrastructure, and returning an output. This model inherently exposes confidential speech, proprietary documents, and private photos to third-party interception, breach, or unauthorized secondary use.
The Tool Room operates on a privacy-first paradigm: In-Browser Execution & Zero Data Retention. PDF merging, page extraction, image compression, and format conversions execute 100% client-side in your local browser sandbox. For audio and video transcription, the browser extracts and resamples audio locally before transcribing with OpenAI Whisper AI with no accounts and no data retention.
2 Information We Never Collect or Process
Because of our client-side architecture, The Tool Room has neither the capability nor the desire to collect the following categories of information:
- Audio and Video Content: Audio decoding occurs in local browser memory, and transcription requests are processed with zero retention and no permanent server storage.
- Document and Image Contents: PDF pages, scanned files, photographs, graphic assets, and text documents are decoded locally.
- Transcripts and Generated Text: Converted text, timestamped subtitles (SRT, VTT), JSON exports, and cleaned URLs are assembled in browser memory and written directly to your local downloads folder.
- User Profiles & Personal Identifiers: We do not ask for, collect, or store names, email addresses, phone numbers, usernames, or passwords.
- Payment Information: The Tool Room is 100% free; we collect no credit card numbers, billing addresses, or financial data.
3 Local Browser Storage (localStorage & IndexedDB)
To improve your user experience across browser sessions, The Tool Room uses standard browser storage mechanisms exclusively on your device:
| Storage Key / Technology | Purpose | Where Stored |
|---|---|---|
theme (localStorage) |
Remembers your preference for Light or Dark theme across visits. | Local Browser |
app_language (localStorage) |
Preserves your selected transcription language preference. | Local Browser |
custom_google_client_id (localStorage) |
Saves your user-provided Google OAuth Client ID for Google Drive export. | Local Browser |
onnx-models (IndexedDB/Cache) |
Caches Whisper AI model weights locally so repeat visits do not re-download weights. | Local Browser |
You can clear this data at any time by clearing your browser cache and cookies, or resetting site data through your browser settings.
4 Optional Google Drive Integration
The Tool Room provides an optional convenience feature enabling you to export your completed transcripts directly to your Google Drive account. Here is exactly how this integration handles privacy:
- Direct Client-to-Google Communication: Authentication uses Google Identity Services (GIS). All authorization dialogs and token exchanges occur directly between your web browser and Google servers (
accounts.google.com). - Zero Intermediary Servers: The Tool Room maintains no server-side backend or proxy. Your Google OAuth access token is stored temporarily in your browser session memory and is never transmitted to, viewed by, or saved by The Tool Room.
- Scoped Permissions: The application only requests access to create and upload specific transcript files that you explicitly choose to export. It does not inspect, read, or modify your existing Google Drive files.
5 Artificial Intelligence & Speech Recognition
Our transcription tools utilize the state-of-the-art Whisper model. When you begin transcribing:
- Your browser extracts and normalizes the vocal track into a lightweight 16 kHz audio buffer.
- Speech recognition is performed via Whisper AI without requiring user account registration or API keys.
- Zero Telemetry or Model Retraining: User audio inputs and generated transcripts are never used for model training, reinforcement learning (RLHF), or data harvesting, and files are not retained after transcription.
6 Third-Party Content Delivery & Server Logs
When you visit the website, your browser requests static assets (HTML, CSS, JavaScript, WebAssembly binaries, and web fonts). Static hosting infrastructure automatically collects standard technical connection logs (such as IP address, browser user-agent, operating system, and request timestamp) solely for network security, DDoS protection, and server health. These technical logs contain no file contents or personal identifiers and are rotated according to standard industry practices.
7 International Privacy Compliance (GDPR, CCPA/CPRA, CalOPPA)
Because The Tool Room does not collect, sell, lease, or monetize personal information, our data practices exceed international privacy requirements:
- European Union GDPR: We collect zero personal data, meaning no personal data processing, profiling, or cross-border data transfer occurs on our systems.
- California Consumer Privacy Act (CCPA / CPRA): We do not sell or share personal information. We do not track users across third-party websites.
- No User Data to Disclose or Delete: Because we possess no database of user identities or files, data subject access requests (DSAR) cannot yield user records since none exist.
8 Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect improvements in client-side technology or newly added tools. Any updates will be published directly on this page with a revised "Last Updated" timestamp. Continued use of our tools following any revisions constitutes your acknowledgment of the updated policy.
9 Contact & Responsible Disclosure
If you have questions, feedback, or security inquiries regarding our client-side privacy architecture, you can reach out via GitHub or through the project repository.
Frequently Asked Questions
Direct answers about client-side privacy, file security, ownership, and operating terms.