flanger

Privacy Policy

Effective date: July 8, 2026

Flanger Musician Workstation is a Chrome extension for local music practice tools on compatible HTML5 media pages. Flanger processes media content and Flanger interface interactions to provide its features. It does not sell user data or use user data for advertising.

Information Flanger Handles

Flanger handles the following Chrome Web Store user data categories:

• Website content: audio, video, Media Source Extensions (MSE) chunks, media segments, media URLs, playback state, timing, and related media metadata from compatible pages. When the extension is enabled on a page with an active MediaSource, Flanger may capture MSE audio chunks while the player is hidden. When the user clicks Run Flanger, those chunks may be decoded and buffered locally so Flanger can detect tempo, split stems, control playback, loop sections, repitch audio, and synchronize the mixer/metronome.
• User activity: clicks, keyboard shortcuts, dragging, scrolling, pointer position, and editing gestures inside the Flanger interface. Flanger uses this information to operate DAW controls, mixer controls, beat/section editing, transport controls, and other visible extension features.

Information Flanger Does Not Collect

Flanger may use the current page or media URL locally only to operate on the active media page. It does not create a browsing profile, sell browsing activity, or send browsing history to external servers.

How Information Is Used

Flanger uses handled information only to provide its visible music practice features, including local media processing, playback control, looping, repitching, stem separation, and interface controls.

Storage And Retention

Flanger only keeps data for the media currently being played. When playback changes, previously processed data is cleared.

To make processing start smoothly when the user clicks “Run Flanger,” Flanger may temporarily pre-buffer encoded media data while the extension is enabled. This data stays on the user’s device, is not decoded until processing is started, and is cleared when the current media changes.

Security

Flanger is built with privacy in mind. All processing happens locally on the user’s device, without data leaving the device.

Because this data stays on the user’s device, the developer does not have access to the user’s media content or Flanger processing data.

Changes

This policy may be updated when Flanger changes its data handling practices. Material changes will be reflected on this page.

Contact

For privacy questions about Flanger, contact the developer through the Chrome Web Store listing.