Blip Privacy Policy
Effective date: April 9, 2026
This Privacy Policy explains how Blip handles information when you use the Blip Chrome extension. Blip is designed to record browser tab audio and microphone audio for the user who installs the extension. The extension is built to minimize data collection and keep recordings under the user's control.
Information Blip Collects
- Audio recordings: Recordings you make with the extension are stored locally on your device or inside the extension's local storage workflow.
- Usage settings: The extension stores preferences such as plan status, recording format, and local usage counters inside Chrome extension storage.
- Payment status: If you subscribe to Pro, ExtensionPay may provide payment status information so premium features can unlock inside the extension.
Information Blip Does Not Collect
- No third-party analytics or behavioral tracking.
- No advertising identifiers.
- No sale of personal information.
- No remote upload of recordings by default.
How Audio Data Is Handled
Blip requests microphone or tab-audio access only when you choose to record. The extension uses that permission to capture audio locally and create a recording file for you. By default, those recordings are not transmitted to any Blip server.
Optional Transcription Features
If Blip offers an optional transcription feature, the audio you choose to transcribe may be sent to a third-party transcription provider such as Deepgram, Groq Whisper, or another provider selected by the product operator. That transmission happens only after you explicitly invoke the transcription action. The privacy practices for that processing are governed by the applicable third-party provider.
Optional AI Analysis Features
When you configure an AI analysis key, transcript text is sent to the AI provider (Cerebras) for analysis. This only happens when you have explicitly configured a key and recorded audio. No audio data is sent to Cerebras - only the text transcript. The AI provider privacy policy governs that processing.
Payments
Blip uses ExtensionPay for subscription and payment status handling. Payment processing is handled by ExtensionPay and its payment partners, not by Blip directly. Blip receives only the limited account status data needed to determine whether Pro features should be available.
Data Storage and Retention
- Recordings remain in local storage until you delete them.
- Usage settings remain in local extension storage until you clear them or uninstall the extension.
- No central server retention policy applies to recordings because recordings are not stored on a product server by default.
Data Sharing
Blip does not sell or rent user data. Information is shared only in the limited situations required to operate optional services you request, such as payment verification or transcription processing.
Security
Blip is designed to keep recordings local whenever possible. No system can promise absolute security, but the product architecture aims to reduce risk by avoiding unnecessary remote storage and analytics tooling.
Your Choices
- You can stop using the extension at any time.
- You can delete recordings from the extension interface or local storage workflow.
- You can uninstall the extension through Chrome.
- You can decline microphone access, although recording features will not work without it.
Changes to This Policy
This Privacy Policy may be updated if Blip changes its features or data practices. The latest version should always be published at the public privacy policy URL linked in the Chrome Web Store listing.
Contact
For privacy questions about Blip, contact mjiaminwork@gmail.com.