1. Local media analysis
The video file is processed in your browser.
When you choose a video, ClipCompat uses the browser File API and a Web Worker running MediaInfo compiled to WebAssembly to inspect media metadata. The selected video is not uploaded to a ClipCompat server for analysis.
The analysis can derive technical facts such as container, codec, profile, bit depth, chroma, frame rate, frame-rate mode, resolution and audio properties. Those facts are used in memory by the page to produce the compatibility result.
2. What the checker does not collect
No account, media database or upload history exists.
- No user account or profile
- No server-side video upload for analysis
- No server-side storage of selected video files
- No database of analysis results
- No server-side database of advertising profiles created by ClipCompat
- No dedicated application analytics integration currently embedded in ClipCompat pages
ClipCompat does not intentionally send the selected video file, filename or extracted media facts to Google AdSense or a dedicated application analytics service as part of the checker result.
3. Hosting and normal web requests
Loading the website is different from uploading your media.
ClipCompat is served through Cloudflare infrastructure. When you request the site, Cloudflare may process ordinary network and request information needed to deliver, secure and operate the service, such as IP addresses, traffic-routing information, requested URLs and related connection data. This traffic is separate from the selected video file, which remains in the browser for analysis.
For more information about Cloudflare's handling of end-user data, see the Cloudflare Privacy Policy.
4. Google AdSense connection
AdSense code is present for site verification and review.
ClipCompat includes Google AdSense code and a publisher verification meta tag. Google may receive ordinary web-request information when its code is loaded. If ads are served, Google and its advertising partners may process data and use cookies or similar technologies according to applicable law and consent choices. See How Google uses information from sites or apps that use its services.
6. External links
Vendor documentation is outside ClipCompat.
Guides and Methodology pages link to Adobe, Blackmagic Design, MediaInfo/MediaArea and other external websites. Opening those sites is subject to their own privacy practices and may create network requests or cookies controlled by those third parties.
7. Security and limitations
Local processing reduces transfer, but it is not a security guarantee.
Keeping media in the browser removes the need for ClipCompat to receive and store the selected file, which reduces one category of privacy risk. Users should still use a trusted device and browser, keep software updated and avoid selecting files on shared devices when that would expose sensitive material locally.
8. Contact messages
Email is processed only when you choose to contact ClipCompat.
Messages sent to contact@clipcompat.com are routed through Cloudflare Email Routing to a monitored mailbox. The message, sender address and ordinary email metadata are handled by the services involved in delivering and receiving that email. Do not attach private footage or sensitive files by default.
9. Service and consent changes
This policy is updated when data flows materially change.
If advertising, analytics, consent management, error telemetry, accounts or another feature changes how personal data is processed, this policy and related notices will be updated to describe the active production behavior. Where consent is legally required, the relevant technology must use an appropriate consent mechanism for that user.
10. Privacy contact
Questions about this policy can be sent by email.
Contact contact@clipcompat.com for privacy questions related to ClipCompat.
Last reviewed: September 30, 2026