FieldPulse — Privacy Policy

      Summary: FieldPulse processes all data locally in your browser. No data is transmitted to external servers. We do not collect, store, or share any personal information or Salesforce data.
    

1. What FieldPulse Does

FieldPulse is a Chrome extension that analyzes field-level data quality on Salesforce Lightning record pages. It overlays visual analytics (fill rates, health scores, edit frequency) directly on the page you are viewing.

2. Data Access

FieldPulse accesses the following Salesforce data only within your browser:

Field metadata — field names, labels, data types, and page layout information via the Salesforce UI API
Aggregate field statistics — fill rate counts (e.g., "5,000 out of 10,000 records have this field populated") via SOQL COUNT() queries. Individual record data is never retrieved or stored.
Edit frequency data — aggregate counts from Salesforce History tables (how often each field is edited org-wide)
Session authentication — the Salesforce session cookie (sid) from your active browser session to authenticate API calls. This token is held in memory only and never persisted to disk.

3. Data Storage

All cached analytics data is stored exclusively within your browser using:

chrome.storage.session — in-memory storage cleared when the browser closes
IndexedDB — local browser database for analytics cache (auto-expires based on TTL)
chrome.storage.local — user preferences (palette, toggle settings)

No data is ever transmitted to any external server, third-party service, or analytics platform.

4. Data We Do NOT Collect

Individual Salesforce record data (names, emails, phone numbers, etc.)
Personal information about the user
Browsing history or activity outside of Salesforce pages
Usage telemetry or analytics
Crash reports or error logs sent externally

5. Third-Party Services

FieldPulse uses zero third-party services. The only network requests made are to the Salesforce REST API at your own org's domain (e.g., yourorg.my.salesforce.com). The extension loads the IBM Plex Sans font from Google Fonts for the side panel UI only.

6. Permissions Explained

activeTab — access the current Salesforce tab to detect record pages and inject the overlay
storage — save user preferences and cached analytics locally
sidePanel — render the analytics dashboard in Chrome's side panel
scripting — inject the content script into Salesforce pages
alarms — schedule periodic cache refresh (every 30 minutes)
cookies (optional) — read the Salesforce session cookie for API authentication
Host permissions (*.salesforce.com, *.force.com) — make REST API calls to your Salesforce org

7. Data Retention

Cached analytics data expires automatically:

Field metadata cache: 7 days
Fill rate data: 24 hours
Edit frequency data: 1 hour
Session data: cleared when browser closes

You can clear all cached data at any time using the "Clear Cache" button in the extension popup or side panel.

8. Security

All API calls use HTTPS with Bearer token authentication
Session tokens are stored in memory only (chrome.storage.session), never written to disk
Content script UI is rendered inside a Shadow DOM to prevent CSS/JS leakage
The extension follows Manifest V3 security requirements

9. Changes to This Policy

If we make material changes to this privacy policy, we will update the "Last Updated" date at the top of this page and notify users through the Chrome Web Store update description.

10. Contact

For privacy-related questions or concerns, please contact us or open an issue on our GitHub repository.