Screen capture
ScreenK9 uses Apple’s ScreenCaptureKit to create a filtered representation of the display you choose. Frames are rendered into the local ScreenK9 audience window. ScreenK9 does not upload, record, or analyze frame content.
Chrome companion
The extension stores a profile label, classification, and random local profile identifier inside that Chrome profile. It sends the local Mac helper that data together with the active tab title, Chrome window ID, tab count, and timestamp. It does not send URLs, account email, browsing history, cookies, form values, or page content.
ScreenK9 uses the title only to match a work Chrome window to a shareable macOS window. Unknown, stale, personal, or ambiguous matches are excluded.
Local storage
Privacy profiles and redaction regions are stored with macOS user defaults. Fresh Chrome profile snapshots are stored under your user Application Support directory. A license key and its activation ID are stored in macOS Keychain. ScreenK9 has no product account or cloud synchronization.
Purchases & licenses
Polar Software Inc. provides checkout, receipts, license keys, and the customer portal. During purchase, Polar processes the contact, payment, billing-country, and tax information needed to complete the order. ScreenK9 does not receive or store full payment-card details.
When the Mac app activates or validates a license, it sends Polar the license key, ScreenK9 organization identifier, activation identifier, device label, and licensed major-version condition. It never sends screen content, window or tab titles, URLs, application names, profile labels, or meeting data to Polar.
Optional product analytics
The website sends cookieless, memory-only page-view, checkout, and download events to a dedicated ScreenK9 project in PostHog EU. Session recording, autocapture, and person profiles are disabled. A session-storage flag prevents the same exit offer from appearing more than once in one browser tab session.
Anonymous analytics inside the Mac app are off by default. If you enable them from the menu-bar app, ScreenK9 sends only product events such as app launch and capture start or stop, together with the app version and a random installation identifier. It never sends screen pixels, window or tab titles, URLs, application names, profile labels, redaction regions, or meeting data.
Permissions
macOS Screen Recording permission is required to create the audience view. Chrome grants the companion access to tabs, local extension storage, alarms, and the ScreenK9 native messaging host. ScreenK9 does not request Chrome identity, browsing-history, cookie, or general website access, and does not request Accessibility, camera, microphone, or meeting-account access on macOS.
Important limits
ScreenK9 protects only the separate window it creates. If you share a physical display directly, your meeting tool receives that display outside ScreenK9’s control. Protected video, DRM content, and operating-system surfaces may be unavailable to capture. Any unavailable or unverified state is hidden by default.
For the practical capture boundary, compare the ways to share several apps without sharing the full screen. For browser identity, use the guide to keeping client Chrome profiles private.