BrowserFloat Privacy Policy

Summary: BrowserFloat is a free bring-your-own-key (BYOK) study extension. It does not automatically transmit webpages to AI. Only when you expressly consent and request an AI response does the extension send the text you selected directly to the API provider that you configured. Ahaly does not receive the selected text or your API key.

What data is processed?

BrowserFloat reads a user-selected text snippet on supported webpages in order to display an action icon. Once you click the icon to request translation, explanation or a concise answer, the extension sends that selected text together with task instructions and response settings to the API endpoint selected in settings. The extension does not submit your full page content, browsing history or keystrokes to Ahaly. Do not submit confidential or sensitive material.

Third-party AI API providers

BrowserFloat 1.0.1 uses a user-supplied DeepSeek API key. BrowserFloat 1.1.0 and later also allow users to supply OpenAI Chat Completions-compatible HTTPS API endpoints, select models and enter API keys. Presets may include DeepSeek, OpenAI, OpenRouter, Google Gemini and Groq, but users can specify other compatible providers or gateways. Your selected text and API key are sent directly from the extension to the provider endpoint you choose, not to Ahaly infrastructure.

Selected providers or gateways may have their own terms, logging, retention, training, cross-border transfer practices and API fees. Their use of the data is controlled by their own privacy notices. Check the provider URL carefully before saving an API key; a custom endpoint receives the credentials and content you choose to send. We do not control the provider's handling of your data. Some providers may process data outside your country.

What is stored?

• API credentials: Stored in Chrome extension session storage only, separately for each configured provider in version 1.1.0. They are not intentionally stored in persistent preferences, page scripts or Ahaly servers. A browser restart, extension reload or update can require re-entry. You can clear credentials from settings.
• Preferences: Output language, mode, token limit, provider/model names, endpoint URLs, active model, AI consent and website pause settings are saved in Chrome local extension storage. Endpoint settings do not include secret keys.
• Responses: No persistent browsing or AI learning history is stored. The service worker may temporarily cache a few recent responses in memory to avoid duplicate requests, for up to two minutes.

Permissions and security

BrowserFloat uses website access to show the selection icon on supported pages, plus Chrome's scripting, activeTab and storage permissions. It can be paused globally or per website. AI requests are made over HTTPS. The custom endpoint feature rejects non-HTTPS URLs and URLs containing embedded credentials. Authentication headers are provided to the chosen endpoint only when a real AI request is made. Requests do not intentionally follow redirects.

Your choices

AI requests require an affirmative in-extension consent. You may disable consent at any time in settings, use demonstration mode without network AI requests, pause websites, delete stored API keys, or uninstall BrowserFloat to remove its settings. BrowserFloat does not require an Ahaly account or a subscription and does not sell user data or use it for advertising.

Contact and changes

For questions, please visit https://ahaly.app/ or use the support contact shown on our Chrome Web Store listing after publication. If we make material changes in how data is shared, we will update this policy and the consent experience as required. This policy is specific to BrowserFloat and does not describe separate Ahaly for Mac services.