push.fwd

Privacy Policy

Last updated: May 2026

No data collection

push.fwd does not collect, transmit, or store any personal data on external servers. The extension and companion server are designed to keep all data entirely within your own infrastructure.

What the extension reads

The Chrome extension reads page content solely to detect generation completion events on sites you have explicitly configured. No browsing history, page content, or personal information is sent to any third party — only to your own self-hosted push.fwd server.

Your push server

All push notification delivery runs through a Node.js server you host yourself. Neither the push.fwd project, Anthropic, nor the Chrome Web Store have access to your notifications, device subscriptions, or any data that passes through your server.

Local storage only

The extension stores only your server URL, saved locally in chrome.storage.sync. This syncs across your Chrome profile via Google's infrastructure and is not accessible to push.fwd.

VAPID keys

Push subscription endpoints and VAPID keys are stored in data/subscriptions.json on your own server. This file is gitignored and never leaves your machine.


Questions or concerns: hello@framedepartment.co