One engine, many sources
The EVdlc engine handles a wide range of sources. The bot exposes that engine through Telegram, so you do not have to pick a tool yourself.
Secure link-to-file automation
EVdlc Bot
Send a link. Get the file back in Telegram.
EVdlc Bot is a Telegram bot that downloads files for you. You send it a link — a video, a shared file, or a direct download — and EVdlc Bot identifies the source, downloads the file, reports progress back in the chat, and returns the finished file to you. There is nothing to install and no account to create.
If you connect a Google account, EVdlc Bot can also save a finished download straight into your Google Drive instead of sending it through Telegram.
Access is granted per account while capacity is scaled up. Use the support address below to request access.
View our privacy practices- User-selected Google Drive files only
- No advertising trackers
- Temporary processing
- Clear data controls
Data use
What EVdlc Bot asks for, and why
EVdlc Bot asks for the least it can. Each item below exists only to carry out a download you asked for.
Your Telegram account
Your Telegram user and chat ID, so EVdlc Bot knows who asked for a download and where to send the finished file back.
The links you send
The URL you submit, so EVdlc Bot can identify the source and download the file it points to.
Google Drive, only if you connect it
The
drive.filepermission — the narrowest Drive scope Google offers. It covers only files you pick yourself and files EVdlc Bot saves for you. It cannot browse or read the rest of your Drive, and it never touches Gmail, Contacts or Calendar.Signing in with Google
When you connect Google, EVdlc Bot also uses the standard sign-in scopes
openid,userinfo.emailanduserinfo.profile. They identify which Google account the Drive connection belongs to — your account’s email address and basic profile details — so a download goes to the right Drive and you can disconnect it later.
Full detail, including how long anything is kept and how to have it deleted, is in the EVdlc Bot Privacy Policy.
Overview
What EVdlc Bot is
This site is about EVdlc Bot, the Telegram bot. It is built on top of the EVdlc engine, a separate local downloader — that engine is a component, not the app described here.
Delivered, not just downloaded
A finished job comes back as a file or a clear result, or is placed in your Google Drive if you have connected one.
Least privilege by design
Google access is limited to the drive.file scope, which covers only the files you pick and the files the service creates for you.
Honest about limits
Availability depends on the source and its rules. The service does not attempt to bypass DRM, paywalls, or access controls.
How it works
Four steps, start to finish
Send a supported link
You paste a link into a chat with EVdlc Bot. No installation, no browser extension.
The source is detected
EVdlc Bot identifies the source and starts the download workflow that matches it.
Progress is reported back
The bot reports progress and delivers the resulting file or download result.
Temporary data is removed
Temporary processing data is removed according to the published retention policy — 24 hours at most.
Supported sources
The link types in scope
Each category below is supported. Categories that are not part of the public bot are not listed at all.
Video and media sites
Available
YouTube plus the wider set of supported media sites handled by the yt-dlp engine.
Direct HTTP/HTTPS files
Available
A plain file URL that responds with a downloadable file over HTTPS.
Google Drive
Available
Only the files you explicitly pick through Google's own picker are ever read.
Telegram links
Available
Public Telegram post and file links you are able to open.
MEGA
Available
Shared MEGA links, including links that carry a decryption key.
Dropbox
Available
Shared Dropbox file links.
OneDrive and SharePoint
Available
Shared OneDrive and SharePoint file links.
Supported social media
Available
Public posts on social platforms covered by the same media engine.
Google Drive
Google Drive access, limited by design
EVdlc Bot asks for the narrowest Google Drive permission that exists. It is scoped to the files you choose, and nothing else.
The only Google Drive permission requested
https://www.googleapis.com/auth/drive.file
- EVdlc Bot will use the Google Drive picker, so a file is only ever involved after you select it.
- This permission covers only files you explicitly select, open, or share with EVdlc Bot, plus files the service creates or uploads at your request. It does not allow browsing or reading arbitrary unselected files across your Drive.
- Selected files are accessed only to carry out the download or delivery you asked for.
- Google OAuth tokens are confidential credentials. They are never displayed publicly and never stored by this website, and the EVdlc Bot backend is required to protect them at rest before it handles a single account.
What EVdlc Bot can access
- Files you explicitly select through Google's own picker
- The metadata needed for those selected files, such as name, size and type
- The content of a selected file, only where the transfer you asked for requires it
- Files EVdlc Bot itself creates or uploads to your Drive at your request
What EVdlc Bot cannot access
- Arbitrary files in your Drive that you did not select
- Your entire Google Drive library
- Gmail, Contacts, Calendar, Photos, or any unrelated Google service
- Your Google account password or your Google account settings
Privacy and security
Built to hold as little as possible
The website you are reading has no login, no database and no tracking — that part is true today. The rest are the commitments the bot must meet before it launches.
No hidden trackers
This website loads no analytics, no tracking pixels, and no third-party scripts, and it stores no request telemetry.
No sale of personal data
Your data is never sold or rented, and never shared with ad networks.
No advertising profiles
Nothing you send is used to build an advertising or behavioural profile.
Least-privilege Google scope
Only the drive.file scope is requested, covering the files you explicitly pick.
Temporary file processing
Temporary files are removed no later than 24 hours after successful delivery, cancellation, failed-job cleanup, or expiry.
You stay in control
You can revoke Google access at any time, or ask for your stored data to be deleted.
Support
Questions, problems, or a deletion request
Email the address below. Please include enough detail to identify the issue, and never send passwords, verification codes, OAuth tokens, session files, or private keys.
Messages are reviewed and answered as quickly as reasonably possible. No specific response time is guaranteed.