Privacy Policy

Last updated: September 16, 2026

Core Privacy Commitment WisperNotes is designed with an on-device, privacy-first architecture. All audio recordings, speech transcription (Whisper), and text polishing models execute directly in your web browser. Your recordings and notes never touch our servers because we do not operate any backend servers.

1. Information We Collect & Usage Analytics

Your Notes and Audio (100% On-Device): WisperNotes does not collect, transmit, or store your personal notes, transcriptions, audio recordings, or AI model inputs/outputs on any remote server. All your notes, folders, audio clips, and configurations remain strictly on your physical device within your browser's private IndexedDB storage.

Anonymous Analytics for Improvements: To evaluate application reliability, feature performance, model load times, and diagnostic errors across diverse hardware, WisperNotes includes Google Analytics (using the Google tag). This telemetry collects aggregated, anonymous usage events (such as page views, user interface actions, session diagnostics, and errors). We do not collect or transmit any personally identifiable information (PII), note text, audio data, or sensitive user inputs.

Offline Resilient Queueing: When using WisperNotes without an internet connection, analytics events are temporarily cached in your browser's local storage using a Service Worker Background Sync queue (via workbox-google-analytics). Once your device reconnects to the network, these pending diagnostic hits are replayed to help us understand and improve offline usability.

2. Microphone and Display Audio Access

WisperNotes requests access to your microphone and, optionally, your display audio (in meeting recording mode) solely to generate local audio waveforms and pass 16kHz mono audio streams to the in-browser Whisper engine.

Audio buffers are captured in volatile memory (RAM) and saved into local IndexedDB.
Audio is never streamed, relayed, or uploaded to any third-party cloud service without your explicit manual trigger.

3. In-Browser AI Models

Whisper transcription and WebLLM language models run via Web Workers and WebAssembly/WebGPU inside your browser session. Model weights downloaded from Hugging Face repositories are cached locally via the browser Cache API or IndexedDB so subsequent launches operate completely offline.

4. Google Drive Sync Integration

WisperNotes offers an optional Google Drive synchronization feature for users who wish to back up their data. If you choose to connect your Google account:

Restricted Scope: We request only the https://www.googleapis.com/auth/drive.file scope. This grants WisperNotes permission only to view, create, and edit files and folders specifically created by the WisperNotes application. WisperNotes cannot see, access, or edit any other existing files, photos, or documents in your Google Drive.
Visible Folder: All synced files are placed in a user-visible folder titled WisperNotes/ in your Google Drive, containing database.json, formatted Markdown notes, and audio WAV recordings.
Client-to-Google Communication: Direct network calls are made strictly between your client browser and Google APIs using your personal OAuth token. No intermediate proxy or relay server is involved.
Revocation: You can disconnect and revoke token access at any time directly through the WisperNotes UI or via your Google Account Permissions console.

5. Data Retention and Deletion

Because your data resides entirely in your local browser storage, deleting a note or clearing your browser site data immediately and permanently removes that data from your device. If you use Google Drive sync, you can freely inspect, modify, or delete the WisperNotes/ folder directly within your Google Drive account.

6. Contact & Updates

If you have questions regarding this Privacy Policy or the security of WisperNotes, please visit our open-source project repository.