PageKeeper Privacy Policy

PAGEKEEPER PRIVACY POLICY

Last updated: 22 August 2026

1. Overview

PageKeeper is a Chrome extension that helps keep user-selected tabs active and reduces interruptions caused by page inactivity, pausing and automatic tab discarding.

PageKeeper handles a limited amount of information locally to provide this functionality. Selected preferences can also be synchronised through the user’s Chrome account if the user explicitly enables Chrome sync.

No user data is sent to PageKeeper’s developer, sold, used for advertising or shared with unrelated third parties.

2. Information handled by PageKeeper

When a user explicitly enables PageKeeper on a tab, the extension temporarily handles:

• The website origin, such as https://example.com
• The title of the protected tab
• Chrome’s internal identifier for the tab
• The protection methods and timing selected by the user
• The selected automatic stopping time
• Operational information such as pulse counts, method status, warnings, errors and scheduled recovery attempts

The website origin and tab title fall within the Chrome Web Store’s web-history data category.

PageKeeper handles this information only for tabs on which the user explicitly enables protection or websites for which the user creates an automatic protection rule. It does not access or create a record of the user’s complete browsing history.

PageKeeper may also store:

• Language, theme and interface preferences
• Default protection settings
• Named protection profiles
• Automatic-repair and activity-log preferences
• Optional notification choices
• Optional automatic website rules
• A recent local activity history containing event types, times and limited tab title or website-origin information

3. How this information is used

The information is used solely to:

• Apply the selected protection methods to the correct tab
• Keep every protected tab’s settings independent
• Display protected tabs in the PageKeeper dashboard
• Show operational status and diagnostics
• Stop temporary protection when its selected duration expires
• Restore protection after Chrome suspends the extension’s background service worker
• Retry compatible protection after temporary failures
• Apply user-created profiles and automatic website rules
• Display optional failure or expiry notifications
• Synchronise selected preferences when the user enables Chrome sync

This information is not used for profiling, advertising, analytics or any unrelated purpose.

4. Session storage and retention

PageKeeper stores temporary protected-tab state using Chrome’s extension session storage on the user’s device.

This temporary information includes the protected tab’s identifier, title, website origin, selected protection settings and operational diagnostics.

Closing a protected tab removes the temporary information associated with that tab. Session information is also cleared when Chrome restarts or when the extension is disabled, reloaded, updated or removed.

Temporary notification cooldown information may also be stored in session storage to prevent repeated notifications from being displayed too frequently.

5. Local preferences and activity history

PageKeeper stores language, theme, interface mode, default settings, named profiles, automatic-repair settings, notification choices, website rules and activity-log preferences locally on the user’s device.

If activity logging is enabled, PageKeeper keeps a maximum of 200 recent activity entries. These entries contain an event type, time and limited tab title or website-origin information where relevant. Users can clear the activity history from the Protected Tabs dashboard.

Local preferences and activity history remain after Chrome restarts. They remain stored until the user changes or removes them or uninstalls PageKeeper.

6. Optional Chrome sync

Chrome sync is disabled by default.

If the user enables preference sync, PageKeeper uses Chrome’s synchronised extension storage for:

• Language
• Theme
• Interface mode
• Default protection settings
• Named profiles
• Automatic-repair preferences
• Activity-log preferences

Profiles are stored as separate synchronised items to remain within Chrome’s storage limits.

The following information is never synchronised:

• Currently protected tabs
• Protected-tab diagnostics
• Website rules
• Granted website permissions
• Activity-history entries
• Notification permission and notification choices

The sync on/off choice remains local to each device. Turning sync off on one device does not delete the shared preferences used by other devices.

Google handles synchronised data under the user’s Chrome account and applicable Google privacy terms. PageKeeper’s developer cannot access the user’s Chrome account or synchronised PageKeeper information.

7. Optional website rules and site access

Users can optionally create an “Always protect this website” rule.

When creating a rule, PageKeeper requests access only to the exact HTTP or HTTPS website selected by the user. This access is used solely to recognise that website and automatically apply the protection profile chosen by the user.

PageKeeper does not request access to every website at installation.

Website rules and their granted site permissions remain local to the device and are not included in Chrome sync or exported backup files.

Removing a website rule also asks Chrome to remove PageKeeper’s permission for that website. If a required permission is removed through Chrome, PageKeeper disables or removes the affected rule.

8. Optional same-site HTTPS request

If the user explicitly enables the HTTPS server keep-alive method, PageKeeper sends a HEAD request to the same website already open in the protected tab.

Applicable authentication cookies belonging to that website may be included automatically by Chrome. PageKeeper does not read, store or receive the contents of those cookies.

The request is sent only to the website the user already has open. It is not sent to PageKeeper’s developer or an unrelated third party.

PageKeeper does not upload page content through this request and does not use a developer-controlled server.

9. Optional notifications and right-click controls

Notification permission is requested only when the user enables failure or protection-expiry alerts.

A notification may contain the protected tab’s title or website origin and a local description of its protection status. Notifications are generated locally through Chrome and are not sent through a PageKeeper server.

If the user disables both notification options, PageKeeper asks Chrome to remove the optional notification permission.

PageKeeper’s right-click controls act only on the tab where the user invokes them. These controls can start, pulse or stop protection or apply a saved profile.

10. Activity and website content

PageKeeper may generate a synthetic mouse-movement event as an activity pulse. It does not monitor, record or collect the user’s actual mouse movements, clicks, scrolling, form entries or keystrokes.

PageKeeper does not collect website text, images, videos, messages, form contents, passwords, payment details or other page content.

PageKeeper may temporarily use the page’s title and website origin to identify protected tabs, display status information and apply user-created website rules.

11. Import and export

PageKeeper can export selected preferences to a JSON backup file.

An exported backup may include:

• Language, theme and interface preferences
• Default protection settings
• Named profiles
• Automatic-repair and activity-log preferences
• Notification choices

Exported backups do not include:

• Protected-tab state or diagnostics
• Activity-history entries
• Website rules
• Granted website permissions
• Browsing history or page content

Import reads only a backup file explicitly selected by the user. The file is validated and processed locally.

12. Analytics, advertising and tracking

PageKeeper contains:

• No analytics
• No telemetry
• No advertising
• No tracking technology
• No user accounts
• No remote code
• No developer-controlled data-collection server

The developer cannot view users’ protected tabs, browsing information, profiles, website rules, settings, activity history or diagnostics.

13. Data sharing and sale

PageKeeper’s developer does not sell, rent or share user data.

Information handled by the extension is used only to provide its disclosed, user-facing tab-protection functionality.

The only optional external transmissions are:

• Selected preferences sent through Chrome’s synchronised extension storage when the user enables Chrome sync
• A same-site HTTPS HEAD request sent to the website already open when the user enables the server keep-alive method

Information is not transferred for advertising, profiling, creditworthiness, lending or other unrelated purposes.

14. User control

PageKeeper is off by default.

Users choose which tabs to protect, which protection methods to enable, whether to enable Chrome sync, whether to receive notifications and whether to create automatic website rules.

Protection can be stopped at any time from the extension popup, right-click menu or Protected Tabs dashboard. Closing a tab removes its temporary protected-tab information.

Users can:

• Stop protection on individual tabs
• Stop protection across all tabs
• Delete saved profiles
• Remove website rules and their permissions
• Disable notifications
• Clear the local activity history
• Export or import selected preferences
• Disable Chrome sync
• Remove PageKeeper’s local data by uninstalling the extension

Disabling Chrome sync on one device does not automatically delete synchronised preferences used by other devices. Chrome and Google manage the retention of synchronised extension data under the user’s Chrome account and Chrome settings.

15. Chrome Web Store Limited Use compliance

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

PageKeeper uses information obtained through Chrome APIs only to provide, maintain and secure its disclosed, user-facing tab-protection functionality.

16. Changes to this policy

This policy may be updated if PageKeeper’s functionality or data practices change.

Any updated version will be published on this page with a revised “Last updated” date.

17. Contact

For questions about this privacy policy or PageKeeper’s data practices, please use the developer contact information or support link shown on PageKeeper’s Chrome Web Store listing.