Links and public metadata
When you submit a link, it is sent to VidTote’s server for lookup of public source metadata. Lookup can make limited requests to Facebook and follow supported public redirects. The source can receive the server’s connection information.
The submitted link, temporary media addresses and metadata are kept in processing memory and short-lived memory caches, not a persistent link history. Cache lifetime is at most 60 seconds and may be shorter when an address expires or its lifetime is unknown.
Application logs and analytics do not retain pasted links, signed addresses, media identifiers, tokens, media titles or file names. Do not paste a private address or credentials.
The video travels directly to your browser
VidTote’s server does not fetch, store or relay video bytes. A video save action connects your browser directly to Facebook’s CDN. That provider can receive network information, including your browser’s IP address, and handles it under its own policies.
Temporary save tasks and addresses stay in browser memory; they are not placed in a persistent media history, cache database or VidTote page URL. No video is automatically downloaded merely because a result is displayed.
A browser download, an opened file or a system share action can create a file on your device. The browser and operating system control that copy; cancelling on this page may not remove a partial file already created by the browser.
Separate audio and thumbnails
When you request an available MP3 or thumbnail, VidTote fetches the permitted small source and processes it within bounded memory. Audio conversion uses a separate confirmed audio track, never a downloaded video.
Media input and output are not written to the server’s disk. Time, size and capacity limits can stop processing. The persistent daily budget records allowance reservations and byte accounting, without a link, token, content identifier or file name.
First-party site statistics
VidTote records page views, estimated unique visits, crawler counts and controlled lookup or saving outcomes to operate and understand the site. It does not use a visitor cookie for this first-party counting.
Connection information is processed transiently to receive requests and derive a rotating daily visitor hash. The statistics and application logs do not store your IP address or original user-agent text. The daily hash is not sent to Google.
Raw statistical events are retained for 14 days and daily aggregates for 90 days. Logged routes and outcome fields are fixed categories, rather than user-entered links or arbitrary error text.
Browser-reported bytes and completion signals are separate from server-delivered small-file bytes. Clicks, stream completion and handoffs do not prove operating-system saving or gallery placement. First-party counts and Google Analytics counts are not added together.
Optional Google Analytics
On configured production pages, Google Analytics 4 follows regional privacy controls. In regions that require prior consent (the EEA, the UK, Switzerland and similar conservative jurisdictions) or when your region cannot be determined, it loads only after you choose Allow in the footer’s Analytics settings. In other recognized regions it is on by default, and you can turn it off at any time in the same settings; it stays off if your browser blocks storage. Before consent where consent is required, after you turn it off and on preview pages, the site makes no Google Analytics requests and sets no Google Analytics cookies.
Your approximate region is read from this site’s own Cloudflare edge, not from Google. Do Not Track and Global Privacy Control are respected in every region: when either applies, Google Analytics remains off even if a preference was saved earlier. The download tool works independently of your analytics choice.
The only Google event sent is a page view using the site’s static page title and controlled path. Query strings, fragments and referrer paths are removed. Tool inputs, media addresses, file names, titles, quality choices and download actions are not sent to Google.
When Google Analytics is active, by your choice or by the regional default, Google receives connection information through its client service, which can include your IP address, and may process data across borders. Google Analytics is not described as anonymous or as never receiving an IP address.
Preference storage and withdrawal
An analytics preference can be stored in your browser for up to 180 days. When Google Analytics is active, its cookies have a configured lifetime of up to 180 days. Google’s user and event retention is configured to two months; aggregate reports can remain longer.
Open Analytics settings in the footer to decline, turn off or withdraw consent at any time. This stops subsequent analytics transmission and clears cookies controlled by this integration where accessible; it cannot recall data already sent to Google.
Preview or unconfigured pages show optional analytics as disabled and do not offer a control that could enable it. Your input and download task are not cleared or blocked by an analytics decision.
Data minimization and safe requests
The service accepts supported public links and checks source addresses before processing them. It does not accept account cookies, authentication headers, arbitrary proxy destinations or a request to transfer video through the server. To limit abuse, the server keeps short-lived request counters in memory, keyed by a daily salted hash of the connection address; these counters are not written to disk, logs or statistics.
Transport protections and limited processing reduce exposure but do not make any network service risk-free. Keep private information out of the input and any report, and manage downloaded files on your device yourself.
Questions and revisions
When a receiving address is configured, you can use the contact page for privacy questions, including questions about information you chose to send in a report. Sending email also involves your email provider and the receiving email service; this policy does not claim control over their processing.
The contact page states when an inbox is not enabled. Do not send a password, account cookie, private video link or signed media address. The revision date below reflects this policy’s content update.
Questions
Does turning off Google Analytics stop all site counting?
No. First-party operational statistics are separate and do not use a visitor cookie. Turning off optional Google Analytics does not prevent you from using the tool.
Updated