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, a coarse error category when a file cannot be processed (such as damaged file or file too large), 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. Each event also carries how many times it has happened in the open tab (1 for the first file, 2 for the second, and so on); that count lives only in the tab’s memory and starts again when the page reloads. After someone cleans more than 10 files in one visit, BeforeShare may ask once whether they would pay for a Pro version; if you answer, only the fixed option you pick (a price, no, or skip, and optionally what the files are for) is recorded. The server adds a device type (phone, tablet or computer) worked out from the browser’s user agent, and does not record events from known search and advertising crawlers. These events exclude filenames, file contents, extracted metadata values, error messages, 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. Processing events can also include a fixed stage (inspection, cleaning including reinspection, verification, or saving) and a broad time range: up to 0.25 seconds, 1 second, 5 seconds, 15 seconds, or longer. Exact times remain in browser memory. A save event describes dispatch or the share action, not proof that a file was saved to disk. Operational counts also record selection and file-size ranges, capacity limits and waiting queues, completed batch outcomes, explicit retry outcomes, neutral-filename choices, fixed failed-check codes, and save cancellation, fallback or export failure. Inspection sends only a broad result: supported removable details found, none found, or incomplete inspection; no field names, metadata categories, generator names or values are sent. The server adds only broad platform and browser families. No file fingerprints or session identifiers are collected. These measurements are best effort and do not prove that an output was saved. Hosting request logs remain separate and can contain IP addresses and timestamps.

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 10 October 2026. It may be updated when the service, providers, or legal requirements change.

← Clean Files

Privacy Policy