Window-following blur for Mac

Blur that follows your window.

Pin a mask to a display or update it as your selected window moves and resizes. Inspect the composited result before you share.

macOS 14.0 or later · Local-first · Apache-2.0

Two coordinate modes

Pin it. Follow it. Inspect it.

Match the sharing method with two placement modes and a separate preview you can check.

Display Pin

For notification areas and fixed layouts. Place a mask at a proportional position on one display.

Window Pin

For moving windows. Update a mask's position and size from proportional window coordinates.

Share Preview

Composite matching Window Pins on your Mac and inspect the result in a separate regular window.

Share Guide

See the different workflows for full-display, single-window, and browser-tab sharing.

Three visual styles

Choose Frost, Mosaic, or Redact for an area you have visually identified.

Last-position cover

Optionally cover the latest position known to the app after tracking stops. It may not be current.

Inside the app

See the complete path before you share.

These are shipping BlurFollow screens, shown in the same order as the placement and verification workflow.

BlurFollow onboarding screen comparing Display Pin and Window Pin
Pin to a display. Follow a window.Compare both placement modes before choosing where the mask belongs.
BlurFollow Share Guide explaining full-display, single-window, and browser-tab workflows
Choose for your sharing method.Share Guide explains when to inspect desktop masks and when to use Share Preview.
BlurFollow pre-share review screen listing full-display, single-window, and browser-tab checks
Check every mask before sharing.Inspect the composite, then verify it again in the meeting application's preview.
BlurFollow Settings screen showing mask visibility, Screen Recording access, local export and deletion, version, and license information
Local controls, on your Mac.Review visibility, permission, export, deletion, version, and licensing in one place.

Guide

Place the mask, inspect the result, then share.

Choose the capture method first. A desktop overlay and a single-window or browser-tab capture do not behave the same way.

Basic use

Pin to a display

  1. Choose Display Pin from Home.
  2. Drag over the area on the target display.
  3. In Masks, choose Frost, Mosaic, or Redact. Adjust Strength for Frost or Mosaic, then inspect the position and appearance on the actual display. Redact remains opaque.

Follow a window

  1. Choose Window Pin from Home.
  2. Select the source in Apple's system picker.
  3. Drag over an area inside the window. Move and resize the source to inspect the resulting mask position.
  4. If the source was recreated, its title changed, or its state becomes Select again, use Reconnect… in Masks. Inspect the layout again after reconnecting.

Adjust an existing mask

  1. Open the mask in Masks. Strength changes the appearance of Frost and the tile size and opacity of Mosaic. Redact remains opaque regardless of Strength.
  2. To change its position, choose Move…, then drag the mask itself on screen. Release the mouse or trackpad to save the position; press Esc before saving to cancel. Move… is available when masks are shown, that mask is on, and its position is known.
  3. Open the BlurFollow menu-bar icon to identify each Display Pin or Window Pin by name and state, then switch that mask on or off. Show Masks is the master switch for desktop overlays; when it is off, no desktop mask is displayed even if its individual setting is on. Share Preview uses individually enabled Window Pins, so inspect it separately.

A Window Pin updates its displayed position as its source moves or resizes. When a matching mask's position, style, Strength, or on/off state changes—or Share Preview's capture state changes—Share Preview updates its display and may clear or cover the previous image while updating. If “I checked every mask” is reset, wait for the current composite and inspect every mask again. A display update does not guarantee zero latency, exact alignment while moving, correct mask placement, or correct shared content.

Choose a sharing method

Full display

Inspect the desktop masks first, choose the full display in the meeting app, and inspect that app's own preview. Watch for notifications, other Spaces, and full-screen changes.

Single window

An overlay drawn by another app is normally excluded from single-window capture. Open Share Preview in BlurFollow, select the source, and inspect every matching Window Pin. In the meeting app, select BlurFollow Share Preview instead of the original window.

Browser tab

Tab sharing also excludes desktop overlays. Share Preview selects the browser window, so inspect whether browser chrome or content outside the intended tab is visible. Share BlurFollow Share Preview to the meeting app and inspect its receiving preview.

Before pressing Share

Following, Placed, and Preview active describe technical state observed by BlurFollow. They do not certify the content. Recheck BlurFollow and the meeting app after scrolling, zooming, moving, reconnecting, or editing a mask.

Support

Permissions, limitations, and troubleshooting.

BlurFollow reports technical state, but you remain responsible for checking the actual image shown to the receiver.

Screen Recording permission

  • Display Pin: does not require Screen Recording permission.
  • macOS 15.2 or later: Window Pin and Share Preview use authorization for the window selected in Apple's system picker.
  • macOS 14 through 15.1: the compatibility path requires broader Screen Recording permission to identify the selected window without guessing. After granting access in System Settings, quit and reopen BlurFollow.

If access is denied, Window Pin and Share Preview stop instead of guessing a window. Check System Settings → Privacy & Security → Screen Recording. On macOS 14 through 15.1, revoke the broader permission there when it is no longer needed.

BlurFollow does not request Accessibility, Full Disk Access, camera, or microphone permission.

Limits of a visual aid

BlurFollow assists with mask placement and pre-share inspection; it is not a security control. It does not automatically identify confidential information or guarantee mask placement, blur or mosaic unreadability, or inclusion in a shared output. Scrolling, zoom, layout changes, child windows, tracking loss, and capture method can change what appears. Remove secrets from the source where possible, choose opaque Redact when appropriate, and visually inspect both BlurFollow and the meeting application's receiving preview every time.

Frequently asked questions

The desktop mask is missing when I share a Chrome window or tab.

Single-window and tab capture normally excludes another app's overlay. Composite the browser window and matching Window Pins in Share Preview, then select BlurFollow Share Preview as the meeting app's sharing target.

A Window Pin no longer follows its window.

The window may have closed, become hidden, been recreated, or become ambiguous among similar candidates. Check Masks and use Reconnect… to choose it again with Apple's picker. Proportional coordinates remain, but visually inspect whether the content layout changed.

What is Last-position cover?

When window position becomes unavailable, it can cover the latest position BlurFollow had available. That may not be the source's current position and does not replace reconnecting or checking the shared output.

Share Preview says Preview paused or shows a covered frame.

BlurFollow does not show its normal composite if no matching Window Pin exists, the source or frame cannot be validated, restored settings need acknowledgement, or capture stopped. Follow the reason shown in the window: add or reconnect a Window Pin, review restored settings, or select the source again.

Do blur and mosaic make information unreadable?

See Limits of a visual aid for why opaque Redact and receiver-side inspection may be more appropriate.

Does BlurFollow record or upload screen content or audio?

See the privacy summary and Screen frames for the exact behavior of version 0.1.0 and the separate role of a meeting app.

How do I delete stored masks?

See Retention, deletion, and choices for individual masks, all app settings, exported settings, and backups.

Contact

For product support, email support@hinoshiba.com in Japanese or English. For privacy questions, use the subject BlurFollow Privacy.

For support, include the BlurFollow version, macOS version, Mac model/architecture, sharing method, source and meeting app, displayed state, reproduction steps, expected result, and actual result. Reproduce with fabricated data. Do not send real confidential frames, window titles, personal data, or credentials.

For a suspected vulnerability, include “Security” in the subject and do not post details in a public issue.

Privacy policy

How BlurFollow handles screen content and settings.

The policy below describes each feature of the audited macOS build.

Last updated: August 16, 2026 · Applies to: BlurFollow 0.1.0 for macOS

Summary

  • No account, advertising, analytics, tracking, or third-party runtime SDK.
  • Window frames are processed transiently on the Mac for Share Preview. BlurFollow does not write them to a recording or send them to its developer.
  • No audio, camera input, keystrokes, or clipboard content is captured.
  • Mask settings and limited metadata used to identify a selected window again are stored locally.

Screen frames

For Share Preview, ScreenCaptureKit provides one window deliberately selected in Apple's system picker. BlurFollow composites matching Window Pins in memory and displays the result in a separate regular window. Audio capture is disabled.

The current app has no code intended to encode frames as an image or video, transmit them over a network, analyze them, or use them for model training. It releases its current preview image when capture stops. This does not claim complete control over macOS swap, GPU buffers, crash diagnostics, user-created screenshots, backups, or another process with screen-capture access.

After a user shares BlurFollow Share Preview through a meeting, streaming, or recording app, that product and its recipients process the displayed video under their own terms. BlurFollow does not control meeting participants, recordings, or later redistribution.

Local settings

BlurFollow stores these categories in a JSON configuration:

  • mask name, proportional rectangle, visual style, strength, corner radius, enabled state, creation date, and display identifier;
  • for Window Pin, window ID, process ID, app name, bundle ID, window title, and saved window bounds; and
  • global visibility, Last-position cover, onboarding, and related preferences.

In a sandboxed Mac App Store build, the file normally resides at Library/Application Support/BlurFollow/Masks.json inside the app container. BlurFollow may keep the last validated settings at Masks.json.backup in the same folder. Window titles and user-entered mask names may themselves be sensitive.

Export Mask Settings writes the same categories to a user-selected location. That copy is then subject to the storage, synchronization, and backup software chosen by the user.

Transfers and App Privacy

The audited 0.1.0 app has no network client or remote endpoint. The developer does not collect personal data through the app, share data for advertising, or track users across apps or websites. For the current unmodified build, the expected Apple App Privacy answer is “No, this app does not collect data.”

The App Store, signing and notarization services, download host, macOS, and a meeting app may process information separately as their respective providers. That is distinct from a BlurFollow runtime transmission.

Retention, deletion, and choices

  • Stop Share Preview to end capture and release the current preview from app state.
  • Disable or delete individual masks. Delete All Masks empties the mask list and removes the recovery backup.
  • To remove every stored setting, quit BlurFollow, then delete Masks.json and Masks.json.backup from its sandbox container.
  • Delete exported settings and copies held by synchronization or backup products separately.
  • Uninstalling the app may leave Application Support or sandbox-container data behind.

There is no BlurFollow account or server profile to access or delete.

Policy changes

If a future build adds networking, accounts, analytics, payments, cloud sync, or another change to data handling, this policy and the App Privacy answers will be updated before distribution.

Open source

Open code. Explicit boundaries.

BlurFollow code and ordinary documentation use the Apache License 2.0. Brand Assets and trademarks have separate terms.

Apache License 2.0

Except for Brand Assets and verbatim third-party legal texts, BlurFollow source code and ordinary documentation are provided under the Apache License, Version 2.0. Subject to its conditions, the license permits use, modification, redistribution, and commercial use. Redistributors must retain the license and NOTICE, identify modified files, and preserve required attribution. Patent and termination provisions also apply.

Apache-2.0 commercial-use permission does not grant permission to use the BlurFollow name, logo, or icon as a product brand. It also provides no warranty of fitness or absence of defects. The full license text controls.

Current distribution dependencies

The audited 0.1.0 app bundles no third-party runtime library, SDK, package, executable, model, font, analytics SDK, advertising SDK, or updater. It links to frameworks supplied by macOS, including AppKit, SwiftUI, ScreenCaptureKit, and Core Image. Apple frameworks and the Swift runtime are not relicensed under BlurFollow's Apache-2.0 terms.

Each future release must re-audit packages, embedded frameworks, resources, fonts, build tools, and CI actions, then update notices for what is actually distributed.

Name, logo, and icon

The BlurFollow name, logo, app icon, and confusingly similar source identifiers are governed by the trademark and brand policy. Icon artwork and derived renditions are excluded from Apache-2.0; their respective rights holders reserve all rights. Unless separately authorized, a fork or redistribution should use its own name, bundle ID, icon, signing identity, support contact, and privacy statement.

Availability of a name or design varies by territory, goods and services, and similarity. These documents are not trademark clearance or legal advice.

License and audit documents

These downloads reproduce the texts included with the distribution.