Privacy Policy
Video2Any converts videos on your machine. This page lists everything that ever reaches us, why it does, and how long we keep it. The short version: by default nothing you convert leaves your device. Four things can, and each of them only because you asked for it by name. Beyond that we collect only what accounts and billing need to work.
Your videos stay on your device
Uploaded files, direct file links, screen recordings, and everything the converter produces (slides, decks, frames) are processed inside your browser tab. There is no video upload endpoint. Close the tab and it is all gone.
What can leave, and only if you ask for it
Three features send something. None of them runs on its own: each is a button you press, on one deck at a time, and each is described where you press it.
Share links
If you create a share link, that one exported deck is stored on our servers so the recipient can fetch it. It is encrypted in your browser before it is uploaded, with a key that is generated on your machine and placed in the part of the link after the # — which browsers never transmit. We receive ciphertext and its size. We do not receive the key, the file name, or anything about what is inside. We cannot open it, and neither can anyone without the full link.
A share expires after at most thirty days, sooner if you chose a shorter window or a download limit, and you can delete it at any time from your account. There is no setting that makes one permanent: a public link holding your slides has to end. Expiry and deletion remove the stored object, not just the link. Nothing is shared unless you click the button.
Saved decks
Choosing Save to library stores that deck's slides on our servers so you can open it on another machine. Unlike a share link this is stored in the clear, and we are telling you rather than implying otherwise: a deck encrypted with a key that only ever existed in one browser is a deck you could not open on the machine that never held the key, which is the whole reason to save it. The source video never travels, only the finished slides. If a deck has a transcript, its text is indexed so you can search across your own decks; nobody else's search reaches it. Deleting a deck deletes the stored files and the index, not just the listing.
Cloud transcription
Transcription runs in your browser by default and nothing leaves. If you chooseIn the cloud instead, the audio track alone is extracted in your browser and uploaded, and a third-party speech-to-text provider fetches it through a link that expires. The video itself is never uploaded. The audio is deleted as soon as the provider is finished with it, whether it succeeded or not, and we keep no copy of the transcript: the text goes back to your browser. We record only the length of audio submitted, to enforce the monthly allowance.
Reading the text on a slide
Editable slide exports have to read the text off each slide, and that reading happens in your browser, for everyone, always. Nothing about a slide is sent anywhere. There used to be a more accurate reader that ran in the cloud on paid accounts; it was switched off on 28 August 2026, and with it went the last path in this product that sent any part of a slide to a third party.
The browser extension
The Video2Any extension turns the video already playing in a tab into slides. It holds standing access to no website. When you click its toolbar icon, Chrome grants it access to that one tab for that one moment, and it reads still frames from the video element on the page. That is the only thing it can do.
No video is downloaded, assembled, or saved. What crosses from the extension to video2any.com is JPEG frames — there is no message in the protocol between the two halves that could carry a video file, and no code in the extension that could build one.
Nothing leaves your device. The extension makes no network requests of its own: no analytics, no telemetry, no server of ours it reports to. The frames travel from the tab holding the lecture to the video2any.com tab in the same browser, where they are turned into a deck on your machine, exactly as an uploaded file is. They reach our servers only if you then choose Save to library or create a share link, and those are covered above.
What it remembers. While a capture is running, the extension keeps the identity of the tab it came from — the tab id, the page title, the video's length, and the host. It needs this because Chrome shuts a background worker down about thirty seconds after it goes idle, and an hour-long lecture outlives that many times over; without it, scrubbing your deck's timeline would be told the lecture tab was gone while it sat in front of you. It is held in session storage, which is cleared when you close the browser and is never written to disk. Nothing is kept about any page you did not click the icon on, and no list of pages you have visited is built at any point.
What we collect, and why
Account data. Creating an account stores your email address and a display name. We store no password — signing in sends a six-digit code to your address, and the code is kept only until it is used or expires. Signing in with Google instead stores the name, email address, and account identifier that Google provides. We use this data only to authenticate you and to attach your plan and quotas. Session cookies keep you signed in; we set no advertising or analytics cookies. When you create an account we also record, once, how you found us: the referring site, any campaign tag, and the page you landed on.
Subtitles. Subtitles are generated in your browser by default and nothing about them reaches us. Cloud transcription is the alternative you can choose instead, described above.
Billing. Payments are processed by Stripe. Your card details go to Stripe, not to us; we store only your subscription plan, its status, and the Stripe identifiers needed to match a payment to your account. Stripe's handling of payment data is covered by Stripe's own privacy policy.
Contact form. A message through the contact page stores the topic, your email address, the message text, your account ID if you are signed in, and your IP address. The IP address exists to rate-limit spam and for nothing else.
Operational logs. The service runs on Cloudflare. Standard infrastructure logs (IP address, request path, timing) exist for reliability and abuse prevention, on Cloudflare's usual terms.
Product usage events. To see which features are actually used, the converter reports small usage events: the kind of source (upload, screen recording, or link), the video's duration, how long extraction took, how many slides came out, and the export format. We also record which buttons and menu items are clicked (the button's own label and the page it is on) and, when something breaks, the browser's error message so we can fix it. Never the file itself, its name, its frames, or the link — tied to your account if you are signed in and to a random anonymous id if not.
Where you arrived from. Once per browser, on the first visit, we record the site that linked you here, any campaign tags in the address, and which page you landed on. That is how we tell whether a post, a search engine or a link somewhere sent anybody — it is the same short list of facts a server log would hold, kept against the same random anonymous id, and it is written once and never updated, so coming back later does not add a row. It says nothing about you and nothing about your files.
Which pages were opened. Each time a page here renders, we add a row holding the path (never the query string), the country your network resolves to, and the same random anonymous id. Counting rows tells us how many pages were read; counting distinct ids tells us how many browsers read them. We also store a short label for the crawler your browser identified itself as, when it did — a name likegooglebot or gptbot, and nothing at all for an ordinary browser. We keep the label rather than the full browser string on purpose: the full string is one of the details a browser fingerprint is built from, and a name is all we need to separate people from the software that reads the site on its own.
What you tell us on purpose. Two things in the app ask you a question. After an export, one row asks whether the slides matched the video — missing, right, or extra — and stores your answer with the settings that produced that run: the video's length, the number of slides, the density and sampling mode. No account is needed, and nothing about the file itself is recorded. Separately, a feedback form asks which features you would use and what gets in the way, with a box for anything else; those answers are stored against your account, because the full-length run we thank you with has to land somewhere.
What we do not do
No analytics scripts, no advertising networks, no tracking pixels, no fingerprinting, and no selling or renting of any data. Open the network tab while you convert; that is the audit.
Google user data
If you sign in with Google, we receive your name, email address, and Google account identifier, and we use them only to create and authenticate your Video2Any account. We do not share, transfer, or sell Google user data, and we request no access to anything else in your Google account. You can revoke Video2Any's access at any time at myaccount.google.com/permissions.
Stored on your device
Preferences (theme, language, sidebar state) live in your browser's local storage. None of it is transmitted to us, and clearing your browser data removes it.
Retention and deletion
Account data is kept while your account exists. Usage events are kept to operate rolling quota windows. Contact messages are kept as long as needed to reply and to keep rate-limiting honest. To delete your account and the records tied to it, send a request through the contact page from the email on the account; we delete the account, its sessions, and its usage history.
Who else sees data
Only the processors named above: Cloudflare (hosting, database and file storage), Stripe (payments), Alibaba Cloud Model Studio (speech-to-text, and only the audio you send to it deliberately), and Google (sign-in, if you choose it — nothing else, since cloud text recognition was switched off). Each receives the minimum described here. Beyond that, we disclose data only if the law requires it.
Children
Video2Any is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will delete it.
Changes
When this policy changes, the date at the top moves, and material changes are announced in the product before they take effect.
Contact
Questions about this policy go through the contact page or by email at support@video2any.com; a human reads every message.