FAMULOR

Famulor Loop Chrome Extension Privacy Notice

Effective date: 4 November 2026

This notice supplements the Famulor Privacy Policy and explains data handling specific to the Famulor Loop extension for Google Chrome.

Famulor Loop does not inspect websites, use content scripts, read page content, collect Chrome browsing history, or request access to the titles and URLs of browser tabs.

1. Who is responsible

BEK Service GmbH, Westendstr. 2A, 87439 Kempten (Allgäu), Germany, operates Famulor. Contact: support@famulor.io. Depending on the data and customer relationship, Famulor acts as controller or as processor for the customer's workspace under the applicable agreement.

2. What the extension does

Famulor Loop is a business-communications companion for authenticated Famulor workspace users. Subject to workspace settings and entitlements, it can place and receive Loop calls, operate active-call controls, show operational notifications, and display authorized call and AI-agent activity history. History remains available to authorized users when Loop telephony is not enabled for their workspace.

3. Data handled

The extension handles only data needed for those disclosed functions, which may include:

Famulor account, workspace, member, installation, and browser-softphone identifiers;
authorized contact, caller, recipient, and destination details;
call and interaction metadata such as channel, direction, status, time, and duration;
authorized message subjects, previews, summaries, participants, and statuses;
destinations and transient keypad or DTMF input entered by the user;
questions you manually submit for workspace knowledge search, knowledge-base names, source names and matching original passages;
live microphone and remote call audio while a browser call is connected;
notification, appearance, presence, microphone, and incoming-call preferences;
OAuth client registration, short-lived access and call capabilities, and rotating refresh material;
a small per-workspace activity cursor used to avoid duplicate notifications; and
limited IP, device, security, error, call-quality, and reliability diagnostics.

The extension does not collect a Famulor password. Authentication occurs on Famulor's authorization page using OAuth Authorization Code with PKCE.

4. Microphone, call audio, recording, and transcription

The extension requests microphone access only after an in-product explanation and the user's affirmative Enable microphone action. During a browser call, live audio is transmitted through the communications infrastructure needed to connect the call. Users can deny or revoke microphone access in Chrome or operating-system settings.

Microphone permission does not itself authorize recording or transcription. If a workspace separately enables either feature, the applicable call notice, workspace configuration, customer instructions, contract, and law govern that processing.

Knowledge hints during a call

When your workspace plan includes live hints, you can choose a knowledge base and manually submit a question during your active Loop call. Famulor sends the search text to its AI embedding service (currently OpenAI through Vercel) to find matching workspace passages. This feature does not listen to or transcribe the call. Questions and returned passages stay in panel memory only and are cleared when the call ends, the panel closes, the workspace or account changes, or you disconnect. The extension does not save them in Chrome storage. This search does not add the question to your workspace history; operational security records follow the retention rules in the main privacy policy.

5. Local storage, sign-out, and revocation

Chrome local storage holds non-secret preferences, an installation identifier, notification cursors, the OAuth client registration, and refresh material needed to maintain the signed-in session. Chrome session storage holds short-lived access material and transient call state where supported. Call audio recordings and Famulor passwords are not stored by the extension.

When the user selects Disconnect, active local authentication and call state are cleared and server revocation is attempted. If revocation cannot be confirmed, the client identifier and refresh credential remain in a separate local retry queue solely to retry revocation. A queued credential is never used to restore a session. It is removed after a successful server response or when Chrome removes the extension or browser-profile storage. Removing the extension ends local retries but does not by itself prove that a temporarily unreachable server credential was revoked; support can complete server-side revocation.

6. Notifications

With Chrome and operating-system permission, the extension may show incoming, missed, or failed-call notifications and enabled AI-agent activity notifications. Notifications are not used for advertising. Users can disable activity notifications, incoming-call notifications, or all extension notifications. The Show notification details setting controls whether available call-party or activity details are shown; otherwise generic text is used.

7. Purposes

Extension data is used only to:

authenticate the user and enforce workspace authorization;
provide calling, call controls, user-requested workspace knowledge search, notifications, presence, directory, and authorized history;
maintain security, prevent fraud or abuse, and diagnose service failures;
monitor call quality and reliability; and
respond to a user's specific support or privacy request.

Extension data is not sold, used for personalized advertising, used to determine creditworthiness or lending eligibility, or transferred for purposes unrelated to these disclosed functions, security, or legal requirements.

8. Parties that process or receive extension data

Depending on the feature used, data may be processed by or disclosed to:

BEK Service GmbH (Famulor), which provides the extension and service;
Supabase, Inc., for authentication, database, and related service infrastructure;
Vercel Inc., for application and API hosting and operational logs;
Twilio Ireland Limited and its affiliates, for browser voice signaling, live media transport, telephony delivery, call-quality, and SDK reliability diagnostics;
the call participant and the telecommunications networks needed to complete a user-requested call; and
competent authorities or professional advisers where disclosure is legally required or necessary to establish, exercise, or defend legal claims.

Google Chrome and the user's operating system provide local extension storage, identity redirection, microphone permission, and notifications. Google also distributes the extension through the Chrome Web Store under Google's own terms and privacy policy. The extension does not send browsing history or website content to Google.

9. Human access and Chrome Web Store Limited Use

Famulor's use and transfer of data received through the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Human access is permitted only when:

the user gives explicit consent to access specific data for a specific support request;
access is necessary for security or abuse investigation;
access is required by applicable law; or
the data is aggregated and anonymized for internal operations and cannot identify a user.

10. Retention and controls

Transient extension state is retained only for the active session, call lifecycle, safe recovery, notification deduplication, token validity, or pending revocation described above. Server-side account, call, interaction, security, and support records follow the main Privacy Policy, workspace configuration and customer instructions, contractual requirements, and law.

Disconnecting does not delete the Famulor account or authorized workspace history. Users may request access, correction, export, deletion, objection, or restriction through Famulor product controls or Famulor Support.

11. Security and international transfers

Extension traffic uses encrypted HTTPS/WSS and the encrypted real-time transports required for calls. OAuth tokens are scoped to the dedicated browser-extension API and its exact first-party resource paths. Where providers process data outside the EEA, Famulor uses the transfer safeguards described in the main Privacy Policy and applicable agreements.

12. Contact and changes

Questions and privacy requests can be sent to support@famulor.io or through Famulor Support. This notice may be updated when the extension or applicable requirements change; the effective date above identifies the current version.