Privacy Policy
Last updated: September 4, 2026
This Privacy Policy explains how vidosick.com (“VidoSick,” “we,” “us,” or “our”) handles information when you use our website and browser tools (the “Services”).
Questions? Email contact@vidosick.com.
1. What VidoSick is
VidoSick provides free, browser-based helpers for video work, for example frame/time calculators, aspect-ratio tools, and a video-to-GIF / WebM converter. Most processing happens on your device in your browser. We do not require accounts, and we do not operate a user login system.
2. Information we collect
2.1 Information you send us
If you email contact@vidosick.com, we receive whatever you include in that message (typically your email address and the content of your inquiry). We use that only to respond and follow up as needed.
2.2 Information collected automatically
Like most websites, our hosting provider and analytics tools may process technical data when you visit, such as:
- IP address (or a truncated/approximate form)
- Browser type, device type, and operating system
- Pages viewed, approximate location (from IP), and referral URL
- Timestamps and basic performance/diagnostic signals
We use Google Analytics to understand aggregate site usage (for example which tools are popular). Google may set cookies or similar technologies. See Google’s Privacy Policy for details on how Google processes data.
We use Sentry for client-side crash and error monitoring so we can detect and fix browser engine failures. When an unexpected error occurs, Sentry receives technical diagnostic data (such as browser version, operating system, and stack traces). Error reports are automatically sanitized in your browser before transmission to redact any file names or file paths, ensuring your private file details are never sent. See Sentry’s Privacy Policy for details.
2.3 Files you process in browser tools
Tools such as the video-to-GIF converter, audio extractor, and container converter run locally in your browser. Videos and other files you select are not uploaded to our servers for conversion. Most operations run directly on your device using built-in browser capabilities (WebCodecs) without downloading an engine; where an auxiliary engine (such as ffmpeg.wasm for GIF export or legacy containers) is required, it is downloaded directly to your device without sending your media files anywhere.
The subtitle burn-in tool works the same way. Video and subtitle files you choose are processed on your device using WebCodecs and never uploaded. The caption fonts it offers are downloaded from this site itself, not a third party, only when you pick one, and that download never includes anything about the file you are working on.
The transcription tools (video/audio to text, subtitle generation) also run on your device. The video or audio file you transcribe is never uploaded. The first time you use one of these tools, your browser downloads a speech-recognition model (a one-time download, cached afterwards) from Hugging Face (huggingface.co) rather than from this site itself, which is why it is called out separately from the caption fonts above. The code that runs the model is fetched from the jsDelivr CDN (cdn.jsdelivr.net) at the same time. Both are third parties and will see your IP address, as any site you load a file from does; neither download includes anything about the file you are transcribing.
We do not receive the contents of files you convert unless you separately choose to send them to us (for example by email).
As you use a tool it records a small number of anonymous analytics events: when a file is accepted, when a conversion starts, when it finishes or fails, and when you download the result. Each event names the tool and the settings you chose (for example “subtitle converter, SRT to WebVTT” or “GIF, 480 px wide, 15 fps”), and, for a conversion that ran, which engine did the work.
This is how we tell a page that gets visits apart from a tool that actually gets used, and how we find out that a tool is failing for real people instead of waiting to be told. When something fails we record a general category (“ran out of memory”, “format not supported”) and never the error text itself, because error messages from a conversion engine often quote the name of the file being converted.
These events never include your file’s name, contents, size, or duration, and no part of your file is sent with them.
3. How we use information
We use the limited information above to:
- Operate, secure, and improve the website and tools
- Understand aggregate traffic and feature usage
- Respond to support or contact requests
- Comply with applicable law
We do not sell your personal information. We do not use your media files for advertising or training models.
4. Cookies and similar technologies
We and our analytics provider may use cookies or local storage for analytics and basic site function (for example remembering preferences in your browser if a tool stores them locally). You can block or delete cookies through your browser settings; some analytics may then be limited.
We do not currently offer a separate on-site cookie preference panel. Browser controls and, where available, Google Analytics opt-out extensions or settings remain the primary ways to limit tracking.
5. Sharing
We may share information only with:
- Service providers that help us run the site, for example website hosting (Cloudflare Pages), analytics (Google Analytics), and error monitoring (Sentry)
- Authorities when required by law or to protect rights, safety, or the integrity of the Services
We do not share your uploaded media with third parties because we do not receive it for processing.
6. International processing
Our site is hosted and our providers may process data in the United States and other countries. If you access the Services from elsewhere, information may be transferred to those locations.
7. Retention
Contact emails are kept only as long as needed to handle your request and for ordinary business records. Analytics data is retained according to our providers’ settings and policies. Local tool state (if any) remains on your device until you clear it.
8. Children
The Services are not directed to children under 13 (or the minimum age required in your region). We do not knowingly collect personal information from children. If you believe a child has provided us information, contact us and we will delete it.
9. Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, or restrict certain personal information, or to object to certain processing. Because we do not run user accounts, the main personal information we hold about you is typically what you email us and what analytics collects.
To make a request, email contact@vidosick.com. We will respond as required by applicable law. You can also control cookies via your browser and review Google’s tools for analytics opt-out.
10. Security
We use reasonable technical and organizational measures appropriate for a static/client-side website. No method of transmission or storage is completely secure. For media tools, keeping processing on your device reduces the need to send files to us.
11. Third-party links and CDNs
The Services may load scripts or assets from third parties (for example analytics or fallback engine components). Those parties have their own privacy practices. We are not responsible for sites or services we do not control.
12. Changes
We may update this Privacy Policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the Services after an update means you accept the revised policy.
13. Contact
Email: contact@vidosick.com
Website: https://vidosick.com