Page Push · Privacy
Your browsing data goes where you choose.
Page Push has no account system, hosted backend, analytics, advertising, or telemetry. It sends page events only when you deliberately initiate a page push or run its connection test, and only to the HTTPS endpoint saved in your local browser settings.
What a manual push can include
- Current page URL, title, and hostname
- Timestamp and favicon URL, when available
- Referring URL, when available
- Selected text, when enabled and present
What Page Push does not do
- Does not operate a cloud service.
- Does not route your browsing data through developer-operated servers.
- Does not collect analytics, telemetry, or crash reports.
- Does not automatically monitor browsing.
- Does not execute remote code.
- Does not send page events anywhere except the HTTPS endpoint you configure.
What Page Push does not capture
Page bodies, form contents, passwords, cookies, keystrokes, screenshots, and automatic browsing history are not captured.
Credentials and permissions
Your endpoint configuration and optional authorization credentials are stored locally in browser storage. Page Push requests access only to the endpoint origin you approve. It does not synchronize these settings through a Page Push service.
Retention
Page Push retains its settings and one compact last-delivery result in browser storage. It does not retain a local history of pushed pages. Your chosen endpoint controls any data it receives.
Removing data
Removing the extension clears Page Push data stored in your browser. Data previously delivered to your endpoint is governed by that endpoint and must be removed there.
Contact
Questions about Page Push or this privacy policy can be sent to support@krwill.xyz.
Effective August 5, 2026.