Summary
SwearSoap does not require an account, include advertising or analytics, or send captured audio to a SwearSoap-operated cloud service. The Chrome extension sends captured audio only to the SwearSoap application running on the same computer through the local loopback connection.
Information SwearSoap processes
When the user explicitly asks SwearSoap to prepare a YouTube video, the extension processes the current YouTube video identifier, the video address needed to associate the work with that video, playback state, and captured tab audio. This processing is necessary to create and apply the clean-language filter requested by the user.
Where processing occurs
Captured audio is transferred from the Chrome extension to the SwearSoap desktop application at 127.0.0.1, which refers to the same computer. The included speech-recognition model processes the audio locally. SwearSoap does not transmit the captured audio, transcript, or completed filter to the developer or to a SwearSoap cloud server.
Storage and retention
- Captured audio is stored temporarily while a requested scan is processed. SwearSoap attempts to delete it after both successful and failed scans. Known incomplete temporary files are cleaned during later startup.
- Transcripts are not saved.
- Completed filter files remain on the computer so the same video does not need to be scanned again.
- Rotating diagnostic logs may contain video identifiers and technical status or error codes. They do not intentionally contain captured audio, transcripts, request bodies, browser cookies, authentication data, or full video addresses.
Sharing and sale
SwearSoap does not sell user data. SwearSoap does not share captured audio, transcripts, filters, browsing activity, or diagnostic logs with advertisers or data brokers.
Chrome permissions
- tabCapture: captures audio from the user-selected YouTube tab after the user starts the cleaning workflow.
- offscreen: supports audio recording required by Chrome’s extension architecture.
- activeTab and scripting: prepares the selected YouTube player, displays progress, and applies mute events.
- Access to 127.0.0.1:8765: communicates with the SwearSoap desktop application on the same computer.
User control and deletion
The user starts each new filter creation by selecting SwearSoap. The workflow can be cancelled while capture is active. Removing the Chrome extension stops browser integration. Uninstalling the Windows application removes its program files but intentionally leaves filters and logs so an upgrade does not erase them. A user can remove that retained information by deleting %LOCALAPPDATA%\SwearSoap.
Security
The local service binds only to the loopback interface. Requests are origin-restricted, uploads and filter files are validated, filter writes are atomic, logs rotate, and owned backend shutdown requires a per-launch token. No software can promise perfect security, but SwearSoap is designed to limit access and retain only what its local filtering function requires.
Children
SwearSoap is a general-purpose tool for a parent, guardian, or other user operating their own computer. It does not knowingly collect personal information from children or provide accounts for children.
Changes to this policy
Material changes will be posted on this page and reflected by a new effective date.
Contact
Questions can be submitted through the SwearSoap GitHub issue tracker. Do not attach captured audio or private diagnostic information to a public issue.