Delete Your EVdlc Bot Data

If you connected Google Drive and want to withdraw that access, you can do it yourself, directly with Google. You do not need to ask us first.

1. Open Google Account permissions.
2. Find EVdlc Bot in the list of apps with access to your account.
3. Select it, then remove or revoke its access.

Revoking stops future Drive access immediately: the existing access token stops working and it cannot be refreshed, so EVdlc Bot can no longer read any file in your Drive. The stored tokens for that connection are deleted or invalidated, subject to short-lived backup copies that age out automatically.

Revoking does not delete files you already saved into your own Google Drive — those are yours, and you remove them from Drive itself. It also does not, on its own, erase job records that are still inside their retention window. For that, use Option 2.

EVdlc Bot only ever requests the per-file scope https://www.googleapis.com/auth/drive.file, which covers just the files you explicitly selected through Google’s picker.

To have your stored data deleted, send an email to karimimohammdd@gmail.com.

Use a subject line we can recognise, for example: EVdlc Bot Data Deletion Request

In the message, include enough information to locate the account — and nothing more than that. Any one of the following is usually enough:

• your Telegram user ID;
• your Telegram username;
• the Google account email address you connected.

We may need to verify that the request really comes from the account holder, so that nobody can delete somebody else’s data. If verification is needed, we will reply and explain what is required.

Depending on what exists for your account at the time of the request, a completed deletion can cover:

• Connected OAuth tokens — the Google access and refresh tokens held for your connection.
• Stored account associations — the link between your Telegram identifiers and any connected provider.
• Queued jobs — requests still waiting or in progress, which are cancelled and cleared.
• Retained temporary files — any staged file bytes still inside their retention window.
• Eligible operational records — job and error records that are not covered by one of the exceptions below.

Files you copied into your own Google Drive are not affected. They belong to your Google account, and you delete them from Google Drive.

Some information may remain after a deletion request is completed. Where that happens, it is kept to the minimum necessary and is not used for any other purpose:

• information we are required to keep in order to comply with a legal obligation;
• fraud prevention and security records, such as a record that an account was suspended for abuse;
• data that has already been removed through automatic expiry — it is gone, so there is nothing left to delete;
• short-lived backup copies, which are not individually editable and age out automatically on their own schedule.

Requests are processed within a reasonable period after any necessary identity verification is complete. We will confirm by email once the request has been actioned.

Deletion is not instantaneous, and this page does not promise that it is. Cleanup runs asynchronously, and short-lived backup copies age out on their own schedule rather than being erased on demand.

If you have any question about a request, or you have not had a reply, write to karimimohammdd@gmail.com and we will follow it up.