Privacy Policy

This policy explains how SoundSlicr handles information when you visit the website and when you use the browser audio tools.

SoundSlicr is designed around local-first media processing. In the current version, tool workflows are meant to process files in the browser rather than uploading your audio or video to a SoundSlicr backend for processing or storage.

Because SoundSlicr includes advertising services, some information may still be processed by third parties when ads or advertising tags load. This policy separates (1) tool processing, (2) site operations, and (3) advertising services so the differences are clear.

SoundSlicr does not upload your audio or video files to a backend for audio processing.

Browser file APIs, MediaRecorder, WaveSurfer, and FFmpeg WASM may process files locally on your device.

When a tool route asks you to choose a file, the file is accessed through browser permissions and the browser's file APIs. SoundSlicr does not provide an account system or cloud project storage for you to send files to the service for later retrieval.

Some informational pages explain limits without requesting files. Working tool pages process files locally in the browser where supported.

If a tool fails, it may be due to local device limits (memory, CPU), browser codec support, or file condition (damaged, protected, unusually encoded). Those failures can occur without any server upload, because the processing is happening locally.

SoundSlicr does not offer accounts, billing, cloud storage, saved projects, or first-party analytics.

Basic hosting logs may be created by the hosting provider for security, reliability, and abuse prevention.

Hosting logs typically include information such as IP address, request path, request time, and user-agent details. These logs help prevent abuse and support site reliability, and they may be retained by the hosting provider according to their operational needs.

SoundSlicr does not ask you to submit your name, address, or payment information just to use the tools. If you contact us, you may voluntarily provide information in your email (see the Contact section below).

SoundSlicr includes the Google AdSense site verification and advertising tag. Google and its partners may receive information such as your IP address, browser details, page URL, and device or advertising identifiers when that tag loads.

Google may use advertising cookies, web beacons, IP addresses, or similar identifiers for ad delivery, measurement, fraud prevention, security, frequency control, and personalization where permitted. The ads or data processing available to a visitor can depend on consent choices and regional requirements.

Advertising tags are separate from audio tool processing. Loading an ad does not mean your selected audio file was uploaded to SoundSlicr.

You can learn how Google uses information from partner sites at https://policies.google.com/technologies/partner-sites and manage ad personalization at https://adssettings.google.com/.

SoundSlicr does not control the specific information Google collects through advertising services, or how Google processes it. For details, consult Google's privacy and advertising documentation, including any consent, regional, or personalization settings available to you.

SoundSlicr publishes an ads.txt file at /ads.txt that authorizes Google as a direct advertising seller for this site.

The ads.txt file is a public authorization record for ad inventory. It does not contain visitor information and is not used to process your audio files.

Google advertising services may place or read cookies and use similar identifiers as described above. Consent may be requested where required by law or Google policy.

SoundSlicr stores your light or dark mode preference in localStorage using the key soundslicr-theme. The install prompt dismissal may also be stored locally so the prompt does not repeatedly appear.

localStorage is stored in your browser on your device. It is not a cross-device account sync feature. Clearing site data in your browser typically removes these preferences.

SoundSlicr does not currently run a separate first-party analytics cookie. Advertising services may still use cookies or similar identifiers, subject to consent and regional rules.

SoundSlicr does not provide cloud storage for your processed media, and the current tool workflows are intended to avoid uploading media files for processing. That means SoundSlicr does not maintain a library of your audio inside a user account.

Processed downloads remain on your device after you save them. SoundSlicr does not keep a server copy of those exports.

Operational logs, if present, are retained according to hosting and security needs. Advertising identifiers and ad-related data retention are controlled by the relevant advertising services and their policies.

If you contact us by email, we retain only what is needed to answer the request unless a longer retention period is required for legal or abuse-prevention reasons.

Depending on where you live, you may have rights to access, correct, delete, or restrict certain personal information held by service providers that process data on behalf of websites you visit.

Because SoundSlicr does not operate user accounts or store your processed audio on its servers, many requests will relate to advertising data held by Google or operational logs held by hosting providers rather than a SoundSlicr media library.

For privacy questions about SoundSlicr, contact us through /contact with the subject line 'Privacy question.' Do not send private audio files unless specifically requested.

For Google advertising controls, use https://adssettings.google.com/ and Google's partner-site documentation linked above.

No system can guarantee perfect security. You should avoid processing files on shared or untrusted devices when the audio content is sensitive, and you should keep backups of important source recordings.

Only process files you own, created, licensed, or otherwise have permission to use. SoundSlicr tools make file handling more convenient but do not change copyright, workplace, or privacy obligations.

Privacy questions can be sent through the contact page at /contact.

Do not send private audio files unless specifically requested. If you are reporting a tool problem, you can usually describe the file format, approximate length, browser, and what happened without attaching the underlying recording.