Last updated: 24/09/2026
FloMark ("the extension," "we," "our") is a Chrome and Edge browser extension for documenting browser workflows through screenshots, screen recordings, and step-by-step interaction capture, helping users create clear QA reports, walkthroughs, and how-to guides.
This policy explains what data FloMark accesses, how it's used, and — most importantly — what FloMark does not do with it.
FloMark does not transmit your recorded content or other user data to servers operated by FloMark or to third parties.
FloMark does not sell user data or use it for advertising or tracking.
Everything you record — screenshots, video, audio, notes, report titles — stays on your own device, in your own browser's local storage.
FloMark has no backend server, no analytics, and no third-party integrations of any kind.
2.What FloMark accesses, and why
Screenshots & step data
What it's for: Captured when you mark a step, to build your report
Where it goes: Stored locally on your device only (IndexedDB)
Screen video & microphone audio (only if you enable it)
What it's for: Recorded when you use Screen Video mode
Where it goes: Stored locally on your device only (IndexedDB)
( Active tab content / page URL , Webpage content and page URL )
What it's for: FloMark accesses webpage content and the current page URL when you use its recording and documentation features. This allows FloMark to identify interactions, capture relevant information for your documentation, and determine whether a page can be recorded.
Where it goes: This information is processed locally by the extension and is not transmitted to FloMark's servers or third parties.
Window and display position (system.display, chrome.windows)
What it's for: To correctly place privacy-redaction covers on full-desktop captures
Where it goes: Never transmitted; used only for on-device geometry calculations
Report/session names you type
What it's for: To label and export your reports
Where it goes: Stored locally only
Chrome Web Store review requires a plain-language reason for each permission. Here's the full list:
storage / unlimitedStorage — FloMark uses Chrome's local storage facilities to save extension settings and locally generated session data. unlimitedStorage is requested because screenshots, recordings, audio, and related session data can exceed Chrome's standard extension storage quota.
tabCapture — Used when you choose to capture or record the current browser tab. FloMark uses the resulting media locally to create the screenshot/video output requested by you.
desktopCapture — Used by FloMark's PRO recording mode when you choose to capture your screen, window, or browser tab. Chrome displays its native screen-selection prompt, and FloMark receives the selected media stream for the recording you requested.
offscreen — FloMark uses an offscreen document for background processing that requires document-based web APIs which are not available directly in the Manifest V3 service worker.
scripting — Used to execute FloMark's recording, marking, annotation, and privacy functionality within webpages when required by the user's selected recording/documentation workflow.
alarms — Used for internal scheduling/timing of background tasks; does not access any personal data.
system.display — Used only to determine your monitor's exact position and size, so that PRO mode's privacy-redaction feature covers the correct area of a full-screen capture. This never reads or transmits any content — only display geometry (position and resolution).
Host permission (<all_urls>) — FloMark requests access to webpages because its primary function is to record and document browser workflows on websites selected by the user. This permission allows FloMark's recording, marking, annotation, and privacy tools to operate on the webpages where the user chooses to use them. FloMark does not use this access for advertising, behavioral profiling, browsing-history analytics, or tracking.
All screenshots, video, audio, and report data are stored locally in your browser (via chrome.storage and IndexedDB) and are never uploaded to any server, cloud service, or third party.
Data persists locally until you export it, delete it, or clear your browser's extension data. Uninstalling the extension removes all locally stored data.
You are always in control of exporting (as HTML, Word, or PDF) or discarding a recording session.
FloMark does not:
Use any analytics or telemetry SDKs
Include any advertising code
Share, sell, or transmit any user data to any third party
Make any network requests to external servers
Use cookies or any cross-site tracking mechanism
If you choose to enable microphone audio during Screen Video recording, that audio is recorded and processed entirely on your device and is included only in the video file you create. It is never transmitted anywhere, and is never recorded unless you explicitly enable it for that specific recording.
FloMark is a productivity/documentation tool intended for general professional use and is not directed at children under 13. We do not knowingly collect data from children, and since FloMark collects no data of any kind from any user, this applies uniformly.
FloMark is designed with a local-first architecture. Recorded screenshots, video, audio, and session data are stored locally and are not transmitted to FloMark servers or third parties.
Because FloMark does not operate a backend service for storing recorded content, there is no FloMark server-side repository containing your recordings. However, locally stored data remains subject to the security of your device, operating system, browser profile, and any files you export or share.
If this policy changes, the "Last updated" date above will be revised, and material changes will be reflected here before taking effect.
10. Chrome Web Store Limited Use Compliance
FloMark's use and handling of information received through Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. FloMark uses user data only to provide the extension's disclosed user-facing functionality, does not sell user data, does not use user data for personalized advertising, and does not transfer user data to third parties except where necessary to provide the extension's functionality or where required by law or for security purposes.
11. Exports
FloMark allows users to export recordings and reports to files such as HTML, Word, and PDF. Exported files are created locally on the user's device. Once exported, the security and privacy of those files depends on where the user stores, transfers, or shares them. FloMark does not automatically upload exported files to a server.
12. Permissions may change
FloMark may introduce additional features in future versions that require additional Chrome permissions. If a future feature requires access to additional categories of user data, this Privacy Policy and the extension's disclosures will be updated to accurately describe that access before or when the relevant functionality is introduced.
Questions about this policy or FloMark's data practices can be directed to:
[ pradeepmondol1996@gmail.com]