Page Punch Privacy Policy

About this policy

This policy covers the Page Punch Chrome extension, built by Second Bell. It describes what the extension stores, what (if anything) leaves your device, and the choices you have. The Second Bell website has its own privacy policy.

The short version: Page Punch has no backend. There is no account, no analytics, no telemetry, and no server of ours that receives anything. Your comments, screenshots, and settings stay on your device.

What Page Punch stores

When you capture a comment, Page Punch saves what you chose to capture: your comment text, the page's URL and title, any text you selected and its surrounding context, and any area screenshots you took (including your annotations). It also stores your settings, such as keyboard preferences, your per-domain disable list, and — if you add one — your OpenAI API key.

All of this lives in Chrome's local extension storage and IndexedDB on your device. Nothing is captured in the background; the extension only reads page content at the moment you create a comment.

What leaves your device

Nothing, by default. Page Punch makes no network requests of its own, with two user-initiated exceptions related to voice notes:

• Built-in voice dictation (the default). Voice notes are transcribed by Chrome's built-in speech recognition. That processing is handled by the browser itself and is governed by Google Chrome's terms and privacy policy, not by us.
• Optional OpenAI transcription. If you add your own OpenAI API key in settings, recorded audio is sent directly from your browser to OpenAI's Whisper API to be transcribed, authenticated with your key. That request goes straight to OpenAI and is governed by OpenAI's terms and privacy policy. We never see it.

If you never use the microphone, no audio is recorded and nothing leaves your device at all.

Microphone access

The microphone is used only while you are actively recording a voice note, after you grant Chrome's microphone permission. Audio is processed for transcription and is not retained after the transcript is produced.

Your OpenAI API key

An OpenAI API key is optional. If you provide one, it is stored in Chrome's local extension storage on your device and is used for exactly one thing: authenticating transcription requests sent from your browser to OpenAI. It is never sent anywhere else. You can remove it at any time in the extension's settings.

Exports

Exporting is always something you trigger. Markdown copies go to your clipboard, zip and PDF exports are generated locally and saved or printed where you choose. Once exported, that copy of your data is in your hands and outside the extension's control.

Deleting your data

You can delete individual comments or clear entire pages and sites from the side panel. Uninstalling the extension removes everything it stored — comments, screenshots, settings, and any API key — from your device.

Limited Use

Page Punch's use of information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We do not sell user data, we do not transfer it to third parties (the only transmissions are the user-initiated transcription requests described above), and we do not use it for advertising, creditworthiness, or any purpose unrelated to capturing and exporting your feedback.

Changes to this policy

If the extension's data handling ever changes, we will update this policy and the "last updated" date above before the change ships.

Contact

Questions about this policy or how Page Punch handles your data? Email hi@thesecondbell.com.