Pulse Reload
Pulse Reload
Privacy center
Local-first by design
Privacy policy
This policy explains how the Pulse Reload Chrome extension accesses and uses information while providing automatic reload schedules, page-change triggers, element watching, mass tab controls, and on-page countdowns.
Effective: August 13, 2026Extension version: 1.3.7No accounts · No analytics · No ads
On this page
Plain-language summary
Scope
Information handled
How information is used
Chrome permissions
Storage and retention
Sharing and transfers
Security
Your controls
Children
International use
Policy changes
Contact
Pulse Reload does not collect or sell your personal information. It has no developer-operated server, user account system, analytics service, advertising network, or tracking SDK. Reload rules and countdown preferences are stored locally by Chrome on your device.
The extension can read limited page content when you explicitly configure a text, selector, or element-change rule. That processing happens inside the affected browser tab. Pulse Reload does not send the page content, browsing history, selectors, or tab list to the developer or to an external service.
This policy applies to the Pulse Reload Chrome extension and its built-in popup, settings page, mass control center, content script, background service worker, element picker, and floating countdown widget.
It does not govern websites that you visit or reload. Those sites may collect information under their own privacy policies when Chrome requests or reloads their content. Pulse Reload does not control those sites or their third-party resources.
The extension stores the settings you choose, including whether reloading is enabled, interval and unit, scheduled time and weekdays, timing jitter, hard-reload preference, visible-tab requirement, maximum reload count, page-change delay, trigger type, text or CSS selector values, selected element selector, and countdown visibility and position.
For ordinary page-specific rules, Pulse Reload derives a local key from the page origin and pathname, such as https://example.com/products. This lets the extension restore the correct rule for that page. The key remains in Chrome's local extension storage and is not transmitted to the developer.
The mass control center temporarily reads the open tabs' identifiers, titles, URLs, and favicon addresses so it can display the tabs and apply the actions you select. Tab-specific settings may be stored under the tab's Chrome identifier. Those tab-specific records are deleted when the tab closes.
When you use a text condition, Pulse Reload compares the text you entered with the current page's visible text. When you use a CSS-selector condition or the inspect-style picker, it queries the page's document structure to find the relevant element. When change detection is enabled, a browser MutationObserver watches the whole page or the selected element for changes.
This content is evaluated locally and transiently. Pulse Reload does not create or retain a copy of the page, does not record complete page text, and does not transmit observed changes externally. The specific text or selector you enter is stored as part of your local rule until you change or remove it.
The next reload timestamp and reload count are held in Chrome session storage so the popup and optional page widget can display the live countdown. Session values are temporary and are removed when a pulse stops or when Chrome ends the relevant browser session.
Pulse Reload does not intentionally collect names, email addresses, passwords, authentication tokens, payment information, precise location, health data, contacts, files, keystrokes, form submissions, cookies, or complete browsing history. It does not fingerprint users or build behavioral profiles.
Information accessed by the extension is used only to provide user-facing functionality:
save and restore reload settings for a page or individual tab;
calculate when the next reload should occur;
reload the tab normally or while bypassing cached resources;
decide whether configured text or page-element conditions are satisfied;
detect changes to the whole page or an element you select;
show open tabs and apply individual or bulk actions in Mass Mode;
display and remember the position of an optional on-page countdown; and
stop reloading after a configured safety limit.
Pulse Reload does not use information for advertising, marketing, credit decisions, surveillance, data brokerage, artificial-intelligence training, or purposes unrelated to automatic page reloading.
Permission
Purpose
Privacy boundary
storage
Saves page and tab rules, preferences, countdown timestamps, and temporary reload counts.
Uses Chrome local and session extension storage, not a developer-operated database.
tabs
Finds the active tab, displays open tabs in Mass Mode, reloads selected tabs, and detects when a tab closes.
Tab information is used inside the extension UI and is not sent to the developer.
scripting
Injects the extension's bundled content script into an already-open supported page when Chrome has not injected it automatically.
Only the packaged Pulse Reload script is injected; the extension does not download or execute remote code.
alarms
Reserved for reliable scheduling capabilities as the extension evolves.
The current implementation does not use alarms to collect or transmit information.
<all_urls>
Allows reload rules, text/selector conditions, element picking, change watching, and countdown widgets to work on ordinary sites chosen by the user.
Access enables local functionality. It does not authorize external disclosure, and Chrome blocks extension operation on protected internal pages.
Chrome may separately display permission notices and offers controls for limiting an extension's site access. Those browser controls operate in addition to the controls inside Pulse Reload.
Page rules and general preferences remain in chrome.storage.local until you edit them, remove them, clear the extension's site data, or uninstall the extension. They are not placed in Chrome Sync by Pulse Reload.
Mass Mode can create a setting tied to a specific Chrome tab identifier. The extension requests deletion of that setting when Chrome reports that the tab has closed.
Countdown timestamps and runtime reload counts are short-lived session values. The extension removes the active countdown record when the pulse stops. Chrome may also clear session storage when the browser session ends.
Uninstalling Pulse Reload causes Chrome to remove the extension's stored local data under Chrome's extension-data handling rules. The developer does not retain a server-side copy because no such copy is created.
Pulse Reload does not sell, rent, license, or share extension data with advertisers, data brokers, analytics providers, or other third parties. It does not transmit your settings or inspected page content to the developer.
When Pulse Reload reloads a page, Chrome makes ordinary network requests to that website and possibly to resources embedded by the website. Those requests are the expected result of reloading and are governed by the destination websites' privacy practices. Displaying a site's favicon in Mass Mode may use the favicon address already associated with the tab and handled by Chrome.
Information may be disclosed only if the extension is later changed to include a service described in an updated policy, or if required by applicable law. Because the current extension does not receive user data on a developer server, the developer generally has no extension data to disclose.
Pulse Reload follows a local-first architecture and uses Chrome's extension isolation and storage APIs. It is distributed without remote executable code and performs text, selector, and change checks inside the browser. Reducing external data transfer materially reduces exposure, but no software or device storage can be guaranteed perfectly secure.
You should avoid placing secrets into text or selector fields, keep Chrome updated, install Pulse Reload only from a trusted source, and review the extension's requested permissions before use.
Turn Pulse off at any time using the popup switch or pause controls.
Choose whether a rule applies to a page or to an individual tab through Mass Mode.
Use whole-page watching or limit observation to an element you select.
Disable the on-page countdown or reposition it by dragging.
Restrict reloading to visible tabs and set a maximum number of reloads.
Reset global defaults from the extension's options page.
Use Chrome's extension settings to restrict site access, disable the extension, clear extension data, or uninstall it.
Pulse Reload cannot fulfill server-side access, portability, or deletion requests because it does not maintain user accounts or a remote user-data database. You control the locally stored information through Chrome and the extension interface.
Pulse Reload is a general-purpose browser utility and is not directed to children under 13 or the minimum age required by applicable law. The extension does not knowingly collect personal information from children. Because no account or external collection system exists, Pulse Reload does not ask users to provide their age or identity.
Pulse Reload can be used in different countries, but its local-first design means extension settings ordinarily remain on the user's device rather than being transferred to another country for developer processing. Depending on where you live, privacy law may provide rights regarding personal data. The developer does not operate a database of Pulse Reload user data against which those rights would normally be exercised.
This policy may be revised when Pulse Reload's functionality, permissions, distribution, or legal obligations change. The effective date at the top will be updated. Material changes—especially any future introduction of analytics, accounts, external processing, or new data sharing—should be disclosed through the extension's distribution listing or release information before or when they take effect.
For privacy questions, concerns, or security reports relating to Pulse Reload, contact the developer through the aitaDev GitHub profile. Include “Pulse Reload privacy” in your message and do not include passwords, authentication tokens, or sensitive webpage content.
© 2026 Pulse Reload. All rights reserved.Built as a local-first Chrome extension.