Famulor Loop does not collect Chrome browsing history or request access to the titles and URLs of browser tabs. It reads website content in one case only, and only if you allow it: when you turn on phone links, it reads the address of a phone link at the moment you click it, so the number opens in the Loop dialer.
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.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.Phone links on websites (optional)
You choose under Settings → Phone links whether a phone number you click on a website opens in Famulor Loop or in your system’s phone app. Loop is the preselected choice, but nothing happens on websites until you select Allow on websites and confirm Chrome’s own permission request for access to websites. Chrome words that request broadly. Famulor Loop uses the access for one purpose:- A small script that is part of the extension package is added to the pages you open.
- It acts only when you click a phone link (
tel:) and reads only that link’s number. - It does not read other page content, forms, or the page address, and sends nothing over the network itself.
- The number is placed in the Loop dialer on your device and is sent to Famulor only when you select Call, like a number you type yourself.
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, including a number taken from a phone link you clicked while phone links are on
- 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, phone-link, 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
- limited IP, device, security, error, call-quality, and reliability diagnostics
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.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.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.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
- respond to a user’s specific support or privacy request
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
- competent authorities or professional advisers where disclosure is legally required or necessary to establish, exercise, or defend legal claims
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
- the data is aggregated and anonymized for internal operations and cannot identify a user