In short: the extension connects your existing Pingwire account to your browser to deliver your notifications and to send the current page to your phone. It reads only the active tab’s title and URL, and only when you ask it to. No message contents, no form-field values, and no browsing history are ever logged, stored for analytics, or sold.
Overview
The Pingwire browser extension is a client for your existing Pingwire account at pingwire.dev. It delivers your Pingwire push notifications to your browser and lets you send the current page to your phone. It is not a separate service — it talks only to the Pingwire API.
The Pingwire service, and this extension, are operated by BRANDISTRIES LLC, the data controller:
- BRANDISTRIES LLC
- 2230 Route 70 W Ste 2, Cherry Hill, NJ 08002-3338, USA
- Contact: privacy@pingwire.dev
What the extension reads
- Your Pingwire notifications and channels, by making authenticated requests to the Pingwire API on your behalf after you connect your account.
- The current tab’s title and URL — only when you explicitly click "Send this page to my phone" (or use the keyboard shortcut and confirm). This uses Chrome’s
activeTab permission, which grants access to only the one tab you act on, only at that moment. The extension never reads page content, other tabs, your browsing history, or any tab you did not explicitly act on.
What leaves your browser
- When you connect: an OAuth 2.1 (PKCE) sign-in with pingwire.dev. The extension receives an access token; your Pingwire password is never seen by the extension.
- When you send a tab: the current tab’s title and URL and your optional note are sent to Pingwire and delivered as a message to the channel you pick. This is the purpose of the feature and happens only on your explicit action.
- Nothing else is transmitted to Pingwire or to any third party. There are no analytics, no trackers, and no remotely hosted code — all extension code ships in the package.
What is stored, and where
Stored locally in your browser (chrome.storage.local), not on our servers beyond your normal Pingwire account data:
- Your Pingwire access and refresh tokens — held only by the extension’s background service worker, never exposed to web pages.
- A cache of your recent messages, your read/unread state (read state is device-local and does not sync), your chosen default channel, and your poll-interval setting.
- A local diagnostics event log of facts only — timestamps, event types, HTTP status codes, and the origin involved.
What is never logged or stored
- No message contents and no form-field values are ever written to the diagnostics log or stored for analytics.
- The URL you send is delivered to Pingwire (that is the feature) but is never written to the local diagnostics log.
- If a future optional "email alias" feature is enabled, the alias value and any form-field value are never logged, stored, or transmitted anywhere except into the field you chose to fill.
Permissions explained
- storage — save your session and settings locally.
- alarms — check for new notifications on a timer.
- notifications — show desktop notifications for new messages.
- activeTab + scripting — read only the current tab’s title and URL when you click "Send this page to my phone."
- identity — run the OAuth sign-in flow.
- Host access to https://pingwire.dev/* — talk to the Pingwire API. This is the only site the extension communicates with.
Retention
- Tokens persist until you sign out (which revokes them server-side and clears them locally) or uninstall the extension.
- The local message cache and diagnostics log are capped and roll over automatically; uninstalling removes them entirely.
- Sending a tab creates a normal Pingwire message in your account, retained under your Pingwire account’s own data retention — not by the extension.
Your control
- "Sign out everywhere" revokes your tokens on the server and clears local data.
- Uninstalling the extension removes all locally stored data.
Changes to this policy
We may update this policy as the extension evolves. Material changes will be reflected here with a new "last updated" date.
Contact
Questions about this policy or your data: privacy@pingwire.dev.
Does the extension track my browsing?
No. The extension has no analytics and no trackers, and it never reads your browsing history or other tabs. It reads the current tab’s title and URL only when you explicitly click "Send this page to my phone."
What leaves my browser when I use it?
When you connect, an OAuth sign-in with pingwire.dev (your password is never seen by the extension). When you send a tab, that tab’s title and URL plus your optional note are sent to Pingwire to deliver as a message. Nothing else is transmitted, and there is no third party.
Are my message contents or form fields ever logged?
No. The extension’s local diagnostics log records only facts — timestamps, event types, HTTP status codes, and the origin involved. Message contents, the URL you send, and any form-field values are never written to that log.
Where are my tokens stored?
Your Pingwire access and refresh tokens are stored locally in your browser (chrome.storage.local), held only by the extension’s background service worker. They are never exposed to web pages, and "Sign out everywhere" revokes them on the server and clears them locally.