Legal

Privacy Policy

This page explains, in plain language, what ThinkPulse can collect, why it is collected, where it may be stored, and what controls you have. We keep this policy specific to how the extension and website actually work today.

Last updated: May 5, 2026
Quick Summary

What this policy means in practice

ThinkPulse is designed to help inside the browser only when you actively use it. We do not claim to silently read everything you do. Data is handled in clear categories so account, billing, and AI features can function correctly.

Account and sign-in data

Google identity details (such as email and basic profile fields) are used for login and account mapping.

Billing and usage data

Plan state, wallet/recharge records, and usage counters are used for entitlement, limits, and history.

You control feature inputs

Text, images, OCR, and prompts are processed when you explicitly trigger those actions in the extension.

1. Scope of This Policy

This Privacy Policy applies to ThinkPulse website pages and the ThinkPulse browser extension. It covers data needed to provide login, AI assistance, OCR/image features, billing/recharge handling, notifications, and account support.

2. Data Categories We May Collect

2.1 Account and identity data

  • Google account email address used for sign-in
  • Basic profile data returned by Google sign-in flows (such as display name)
  • Account role/status information (for example user/admin, blocked/deleted, API-block state)

2.2 Billing and payment-related data

  • Plan state and entitlement status (free/basic/premium/admin)
  • Wallet and recharge ledger entries (including promo/invite/reward adjustments where applicable)
  • Payment references and billing activity required to validate top-ups and account balance

2.3 Usage and session data

  • Feature usage counters (for example chat/OCR window counts and totals)
  • Session metadata (for example active session domain/mode, timestamps, and limits)
  • Notification state (for example read/unread state for product and billing notifications)

2.4 User-provided content

  • Chat prompts/messages and optional image payloads you submit
  • Selected text, screenshot/OCR captures, and related query context you choose to process
  • User-configured API settings (including your own API endpoint/model choices, if provided)

2.5 Support and communication data

If you contact us for help, we may process your email address and the details you share so we can resolve account, billing, or technical issues.

3. How and Why Data Is Used

  • Authenticate users and protect account access
  • Deliver extension features such as chat, OCR, and contextual assistance
  • Apply plan limits, manage wallet balance, and process recharge-related actions
  • Store settings and user preferences to provide continuity across sessions
  • Maintain service reliability, debug issues, and prevent abuse/misuse
  • Respond to support and legal/compliance requests where required

4. Browser Access and Extension Permissions

ThinkPulse is built around explicit user actions. The extension processes content when you actively trigger actions such as asking a question, capturing text, using OCR, or sending a request.

We do not state that the product continuously reads every page in the background for profiling purposes. Access is tied to feature workflows you initiate.

5. Local Storage and Remote Sync

ThinkPulse uses local browser storage for fast extension behavior (for example auth/session state, feature settings, cached UI state, chat session memory, and usage/billing snapshots).

For signed-in users, selected account-linked state can also sync with backend services so your settings and account data stay available across reinstalls/logins. This includes state namespaces used for account and feature continuity (such as billing, account, settings, user API config, and OCR API config).

6. Third-Party Services and Data Sharing

To deliver product functionality, ThinkPulse may interact with third-party providers such as:

  • Google identity services for sign-in/authentication
  • Payment infrastructure for recharge and transaction processing
  • AI/OCR service providers used to fulfill user-requested prompts and captures
  • Hosting/infrastructure providers used for backend storage and service availability

Data shared with these services is limited to what is required for the requested feature or operation. Their own privacy terms apply to data processed on their systems.

7. Payments and Sensitive Financial Data

Payment processing is handled via payment infrastructure. ThinkPulse stores billing outcomes and ledger records needed for account credits and plan status, but does not intentionally store raw full card details on ThinkPulse-managed extension storage.

8. Data Retention

Retention depends on data type and product need. Account/billing records may be retained as long as needed for support, compliance, anti-fraud, and service continuity. Cached/local UI data may be cleared when you log out, uninstall, or manually reset extension data.

9. Security Measures

We apply reasonable technical and organizational safeguards to reduce unauthorized access and abuse. No internet-based system can be guaranteed 100% secure, but we continuously work to improve operational safety and reduce avoidable exposure.

10. What We Do Not Sell

ThinkPulse does not position its business as selling your personal data as a product. Data is processed to run the extension/service and its support workflows.

11. Your Controls and Rights

You can request access, correction, or deletion of personal data by contacting us.

  • Use in-product controls where available (for example clearing chats or changing settings)
  • Disconnect account usage by logging out and removing extension data
  • Contact support for account-level data review or deletion requests

12. Children’s Privacy

ThinkPulse is not intended for young children without supervision. If you believe data was provided by a child in violation of applicable requirements, contact us so we can review and act appropriately.

13. Policy Changes

We may update this policy when product behavior, legal requirements, or infrastructure changes. The latest version is always published on this page with an updated date.

14. Contact

For privacy questions or requests, email thinkpulse@gmail.com.