Data and access

Who handles the data

Lnk2Drv is the Telegram bot @lnk2drv_bot and the site lnk2drv.com. The data controller is:

• Miatov Mikhail Aleksandrovich, sole proprietor
• Tax number (INN) 434549319259, registration number (OGRNIP) 321774600641423
• Pleteshkovskiy pereulok 3, bld. 2, Moscow 105005, Russia
• Email for requests: info@seo-performance.ru

Questions about data, requests to erase your history and requests for the source code — by email or a message to the bot. The formal wording lives in the legal documents.

What the bot receives and why

Telegram identifier and username

To tell your uploads apart from other people’s and to answer in the same chat. Nothing else.

Access token (OAuth) for your cloud

To put files into your Google Drive or Yandex Disk on your behalf. The bot never sees your account password: you type it on Google’s or Yandex’s page. The token is stored encrypted, and the encryption key is kept apart from the database.

Upload history

File name, size, date, the file’s Telegram identifier (that is how the bot spots a repeat send), the link and the file’s identifier in your cloud. These are needed for the /my command, the “Delete” button, and to keep the same file from being uploaded twice. File contents are not stored along with them.

The files themselves

Files pass through: Telegram → bot server → your cloud, and the server copy is deleted right after the upload. With no cloud connected the file stays on our server and is reachable by link for 7 days, after which it is deleted automatically. File contents are never read, indexed or passed on.

What the bot will not do, on principle

• It does not keep your files and has no file storage of its own.
• It does not read or change anything that was already in your cloud. In Google Drive this is enforced by the drive.file scope: an app can reach only the files it created itself. On Yandex Disk the bot works strictly inside the /Lnk2Drv folder.
• It does not sell data and shows no advertising. The only place your files ever go is the cloud you connected yourself: Google or Yandex, using your access token.
• It does not use your files to train models of any kind.

How long all of this is kept

The access token — until you disconnect the cloud: /accounts → “Disconnect” erases the token from the database and sends the provider a request to revoke it. History rows live longer: deleting a file through /my marks the row as deleted, and disconnecting an account does not erase the history — to have it removed entirely, write to the bot and we will delete it on request. The files themselves stay with you: they are your files in your cloud.

How to revoke access

1. In the bot: /accounts → “Disconnect”. The token is deleted here and revoked at the provider.
2. From Google’s side: the “Third-party apps with account access” page in your Google security settings.
3. From Yandex’s side: the “Apps” section in Yandex ID.

Any one of the three is enough. Once access is revoked, the bot can neither add a file nor delete one — managing the files is left entirely to you.

How public the links are

The link the bot returns is ordinary link sharing in your cloud: anyone who has the link can open the file. Links have no password and no expiry date yet. To stop access, delete the file through /my or in the cloud itself.

Cookies and analytics

The site counts visits with Yandex Metrica, including session recording (Webvisor). The counter starts only after you press “Agree” in the banner: before that not a single request goes to mc.yandex.ru.

• lnk2drv_lang — the language you chose, one year; set only after you choose
• lnk2drv_consent — your answer to the banner, one year
• Yandex Metrica cookies — appear after consent and only then

Refusing works: the “No thanks” button in the banner, and clearing cookies in your browser. The “turn off motion” setting is kept in localStorage and is never sent anywhere.

If you are in the EU, the UK or the US

Where you live decides which rights you get. Under the GDPR: access, rectification, erasure, restriction, objection, portability and a complaint to a supervisory authority. Under US state laws: to know, to get a copy, to correct and to delete — and there is no sale of data and no sharing for advertising here at all. The legal bases, response times and how to ask are set out in the legal documents, together with why the data is processed in Russia and on what ground it is transferred there.

Your own instance

If you would rather not trust someone else’s server, run your own copy: then the tokens, the database and the files in transit all stay entirely with you. You will need a server with a domain and your own OAuth apps at Google and Yandex. We hand over the source code on request — write to the bot.