LEGAL / PRIVACY

Privacy Policy

Updated August 30, 2026 · Video Compressor · Developer and data controller: Anton Mikhailenko, Sapiest Dev · sapiest.dev@gmail.com

Overview

Video Compressor is designed to compress videos selected by you on your Android device, iPhone/iPad or Chrome browser. Our service does not accept your video bytes, frames, thumbnails, filenames, paths or media metadata for conversion.

Video and file data

The selected source is read locally for inspection, planning, encoding and verification. The original is not automatically deleted. The output is written as a new copy and is only considered successful after technical checks.

We do not send video bytes, frames, thumbnails, filenames, file paths, URIs, folder names, or the source file's exact duration, resolution, codec or size to analytics, crash reporting, advertising or billing. Analytics may include the compression options you choose, such as an output-format preset, resolution choice, target-size range and batch count; these are settings, not an inspection of your media.

Local storage

Each client may store job state, settings, permission or security-scoped access references, output references, consent choices and entitlement state locally so the flow can recover. Local history and outputs are controlled by you. A browser may require the tab or Chrome process to remain open for active work; iOS and Android may stop work under system resource policies.

Data that may leave the device

Android 1.0.2 and Chrome 1.0.5.0 introduce the measurement behavior described below. Pseudonymous usage and reliability analytics is enabled by default unless you previously opted out. You can turn it off in Settings without losing local compression or saving. An existing explicit opt-out is preserved when you update. This Android/Chrome release does not change the analytics choice in iOS; iOS diagnostics follow its reliability setting.

• Usage and reliability: while analytics is on, allow-listed installation, session, screen, conversion, save, settings, review-prompt and purchase-state events may be sent to Sapiest's first-party analytics service. Records use randomly generated installation, session and event identifiers, timestamps, product/platform and app-version information, bounded settings and safe outcome/error categories. Android also uses Firebase/Google Analytics for approved usage signals. We use these records to measure active use, feature reliability and conversion outcomes, not to identify the contents of your videos or track your browsing history.
• Installation sources: Android reads Google Play Install Referrer and reduces it locally to normalized UTM source, medium, campaign, content and term values for an install_attribution event. Raw referrers and full URLs are not sent. For Chrome installations reached through Sapiest, the onboarding page may pass the same bounded campaign fields to the exact extension ID within 24 hours. This is campaign attribution, not access to other browsing activity.
• Chrome lifecycle: while analytics is on, the extension records extension_installed and registers a signed uninstall callback. When Chrome opens that callback, the edge service records extension_uninstalled using the pseudonymous installation identifier, then redirects to a clean feedback page. Opting out removes the analytics callback. Android uninstall totals, when available, come from aggregate store reports, not from code running after the app is removed.
• Optional feedback: only when you submit it, we receive your selected outcome, written message and limited support context such as app version, platform, OS version, coarse device family and locale. Feedback is kept separate from analytics. Do not include sensitive information or media details in your message; no video attachment is sent automatically.
• Authentication: where Chrome account features are available, Google sign-in provides an account identifier and email address. Session credentials are used to authenticate account, purchase and restore requests. These are separate from analytics identifiers, and neither credentials nor email addresses are included in analytics events.
• Entitlements and checkout: Android uses Google Play Billing, iOS uses StoreKit, and Chrome may open a hosted Dodo Payments or optional lifetime crypto checkout. Purchase status, product identifiers and provider transaction records are used to provide and restore Pro. Payment details are handled by the payment provider, not included in analytics or logged by the clients.
• Ads on mobile: consent-aware ads may be requested in permitted Free placements. Google Mobile Ads may process an IP-based approximate location, device or advertising identifiers, ad interactions and diagnostic information for ads, measurement and fraud prevention, subject to platform and consent controls. This is separate from the app analytics switch. Pro suppresses ad requests where the product contract applies. Chrome has no ads.

Your analytics choice

Turning analytics off stops future optional usage collection and delivery, clears the local queued analytics and resets the local analytics identity. Turning it on again starts with a new analytics identity. Opting out does not undo records already delivered or disable operations you explicitly request, such as feedback, account access, purchase or restore. We do not send debug or test-build usage into production analytics.

Security and infrastructure

Service requests use HTTPS. Infrastructure providers receive an IP address and basic request information needed to deliver requests, protect the service and apply abuse limits. This may include coarse network location; we do not request GPS location. Analytics identifiers are pseudonymous, not a promise that every network request is completely anonymous.

Retention and deletion

Local jobs, history and temporary files can be cleared through the relevant client. Local analytics queues are bounded and are cleared when you opt out. Delivered analytics and feedback are retained only as needed for product measurement, reliability and support; opting out stops future collection but is not a server-side deletion request. Contact us to request access or deletion of records we can identify, including Chrome account data. Because analytics uses pseudonymous identifiers, we may not be able to locate an installation's records from an email address alone. Purchase, entitlement, webhook and security records are retained only as needed to provide access, handle refunds or disputes, prevent fraud and meet legal obligations.

Third parties and international processing

Google, Apple, Firebase, Cloudflare, Dodo Payments and NOWPayments may process the limited data required for their specific service role under their own policies. We do not sell personal data. Network requests are not a substitute for local media processing.

Information received through Google APIs is used only for the disclosed product features and in accordance with the Chrome Web Store User Data Policy and its Limited Use requirements. We do not use it for unrelated advertising, creditworthiness or lending decisions.

Children, changes and contact

Video Compressor is a general-purpose utility and is not directed specifically to children. We may update this policy when product capabilities, providers or legal requirements change. Privacy questions and deletion requests: sapiest.dev@gmail.com.