1. Overview
SavePulse for Qlik is a Chrome extension designed to trigger the existing Qlik Cloud Save action after a compatible note/comment field has changed and the user leaves that field.
SavePulse is designed to operate locally in the user's browser. The current public SavePulse release does not use a SavePulse backend, analytics service, advertising system, telemetry service, or remote-code service.
2. Information SavePulse handles
Note/comment field content
When a user interacts with a supported Qlik note/comment field, SavePulse temporarily reads the field value in browser memory so it can compare the value before and after editing and determine whether a save should be triggered.
This may include website content, form data, and user-generated content entered in the supported field.
SavePulse does not intentionally store the note/comment value in Chrome storage, send the note/comment value to SavePulse or JBR Collection servers, log it, use it for analytics or advertising, or sell or share it.
Qlik page/app location
If the user uses Teach SavePulse, SavePulse stores a local mapping keyed to the applicable Qlik origin and app/path scope so the taught workflow can be applied to the correct Qlik environment. This information remains in Chrome local extension storage on the user's device.
3. Information stored locally
SavePulse may store the following in Chrome local extension storage:
- floating SavePulse position;
- minimized/full-size state;
- Saving Alert enabled/disabled state;
- Saving Alert screen position;
- a generated taught-workflow ID;
- an editor CSS selector;
- a Save-control CSS selector;
- a local key containing the Qlik tenant origin and app/path scope for the taught mapping.
These settings are used only to provide SavePulse's user-facing functionality.
The current public SavePulse release does not intentionally store note text, Save-button text, screenshots, passwords, authentication tokens, cookies, or customer records.
4. Network transmission
The current public SavePulse release does not make network requests to a SavePulse backend. The extension contains no SavePulse analytics, telemetry, advertising, or remote-code system.
When SavePulse triggers a Qlik Save control, the resulting save is handled by Qlik and the user's existing Qlik environment under the user's existing relationship with Qlik and their organization. SavePulse does not receive a server-side copy of that saved note.
5. Sensitive information
A Qlik note field may contain sensitive or confidential information. SavePulse may necessarily read the active supported field locally to determine whether it changed.
SavePulse is not designed to collect or transmit customer names, VINs or identification numbers, account numbers, financial information, email addresses, phone numbers, login credentials, authentication cookies, screenshots, or business records.
Users remain responsible for following their organization's rules regarding what information may be entered into Qlik.
6. Teach SavePulse
Teach SavePulse allows a user to identify the editor used for the note/comment workflow and the Save control used for that workflow.
Teach Mode stores selector-based mappings locally. It is not designed to store the text entered in the editor. The current public SavePulse release also sanitizes older development-build mappings so unnecessary UI descriptor fields are removed.
7. Support screenshots
The extension does not capture or upload screenshots.
If a user voluntarily contacts SavePulse Support about an unsupported Qlik layout, Support may ask the user to provide a screenshot of the relevant edit/Save workflow.
Before sending a screenshot, users should remove or obscure all confidential or sensitive information, including customer names, VINs, account numbers, email addresses, phone numbers, financial information, internal company information, and any other information they should not share.
Support should only review information the user intentionally provides for the support request.
8. Data sharing and sale
The current public SavePulse release does not sell user data. The current public SavePulse release does not transfer Qlik note contents or locally stored SavePulse preferences/taught mappings to third parties.
9. Advertising
The current public SavePulse release does not use user data for personalized, retargeted, or interest-based advertising. The extension contains no advertising system.
10. Retention and deletion
Locally stored SavePulse settings remain in Chrome extension storage until they are changed, removed, cleared by Chrome/the user, or the extension is uninstalled.
A taught mapping can be removed using Forget Taught Layout. Because the current public SavePulse release has no SavePulse server-side data store for these extension settings or note contents, there is no corresponding SavePulse server copy to delete.
11. Site access
The current public SavePulse release is scoped to supported HTTPS Qlik Cloud tenant pages under https://*.qlikcloud.com/*. An additional runtime guard limits activation to supported tenant-style Qlik Cloud hosts. SavePulse does not request access to arbitrary websites.
12. Chrome Web Store Limited Use
SavePulse's use of information obtained through Chrome extension permissions and supported Qlik page access is limited to providing and improving SavePulse's disclosed single-purpose Qlik auto-save functionality and related user-facing compatibility features.
SavePulse does not use or transfer that information for personalized advertising or other unrelated purposes.
13. Changes to this policy
If SavePulse's data practices materially change in a future version, this policy and the Chrome Web Store disclosures should be updated before or with that release, and users should be informed as required.
14. Contact
For support or privacy questions: savepulse@jbrcollection.com
Support page: jbrcollection.com/savepulse/support