Privacy, in plain English.
PageSift is designed to process web content locally in your browser. We do not operate a capture server, require a PageSift account, or include analytics or advertising trackers in the extension.
What PageSift processes
When you ask PageSift to capture a page, selection, element, table, tab group, or routine, the extension reads rendered content from the pages you selected. This can include sensitive information if you use it on an authenticated account page.
Where data is stored
Preferences, saved routines, optional destination credentials, and the most recent routine runs are stored in Chrome's local extension storage on your device. Routine history is capped. Uninstalling the extension removes its local extension storage according to Chrome's behaviour.
When data leaves the browser
Ordinary capture, structured-data detection, token estimation, Stone compression, Markdown/CSV export, and local routine history do not send page content to PageSift or any third party.
Data leaves the browser only when you explicitly copy or download it, or configure a routine destination such as a webhook or OpenAI-compatible endpoint. In that case, the destination receives the routine bundle under its own privacy terms. PageSift does not proxy that request.
Permissions
- activeTab and scripting: read the current page only after you invoke PageSift.
- storage: save local preferences, routines and bounded history.
- clipboardWrite: perform one-click copy.
- alarms: wake scheduled routines while Chrome is available.
- Optional tabs and website access: requested only for tab bundles or the exact origins configured in routines.
Automation safety
Routines are read-only. PageSift does not submit forms, make purchases, initiate payments, place trades, or click transactional controls. Page content is treated as untrusted data and cannot reconfigure a routine.
Retention and deletion
You can delete routines from the Routines dashboard. Routine history keeps the latest 20 runs locally. You can remove all PageSift data by uninstalling the extension or clearing its extension storage in Chrome.
Changes
Material changes to this policy will be reflected by updating the effective date and the policy packaged with the release website.