Is Screen & Webcam recorder - Flonnect safe?
Screen Recorder is rated clean, though our review noted the following. Flonnect's bot-insert control in Meet, Teams, or Zoom sends the meeting URL to Flonnect's backend with credentials included.…
Who publishes itFlonnect - 2 other listings from the same operator, none carrying a finding
Flonnect - 2 other listings from the same operator, none carrying a finding
Same store account
2 other listings published from this account, 6k+ users between them, none of them carrying a finding.
Screen Recorder findings
Meeting URL sent to Flonnect for recording bot
Flonnect's bot-insert control in Meet, Teams, or Zoom sends the meeting URL to Flonnect's backend with credentials included.
DA confirmed the Meet bot control is injected; live join needs an active-meeting click, so no body was captured.
What actually happens
You click Flonnect's control to add a notetaker bot to a Google Meet, Microsoft Teams, or Zoom meeting.
The extension sends the meeting URL to Flonnect's backend so the notetaker can join the call.
The background script includes browser credentials on the backend requests.
Fields assembled for the bot-join flow
- Meeting URLhttps://meet.google.com/abc-defg-hij (illustrative)
Identifies the exact call that the Flonnect notetaker is asked to join.
- Notetaker nameFlonnect Notetaker
Controls the participant name shown for the bot when it joins the meeting.
- Signed-in Flonnect sessioncredentials: include
Links the bot-join request to the browser session that is signed in to Flonnect.
- Meeting platformzoom
Tells Flonnect whether the request came from Google Meet, Microsoft Teams, or Zoom status handling.
Captured request
No live response body was captured; dynamic analysis confirmed the Google Meet control injection, while the live join POST requires an authenticated active meeting click.
When this fires
Every 2 seconds
After the join request succeeds, the extension checks the bot's meeting status every two seconds until the call ends.
The code that does this
The click handlers pass meeting URLs to the background script
Google Meet sends the current page URL
content.js:109213-109218const u = (0, e.useCallback)(() => { o("loading"), window.chrome.runtime.sendMessage({ message: "insert_meet_bot", meetingUrl: window.location.href })}, [o]);Microsoft Teams sends the extracted meeting URL
content.js:116590-116597const u = (0, e.useRef)(null), d = (0, e.useCallback)(() => { o("loading"), window.chrome.runtime.sendMessage({ message: "insert_meet_bot", meetingUrl: u.current, source: "outlook" }) }, [o]);Zoom sends the current page URL and source
content.js:117083-117089const d = (0, e.useCallback)(() => { o("loading"), window.chrome.runtime.sendMessage({ message: "insert_meet_bot", meetingUrl: window.location.href, source: "zoom" })}, [o]);The code that does this
The background handler sends the URL to Flonnect and polls status
Readable background handler
background.js:1168-1232} else if (message.message === "insert_meet_bot") { try { const settingsRes = await fetch(`${host}/flonnect/api/googlemeet/settings`, { method: "GET", credentials: "include", }); if (!settingsRes.ok) throw new Error("Failed to get bot settings"); const settingsData = await settingsRes.json(); const botName = settingsData?.notetakerName || "Flonnect Notetaker"; const meetingUrl = message.meetingUrl; const joinRes = await fetch(`${host}/flonnect/api/googlemeet/join-with-url`, { method: "POST", credentials: "include", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ meetingUrl, notetakerName: botName }), }); if (!joinRes.ok) throw new Error("Failed to join meeting"); const joinData = await joinRes.json(); const eventDbId = joinData?.eventDbId || joinData?.data?.eventDbId || joinData?.id; currentBotEventDbId = eventDbId; currentBotSource = message.source || "meet"; chrome.tabs.sendMessage(senderId, { message: "insert_meet_bot_status", success: true, botName, }); // Start polling bot status every 2 seconds if (botStatusPollInterval) { clearInterval(botStatusPollInterval); botStatusPollInterval = null; } botStatusPollTabId = senderId; const pollBotStatus = async () => { try { const res = await fetch(`${host}/flonnect/api/autorecord/get-bot-status`, { method: "POST", credentials: "include", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ eventDbId, source: currentBotSource }), }); const data = await res.json(); console.log(data,"data in sytatys") const status = data?.data?.botStatus; chrome.tabs.sendMessage(botStatusPollTabId, { message: "bot_status_update", status, }).catch(() => {}); if (status === "bot.call_ended" || status === "bot.done") { clearInterval(botStatusPollInterval); botStatusPollInterval = null; } } catch (e) { console.error("Bot status poll error", e); } }; pollBotStatus(); botStatusPollInterval = setInterval(pollBotStatus, 2000); } catch (e) { chrome.tabs.sendMessage(senderId, { message: "insert_meet_bot_status", success: false, }); }}External host receiving the meeting-bot requests
- backend.flonnect.com
Receives the settings request, the meeting URL join request, and repeated bot-status polling for Flonnect's notetaker flow.
Screen Recorder version history
8.1.2
Mar 4, 2026
+4 more
8.2.88
Sep 19, 2026
8.2.89
Sep 23, 2026
8.3.7
Nov 21, 2026
Chrome Web Store listing
- Versions
- 8.3.7 latest of 8 seen since March 4, 2026
- Store rating
- 3.8 from 1,267 ratings
- Last updated
- November 21, 2026
- Size
- 9.7 MiB
- Privacy policy
- flonnect.com
