Our Core Privacy Promise

Your files are processed locally in your browser. BeforeShare is designed so inspection and cleaning happen on your device. The normal product flow does not require us to receive the contents of your files.

Information We Do Not Collect

Uploaded files
The visible contents of files
Metadata extracted from files
Cleaned file outputs
Personal information contained inside files

Operational Data We May Process

BeforeShare records basic tool events in its existing Google Cloud hosting logs: tool page, language, coarse file format (for a rejected unsupported file, only its extension category such as HEIC or MP4), sample or user workflow, inspection, cleaning, download or unsupported-file outcome, and a coarse arrival category. The arrival category is worked out inside your browser from the referring site or a campaign tag and reduced to a fixed label such as search engine, AI assistant, social or forum, or unknown; the referring address itself is never sent, and an arrival is only labelled when the evidence is clear. After a cleanup succeeds you may be offered one optional question about how you found BeforeShare. Answering is voluntary, only the fixed option you choose or the fact that you skipped is recorded, and a temporary flag in the browser tab, cleared when you close it, stops the question repeating. These events exclude filenames, file contents, extracted metadata, query strings, free text and persistent user identifiers. The event requests send no cookies or referrer and are skipped when your browser signals Do Not Track or Global Privacy Control. Hosting request logs can still contain technical information such as IP addresses.

Cookies, Advertising, and Google AdSense

BeforeShare uses Google AdSense to support the service. Third-party vendors, including Google, may place or read cookies and use web beacons, IP addresses, or other identifiers to serve, personalize, and measure ads based on visits to this site and other websites. BeforeShare may also store a lightweight cookie to remember your language choice. File inspection and cleaning remain local in your browser; BeforeShare does not intentionally send your files or extracted metadata to Google through those tools.

Your Privacy Choices

You can manage ad personalization through Google Ads Settings and use any consent controls shown on the site. You can also block or clear cookies in your browser; clearing the BeforeShare language cookie only resets the saved language preference. Where consent is required, you may withdraw it through the available consent control or your browser settings.

Retention and Third-Party Processing

BeforeShare does not retain selected file contents, extracted metadata, or cleaned outputs because the normal tool workflow does not send them to our server. Hosting and advertising providers may process technical logs, cookie identifiers, IP addresses, and ad-interaction data under their own terms and configured retention periods. Their practices are described in the linked Google partner-sites information and any consent interface shown to you.

Security Approach

Keeping file processing in the browser significantly reduces server-side exposure. It does not replace careful review when a file contains sensitive visible content, but it does remove an important class of avoidable leakage.

Product Limits

BeforeShare removes hidden metadata. It does not automatically redact visible text, signatures, screenshots, or the visible content rendered on a page. Users should review files before sharing them when the stakes are high.

Last reviewed

This privacy notice was last reviewed on 9 September 2026. It may be updated when the service, providers, or legal requirements change.

← Clean Files

Privacy Policy