Browser Extension Privacy Policy

This privacy policy covers the Bella — Executive OS browser extension (Chrome, Edge, Firefox, Safari). It is published alongside the extension so it can be linked from each store listing's "Privacy policy URL" field. The canonical hosted copy lives at https://withbella.io/legal/extension-privacy.

Bella is operated by Sajdak Group Holdings W.L.L. (Bahrain). For data-protection questions, contact privacy@withbella.io.

1. What the extension does

The extension is a window into your existing Bella account. It adds an inline assistant to the email and professional surfaces you already use so you can ask Bella about the message you are reading, draft replies, check your calendar, and look up relationship context — without leaving the page.

The extension does not create a new data store. Everything it shows comes from your authenticated Bella account; everything you send goes to the Bella API.

2. What data the extension reads, and where

The extension only activates on the specific sites listed in host_permissions. On those sites it reads page content (the open message / profile) so it can give the assistant context. It does not read any other website you visit.

The extension reads page content only while the corresponding tab is open and focused, and only the message/profile currently in view — never your whole mailbox, contact list, or browsing history.

3. What data is sent off your device, and to whom

When you ask Bella something about the open item (e.g. "summarise this", "draft a reply"), the extension sends the relevant context (sender, subject, body text, or the profile name/headline) to the Bella API at https://api.withbella.io over HTTPS. That is the only destination. We do not sell data, and we do not send your data to any third-party advertiser or analytics broker from the extension.

The Bella API processes your request inside your own Bella organization (tenant) and may use the configured AI provider to generate the response, governed by your Bella account's data-processing terms. No request is made until you take an explicit action in the extension.

4. Authentication & credentials

You sign in with your existing Bella account, using one of:

• Password — your email + password are sent once to POST /auth/login over HTTPS and exchanged for a short-lived access token. The password is never stored by the extension.
• Sign in with QR / code (OAuth 2.0 Device Authorization Grant, RFC 8628 + PKCE) — you approve the extension from an already-signed-in Bella browser session. The extension never sees your password in this flow.
• API key (advanced) — for self-managed deployments.

The resulting access token (and, for QR sign-in, a rotating refresh token) is stored using the browser's extension storage on your device only. It is never transmitted anywhere except the Bella API as a standard Authorization: Bearerheader. You can revoke a linked extension at any time from your Bella account's device list, or by signing out of the extension.

5. What we store locally

• The access/refresh token for your session (extension storage, on-device).
• A randomly generated per-install device identifier (used only to deduplicate and revoke this specific extension install — it is not linked to any advertising identifier).
• A short-lived cache of items already fetched from the Bella API, to reduce network calls. Cache entries expire automatically.

Signing out clears the token. Removing the extension clears all local data.

6. What we do NOT do

• We do not track your browsing across the web.
• We do not read pages outside the host permissions above.
• We do not sell, rent, or share your personal data with third parties.
• We do not use the data for advertising or for any purpose unrelated to the assistant features you invoke.
• We do not transfer or use data to determine creditworthiness or for lending purposes.

7. Permissions justification (single-purpose)

Every permission maps directly to the single purpose of "show your Bella assistant inside the email/professional sites you use":

• activeTab / storage — read the focused tab on demand; persist your session.
• alarms — periodic background badge refresh (unread/commitment counts).
• sidePanel (Chrome/Edge) — render the assistant in the browser side panel.
• contextMenus— right-click "Ask Bella about this".
• Host permissions — see the table in §2; each is a surface the assistant augments. No <all_urls> permission is requested.

8. Data retention & your rights

Locally stored data is retained only until you sign out or remove the extension. Data processed by the Bella API is retained per your Bella account's terms; you can exercise access/deletion rights through your Bella account or by contacting privacy@withbella.io.

9. Changes

We will update this policy as the extension evolves and bump the "Last updated" date. Material changes will be surfaced in the extension or via your Bella account.