Overview
SearchPulse is an independent mobile application for viewing and exploring Google Search Console information. It is not affiliated with or endorsed by Google. SearchPulse is designed so that Search Console requests travel directly between the app and Google over HTTPS instead of passing through a Priority Bit or SearchPulse server.
This policy explains what information SearchPulse accesses, why it is used, where it is stored and the controls available to you. If a future version changes these practices, this policy and the in-app disclosures will be updated before the new use takes effect.
Google user data
SearchPulse uses Google Sign-In to authenticate you and requests only the read-only Search Console permission https://www.googleapis.com/auth/webmasters.readonly. The app does not request Search Console write access and cannot submit indexing requests, modify sitemaps or change your Search Console properties.
With your permission, the app accesses your Google account identifier and session information, verified Search Console properties, Search Analytics performance data, sitemap information and URL Inspection results. SearchPulse uses this information only to provide the dashboards, comparisons, exploration, watchlists, inspections, exports, widgets, deterministic on-device insights and optional on-device Apple Intelligence explanations that you request.
SearchPulse’s use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Storage and transmission
Google credentials remain in the secure storage supported by Google Sign-In. SearchPulse does not copy raw OAuth tokens into its local database, preferences, logs or fixtures. Search Console data is cached locally on your device to make the app responsive and useful when a refresh is temporarily unavailable.
Cached Search Console records, property choices, watchlists, recent inspections and settings are stored in the app’s local container. A compact metric snapshot may be stored in the shared Apple App Group solely so the SearchPulse widget can display your latest locally available summary. Version one has no hosted SearchPulse database, custom API, remote configuration service, advertising SDK, standalone product-analytics integration, server AI or third-party AI service.
SearchPulse uses Google Sign-In for authentication. Google Sign-In’s embedded Apple privacy manifest declares that Google may collect name, email address, phone number, coarse location, user and device identifiers, other usage data, and other data types for app functionality and analytics. It declares this information linked to the user and not used for tracking. Google processes those direct interactions under its own privacy terms.
When a signed-in user opens the Properties sheet, SearchPulse may request a small public site icon directly from that property’s host over HTTPS. It checks only conventional public favicon paths and does not include Google credentials, account details, Search Console response data, cookies or a referring page. Icons are validated, kept only in memory for the current app session and replaced by a local monogram when unavailable. SearchPulse does not use a third-party favicon service or fetch site pages for metadata. Like any direct website request, the property host can receive ordinary connection information such as the device’s public IP address.
On a supported device, a Pro user can deliberately ask Apple Intelligence to explain one deterministic insight. SearchPulse sends Apple’s on-device model only sanitized, pre-calculated facts: the signal category, evidence strength, detection rule, report dates and displayed metrics. It does not provide the model with the Google account, email address, property identifier, query or page identifier, OAuth credential, raw API response or inspected URL. SearchPulse does not use Private Cloud Compute for this feature, and the generated response is not stored, logged, exported or shared with the widget.
Google API requests are sent directly to Google over HTTPS. Purchase and entitlement requests are sent directly to Apple through StoreKit. Those providers process information under their own terms and privacy policies.
Sharing and sale of data
Priority Bit does not sell SearchPulse user data. SearchPulse does not send your Search Console data to Priority Bit, advertisers, data brokers, analytics providers or other third parties. Data is disclosed only through the direct Google and Apple service interactions and limited property-host icon requests described above, when you deliberately export a file using Apple’s system sharing interface, or when disclosure is required by applicable law.
Purchases and device authentication
Apple provides SearchPulse with a verified StoreKit entitlement so the app can unlock Pro features. Priority Bit does not receive your payment-card details through the app. If you enable the optional device lock, SearchPulse receives only the success or failure result from Apple’s authentication framework; biometric data is never made available to SearchPulse.
Your controls and retention
Local data remains on your device until you clear it, disconnect the account and delete local data, delete all SearchPulse data from Settings, or uninstall the app. The app also provides separate controls to clear cached API data and recent inspections, sign out of Google, restore purchases and disable the optional device lock.
You can revoke SearchPulse’s Google access through your Google Account permissions. Revoking access stops future Google API requests but does not by itself delete records already cached on your device; use SearchPulse’s delete controls or uninstall the app to remove those local records.
Security and logging
SearchPulse uses HTTPS for provider requests and relies on Apple and Google security controls for sign-in and purchases. Developer logging is designed not to include OAuth tokens, API response bodies, email addresses, property identifiers, query or page data, or inspected URLs. No method of storage or transmission is completely risk-free, so users should also protect their device and Google account.
Questions and updates
Questions about SearchPulse privacy can be sent to Luan@prioritybit.co.za. The current policy will remain available at this address, with the effective date updated when material changes are made.