Chrome Extension Privacy Policy

1. Overview

This privacy policy describes how the SpikeCore AI Chrome Extension (the "Extension") collects, uses, and protects your information. The Extension is developed and operated by Spiketech Enterprise Private Limited ("SpikeCore AI," "we," "us," or "our"). It applies specifically to the browser extension; use of the SpikeCore AI web platform is governed by our main Privacy Policy.

2. Information We Collect

The Extension collects and processes the following data:

• Authentication credentials: Your email address and a JWT authentication token are stored locally in Chrome's extension storage to maintain your login session. We never store your password.
• Question text: When you request an AI answer, the text you select or type is sent to SpikeCore's servers for processing. It is used solely to generate your answer and is not retained after processing.
• Portal context: The URL and page title of the procurement portal you are visiting are sent alongside your question to provide contextual answers. This data is not stored permanently.
• Active project selection: Your selected project ID is stored locally to remember your preference between sessions.
• Answer history: Your recent answers (up to 20) are stored locally in Chrome's extension storage for your convenience. This data never leaves your browser.

3. Information We Do NOT Collect

• We do not collect, read, or store form data you enter on procurement portals.
• We do not track your browsing history or activity outside of supported portals.
• We do not collect any personal information beyond what is needed for authentication.
• We do not use third-party analytics, tracking pixels, or advertising services.
• We do not collect device fingerprints or system information through the Extension.
• We do not access your cookies, bookmarks, or other browser data.

4. How We Use Your Information

• Authentication: To verify your identity and provide access to your SpikeCore account.
• Answer generation: To process your questions against your project's knowledge base using AI.
• Credit tracking: To deduct credits from your account for answer generation.

5. Data Storage and Security

• Authentication tokens are stored locally in Chrome's secure extension storage.
• All API communication uses HTTPS encryption.
• Your knowledge base documents remain on SpikeCore's servers and are never downloaded to the Extension.
• Answer history is stored locally in your browser and can be cleared at any time from the extension popup.

6. Data Sharing

We do not sell, trade, or transfer your information to third parties. Your question text is processed by AI language model providers (Anthropic and/or OpenAI) through SpikeCore's servers to generate answers. These providers process the data via API under their respective data processing agreements with SpikeCore and do not retain your data or use it to train their models.

7. Host Permissions

The Extension requests host permissions for the following domains to inject the answering interface:

• gem.gov.in — Government e-Marketplace (India)
• eprocure.gov.in — Central Public Procurement Portal (India)
• sam.gov — System for Award Management (USA)
• ebuy.gsa.gov — eBuy GSA (USA)

These permissions are used solely to add the SpikeCore AI answering overlay to procurement portal pages. The Extension does not read, modify, or transmit any other content from these pages.

8. Your Rights

• You can clear your local answer history at any time from the extension popup.
• You can log out at any time, which removes your authentication token.
• You can uninstall the Extension at any time, which removes all locally stored data.
• You can request deletion of your SpikeCore account and all associated data by contacting us.

9. Changes to This Policy

We may update this privacy policy from time to time. Changes will be reflected by updating the "Last updated" date at the top of this page. Continued use of the Extension after changes constitutes acceptance of the updated policy.

10. Contact

If you have questions about this privacy policy or the Extension's data practices, please contact us: