EVdlc Bot Terms of Service
The rules for using EVdlc Bot. In short: it is a paid service; submit only links and files you are legally entitled to access; do not use it to get around access controls; and understand that what it downloads is archived and may be re-delivered to another user who submits the same link. The full terms are below.
Acceptance of Terms
These Terms of Service govern the use of EVdlc Bot and of this website at evdlc.firstvanguardtech.com. Using the service means accepting these terms. A user who does not accept them should not use the service.
These terms work together with the Privacy Policy, which explains what information is processed and how long it is kept. Where a user connects a third-party account such as Google Drive, that platform’s own terms continue to apply in addition to these.
EVdlc Bot is running. Access is granted per account while capacity is scaled up, so availability, limits and features may change.
Description of the Service
EVdlc Bot is a Telegram-based download automation service. A user sends a supported link, or selects a file through a connected provider; the service identifies the source, chooses an appropriate retrieval method, and delivers the resulting file or download result back through Telegram.
EVdlc Bot is built on EVdlc, a separate local desktop download engine. They are different products. Nothing in these terms should be read as describing the behaviour, storage or licensing of the desktop EVdlc engine.
The service is a tool. It does not host a media catalogue, does not curate content, and does not decide what a user is entitled to download. It acts on the specific links and files a user submits, and the responsibility for those submissions rests with the user.
Two things about the service shape everything below and should be understood before signing up. It is a paid subscription service, set out in Subscription and Payment. And it keeps what it downloads: a completed file is copied into private archive channels the operator runs, and may be re-delivered to a different user who later submits the same link, as set out in Archive Copies and Cross-User Reuse.
Eligibility
To use EVdlc Bot, a user must:
- hold a valid Telegram account and comply with Telegram’s own terms, including its minimum age requirements;
- be old enough, under the law that applies to them, to enter into a binding agreement, or have the consent of a parent or legal guardian where that is required;
- not be barred from using the service under any applicable law or sanctions regime;
- not have been previously suspended or removed from the service for abuse.
Access is granted per account while capacity is scaled up, and it may be withdrawn.
Subscription and Payment
EVdlc Bot is a paid service. Download features require an active subscription; where a feature is gated, the bot says so and offers a payment link rather than failing silently.
- A payment link issued by the bot is valid for a set number of uses, normally one, and may be bound to the user it was issued to. Where it is bound, only that user can redeem it. A link must not be shared, resold, or reused beyond the uses it was issued for.
- Payment is taken by the payment provider on the provider’s own systems, under the provider’s own terms. EVdlc Bot never asks for and never receives card details.
- A subscription runs until its expiry date. Unless it is renewed, gated features stop working at expiry; the account itself is not deleted, and data handling continues to follow the Privacy Policy.
- Prices, plans and plan contents may change. A change applies from the next renewal and is not applied retroactively to a period already paid for.
- Paying grants access to the service, not a right to any content. Every rule in Authorised Use Only applies identically to a paying user, and payment is never a defence to a breach.
- Operational limits still apply to a paid subscription. A plan buys access under the limits described in Download Limits, Queues, and File Availability, not a guaranteed volume, speed or success rate.
Refund requests are considered case by case at karimimohammdd@gmail.com, and any non-waivable statutory refund or cancellation right a user has where they live is unaffected by this section. Access suspended or terminated for a breach of these terms under Suspension and Termination is not refunded for the unused period.
User Responsibilities
Each user is responsible for what they submit and how they use it. That means:
- securing your own Telegram and Google accounts, including the devices you sign in from;
- checking that you are legally entitled to access and download whatever you submit;
- choosing carefully which Google Drive files you select through Google’s picker, because that selection is what grants access;
- complying with the terms of the third-party platforms a link points to;
- keeping your own copies of anything you need to retain — the service does archive what it downloads, for its own operational reasons, but it gives no undertaking to keep any particular file or to keep it retrievable;
- understanding, before you submit a link, that the file retrieved from it is archived and may later be delivered to another user who submits the same link;
- reporting suspected security problems privately to karimimohammdd@gmail.com.
Authorised Use Only
EVdlc Bot may be used only to retrieve links and files that the user is legally authorised to access and download. This is the central rule of the service, and the rest of these terms follow from it.
Specifically, a user must not use the service to:
- bypass DRM, technical protection measures, paywalls, subscription requirements, geographic restrictions, account permissions or any other access control;
- access content that the user is not permitted to access, including content behind someone else’s account;
- attempt to reach another person’s private Google Drive files, or any file that person has not deliberately shared with the user;
- retrieve content whose distribution is prohibited by law in the user’s jurisdiction.
The service does not implement, and will not implement on request, any feature whose purpose is to defeat an access control. Requests of that kind are refused, and repeated attempts are treated as abuse.
Copyright and Intellectual Property
EVdlc Bot must not be used to infringe copyright or any other intellectual property right. Submitting a link does not transfer any right in the content it points to, and the service grants no licence to material it retrieves on a user’s behalf.
Before submitting a link, a user should be satisfied that at least one of the following applies: the user owns the content; the rights holder has permitted the download; the content is offered under a licence that allows it; the content is in the public domain; or the download is otherwise permitted by law, including any personal-use or fair-dealing exception that genuinely applies in the user’s jurisdiction.
Rights holders who believe the service has been used to infringe their rights can write to karimimohammdd@gmail.com with enough detail to identify the material and the complaint. Credible reports are investigated, and accounts used for infringement may be suspended or terminated.
The EVdlc Bot name, this website, and the software and design that make up the service remain the property of their respective owners. These terms grant a limited, personal, revocable, non-transferable permission to use the service as intended, and nothing more.
Prohibited Conduct
The following are not permitted:
- submitting or distributing malware, ransomware, exploit payloads or other harmful code;
- submitting content that is illegal, that depicts the abuse or exploitation of any person, or that violates a third party’s rights;
- harassment, threats, impersonation, or using the service to target another person;
- abusive automation: scripted flooding, mass job submission, or any use designed to consume a disproportionate share of capacity;
- denial-of-service workloads, deliberate overload, or attempts to degrade the service for other users;
- probing, scanning, reverse engineering or attacking the service, its infrastructure, or the accounts of other users, except for a good-faith security report made privately to the address above;
- circumventing rate limits, quotas, size limits, suspensions or any other technical or administrative restriction;
- reselling, sublicensing or commercially redistributing access to the service without permission;
- misrepresenting your identity or authorisation in order to obtain access to content or to the service.
Google Drive and Third-Party Services
Connecting Google Drive is optional. When a user chooses to connect it, EVdlc Bot requests one Drive scope, https://www.googleapis.com/auth/drive.file, which grants access only to the files the user explicitly selects through Google’s own picker, plus the files the app creates or uploads at the user’s request. Broad access to a user’s Drive is not requested.
Alongside it, EVdlc Bot requests the standard sign-in scopes openid userinfo.email userinfo.profile, which identify the account being connected so the connection can be managed and disconnected. That is 4 Google scopes in total, and they are listed in full in the Privacy Policy.
A user may withdraw that access at any time from Google Account permissions. How Google data is handled is described in the Privacy Policy.
EVdlc Bot is independent from Telegram, Google, and every other platform a link may point to. It is not endorsed by, affiliated with, or certified by any of them, and no approval, verification or trust badge from any third party is claimed.
Third-party platforms control their own services. They can change their terms, their APIs, their rate limits, their availability and their access rules at any time, with or without notice. When they do, a source that previously worked may stop working, and EVdlc Bot may have to restrict or remove support for it. That is outside the service’s control and is not a breach of these terms.
Download Limits, Queues, and File Availability
Capacity is finite, so the service applies operational limits. These may include limits on file size, request rate, the number of concurrent jobs, a queue position or waiting time, total usage over a period, and which sources are supported. Limits may differ between users and may change without notice, particularly while capacity is being scaled up.
A job can fail or be refused for reasons that have nothing to do with the user: the source may be unavailable, the link may have expired, the third-party platform may block or throttle the request, the content may exceed a limit, or the source may require an access control the service will not bypass.
Availability of a past result is not guaranteed in either direction. Temporary working files expire and are cleaned up on the schedule published in the Privacy Policy, while a completed file is archived as described in Archive Copies and Cross-User Reuse. An archived copy may nevertheless be removed at any time — on request, following a rights-holder complaint, for a legal reason, or as ordinary housekeeping — and a channel holding it may itself become unavailable. Users should download and keep anything they want to retain. EVdlc Bot gives no undertaking that a completed result will remain retrievable later, and must not be relied on as a backup or as permanent storage.
Temporary Storage
Completing a job requires the service to hold file content on its own infrastructure while the content is retrieved, prepared and delivered. This section covers that working storage only. What happens to a file once it has been delivered is covered by Archive Copies and Cross-User Reuse, and it is not the same thing.
Temporary working files — partial downloads, staging files, and the residue of a cancelled or failed job — become eligible for deletion when a job completes, is cancelled, fails or expires, and are then removed by an asynchronous cleanup process within the retention window published in the Privacy Policy. Deletion is prompt and bounded, but it is not instantaneous, and it does not mean the delivered file has ceased to exist.
Because content is processed on the service’s infrastructure, EVdlc Bot does not provide end-to-end encrypted storage. Users should not use it for material that must never be readable by an intermediary, and should not use it for material they need to keep away from other users of the service.
Archive Copies and Cross-User Reuse
When a download completes, EVdlc Bot copies the result into one or more private archive channels it operates on Telegram, and keeps those copies indefinitely. This is deliberate: mirroring protects a file against the loss of any single channel, and an archived file is re-sent rather than downloaded a second time.
By using the service, a user accepts that:
- a file retrieved from a link they submit is retained by the service after it has been delivered to them;
- that file may be delivered to a different user who later submits the same link, without being downloaded again — so content retrieved from a link is not private to whoever requested it first;
- the operator may remove, replace, or refuse to re-deliver any archived copy at any time and without notice, including in response to a rights-holder complaint, a legal requirement, an abuse finding, or ordinary housekeeping;
- no undertaking is given that an archived copy will still exist, or still be retrievable, at any later date.
Content that required the user’s own authentication is excluded from all of this. A file selected through Google’s picker is used only for the request of the user who selected it: it is not archived, and it is never re-delivered to anyone else.
A user may ask for an archived copy to be removed, through the data deletion page. Removal stops future re-delivery from the archive. It cannot recall a copy that has already been sent to someone, and it does not affect the original source.
Security and Abuse Prevention
To keep the service usable and safe, EVdlc Bot may apply rate limits and quotas, queue or delay requests, refuse a submission, monitor for patterns that indicate abuse, and keep the operational records described in the Privacy Policy. These measures exist to protect users and capacity, not to inspect user activity for any other purpose.
Attempts to evade these measures — rotating accounts to escape a limit, automating around a block, or interfering with abuse controls — are themselves a breach of these terms.
Good-faith security research is welcome, provided it is non-destructive, does not target other users’ data, does not degrade the service, and is reported privately to karimimohammdd@gmail.com before it is published.
Service Changes and Availability
EVdlc Bot is provided on an “as available” basis. It may be modified, suspended, restricted or discontinued, in whole or in part, at any time. Features may be added, changed or removed, supported sources may come and go, and limits may be adjusted.
No promise is made that the service will be uninterrupted, error-free, available in any particular territory, or capable of completing any particular download. Maintenance, outages, capacity limits, upstream failures and third-party changes all affect availability.
The service is under active development. Users should expect interruptions, incomplete features, and changes that are not announced in advance.
Suspension and Termination
A user may stop using EVdlc Bot at any time, disconnect Google Drive as described above, and request deletion of stored data through the data deletion page.
Access may be limited, suspended or terminated where there is a reasonable basis to believe that these terms have been breached, that the service is being used unlawfully or abusively, that the security or stability of the service is at risk, or that action is required by law. Where it is practical and appropriate, a warning will be given first; for serious or repeated breaches, it may not be.
On termination, the permission to use the service ends immediately, and any remaining paid period is forfeited where termination follows a breach. Data handling after termination follows the retention rules in the Privacy Policy: in particular, ending use of the service does not by itself remove archived copies, which are removed on request or at the operator’s discretion. The sections of these terms that by their nature should survive — including intellectual property, disclaimers, limitation of liability and indemnity — continue to apply.
Disclaimer of Warranties
To the fullest extent permitted by applicable law, EVdlc Bot and this website are provided “as is” and “as available”, without warranties of any kind, whether express, implied or statutory. This includes, without limitation, any implied warranty of merchantability, fitness for a particular purpose, title, accuracy or non-infringement.
In particular, no warranty is given that:
- the service will be uninterrupted, timely, secure or error-free;
- any specific link, source or file will be supported or retrievable;
- a retrieved file will be complete, accurate, uncorrupted, or free of content the user did not expect;
- an archived copy will remain available, or remain retrievable, at any later date;
- a subscription will grant access to any particular source, feature or volume of downloads;
- a user’s intended use of retrieved content is lawful in their jurisdiction — that assessment is the user’s responsibility.
Some jurisdictions do not allow the exclusion of certain warranties. Where that is the case, the exclusions above apply only to the extent permitted by applicable law, and any non-excludable rights a user has are unaffected.
Limitation of Liability
To the extent permitted by applicable law, EVdlc Bot and the people who operate it are not liable for indirect, incidental, special, consequential, exemplary or punitive damages, nor for loss of profits, revenue, goodwill, data or files, business interruption, or the cost of substitute services, arising out of or connected with the use of, or inability to use, the service.
This includes, without limitation, loss or damage arising from:
- a failed, incomplete, delayed, cancelled or corrupted download;
- the deletion or expiry of a temporary file under the published retention schedule;
- the removal, loss, or unavailability of an archived copy, or of a channel holding one;
- the delivery of a file to another user under the reuse described in these terms;
- a change, outage, restriction or policy decision by a third-party platform;
- content submitted by a user, or the consequences of retrieving it;
- unauthorised access to a user’s own Telegram or Google account.
To the extent permitted by applicable law, total aggregate liability for any claim relating to the service is limited to the amount the user actually paid for the service in the twelve months before the claim arose, and is nil where nothing was paid. Nothing in these terms excludes or limits liability that cannot lawfully be excluded or limited, and any non-excludable rights a user has under applicable law remain unaffected.
Indemnity
Where enforceable, and to the extent permitted by applicable law, each user agrees to indemnify and hold harmless EVdlc Bot and the people who operate it from claims, liabilities, damages, losses and reasonable costs arising from that user’s:
- breach of these terms;
- submission of links or files they were not authorised to access or download;
- infringement of a third party’s rights;
- unlawful or abusive use of the service.
This obligation applies only to the extent the claim results from the user’s own acts or omissions, and only where such an indemnity is enforceable under the law that applies to that user.
Changes to the Terms
These terms will be updated as EVdlc Bot develops. The current version is always published at https://evdlc.firstvanguardtech.com/terms, and the last-updated date shown at the top of this page is revised when a change is made.
Where a change materially affects a user’s rights or obligations, reasonable steps will be taken to highlight it, including through the bot where that is practical. Continuing to use the service after a change takes effect means accepting the revised terms. A user who does not accept them should stop using the service and may request deletion of their data.
Contact
Questions about these terms, reports of abuse, rights-holder complaints and security reports can be sent to karimimohammdd@gmail.com.
Related pages:
- Privacy Policy — what information is processed and how long it is kept.
- Delete your data — how to revoke Google access and request deletion.