Privacy · Chrome extensions

Chrome Extension
Privacy Policy

Last updated: September 8, 2026

This policy describes data handling for the Bifrost Launch extensions listed below. Each product section forms part of this policy. It covers extension use; our website and business communications policy covers visiting our website and contacting us.

Shared data practices

Our extensions access and use data only to provide the functions described in their listings and in the product sections below. Processing data locally still counts as handling data. The listed extensions do not send extension content to a Bifrost-operated backend, and do not include advertising, tracking or analytics services.

We do not sell or rent extension user data, use it for advertising or creditworthiness decisions, or use it to train general-purpose AI models. Our use of extension user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data use is limited to providing or improving the disclosed user-facing purpose. Transfers are limited to those necessary for that purpose, those you authorize, or those required by law. We do not allow people to read extension user data except with your explicit consent for specific information, where necessary for security or legal compliance, or as otherwise permitted by the Limited Use requirements.

KickScope

Purpose and data: KickScope enhances Kickstarter research. While enabled on Kickstarter, it reads relevant page content and campaign responses to display funding amounts, backer counts, campaign dates, rewards and creator history. When you open a story preview, it processes that story’s text, HTML, title, URL and image references. Optional image recognition processes selected project images and their recognized text.

Network and recipients: KickScope reuses campaign data already loaded by Kickstarter and makes additional requests directly to Kickstarter for missing details. These same-origin requests may use your existing Kickstarter session. KickScope does not send your session to Bifrost. On your request, it downloads project images from Kickstarter or its image delivery hosts, including Imgix, over HTTPS. These services receive the requested resource and ordinary connection information such as your IP address. KickScope does not send project content to an external AI API; optional recognition uses Chrome’s on-device AI. Chrome may download a model, subject to Google’s own browser services and policies.

Storage and retention: The enabled setting is stored in local extension storage until changed or removed. Story content is temporarily passed through browser session storage and removed when the reader retrieves it; an unconsumed entry can remain for the browser session. Recognition results, image URL hashes and cache timestamps are stored locally. Cached results expire after 30 days and are removed when accessed or during subsequent cache writes, rather than by an always-running deletion timer. Cache size limits may remove results earlier.

Permissions and controls: Kickstarter site access supports the page enhancements. The storage permission saves settings, temporary stories and recognition results. Clipboard write access copies content only when you choose to copy it; KickScope does not read your clipboard. Optional Kickstarter and Imgix host permissions are requested for the image origins used by a story when you choose recognition. You can decline or revoke those permissions, switch KickScope off in its popup, use “Clear cache” in the reader, or remove the extension. Copies you paste elsewhere remain under your control.

AI Prompt Assistant

Purpose and data: AI Prompt Assistant (also known as Team Prompt Manager) reads a Feishu Base prompt library you configure and fills chosen prompt templates into supported AI websites. It handles Feishu application credentials (App ID and App Secret), access tokens used for API requests, Base and table identifiers, cached prompt records, API domain preferences, and prompt text and template parameters you choose to use.

Network and recipients: Authentication and table-reading requests go directly from your browser to the configured Feishu/Lark API over HTTPS. Feishu receives the credentials or token and table identifiers needed for those requests; the data is not routed through Bifrost servers. When you fill a prompt into ChatGPT, Claude, Gemini or AI Studio, that text becomes available to the selected website and is subject to its own data practices. Filling a prompt is not a promise that the website only processes text after submission. The extension does not collect your AI conversation history for Bifrost.

Storage, permissions and deletion: Configuration, credentials and prompt cache are held in local extension storage until replaced, cleared or the extension is removed. Local browser storage is not an encrypted credential vault. Storage access supports that configuration; active-tab and scripting access support filling prompts; host access enables the supported AI sites and Feishu API. You can change your configuration, stop using autofill or remove the extension to delete its local storage. Deleting local data does not delete records in Feishu or text already shared with an AI website; manage those with the corresponding provider. Revoke application credentials in Feishu when they are no longer needed.

Feishu Minutes Exporter

Purpose and data: After you choose to start collection, Feishu Minutes Exporter reads the transcript you are authorized to view on the current Feishu/Lark Minutes page. This includes speaker names, timestamps, transcript text, page title and page URL, for export as TXT or JSON.

Storage and recipients: Collected results remain in the current page session. The extension does not upload transcripts, account information or exported files to the developer or another remote server. Exported files are saved to your device when you choose to export. Feishu/Lark continues to operate the original website under its own privacy policy.

Permissions and deletion: Active-tab access identifies the current Minutes page; scripting injects the packaged collection script; Feishu/Lark Minutes site access reads the authorized transcript; downloads access saves the requested file. You can stop collection or close the page to end the session. Delete downloaded TXT/JSON files yourself when no longer needed. Removing the extension does not remove already exported files.

Security and third-party services

Extension API and image requests described above use HTTPS. Access is constrained by browser permissions and the permissions of your account on the source website. Local data remains subject to the security of your device and browser profile. We do not promise that local storage is encrypted or that any system is completely secure.

Third-party services process information they receive under their own terms and privacy policies. Disabling or uninstalling an extension does not delete data from those services. These extensions are independent products and are not endorsed by Google, Kickstarter, Feishu/Lark or the AI websites they support.

Your choices and privacy requests

You can review or revoke extension site access in Chrome’s extension settings, stop optional features and remove an extension. Product-specific deletion steps appear above. Bifrost cannot remotely retrieve or delete data stored only in your browser or files on your device.

If you email support, we receive the email address and information you choose to send and use them to resolve your request. Please do not send passwords, App Secrets or private transcripts. For access, correction or deletion of information you have sent us, email [email protected] with the subject “Extension Privacy Request” and the extension name. Support correspondence is covered by our business communications policy.

Changes and additional extensions

We update this page when data practices change and show the revision date above. Additional extensions are covered once their product-specific data practices are listed here. Material changes requiring disclosure or consent will be presented in the affected extension before the new processing begins; publication of this policy alone does not constitute consent.

Contact

Bifrost Launch
[email protected]
Extension help & support