Parsing a personal account?

Question

Parsing

The question is technical and legal.
Does the user have any personal account (for example, MTS Internet Assistant)
1. parse the page with information about his balance in order, for example, to display it as a widget;
2. by sending a specific request, say, disable / enable any service?

Answer 1

Something I have not seen in the user agreements of such restrictions. And technically, this is no different from using a personal account through a browser.
Consider that everything is chocolate - if someone does not like it, then you will know it.

Answer 2

MegaFon itself allows. There is even a type API. The user has the right to choose whether to enable or disable the possibility of automatic access to the system.

Answer 3

In my opinion, it all depends on the frequency of operation. If you update the information every 2 seconds, then most likely you will be asked - "why?".

Answer 4

So I’m wondering if anyone has come across a similar issue, because the user agreements really don’t say a word about this. And as you noticed, from the server side it will be indistinguishable that the browser is the client program.

Answer 5

I would like to hear from a service representative. Will there be pitfalls in the legal field?

Answer 6

Let's say the service doesn't have an API.

Answer 7

Everything that is not forbidden is allowed. If there is no explicit prohibition in the user agreement, then it is possible.

Answer 8

Wash of course you can. This is your account, log in to it even from a browser or from the console. What is the difference to the personal account server? He won't even understand. Write to support. Everything will be clear.

Answer 9

Parse the page with _your_ personal means or by providing your login/password to a _third party_ service?
We ask such a question, because they themselves did a similar service :)
There are no problems with _Own_, everything is legal. To a third-party service - depends on the operator, somewhere it is forbidden, somewhere it is allowed, somewhere you can get around the legal restriction if the operator user does not provide a login / password to the service directly, but buys a monitoring service from him and installs the monitoring script provided there (the difference between - fill in hosting data to manage Yandex.wallet and provide the left service with your data to manage Yandex.wallet).

Answer 10

1. We read offers with operators to whose offices access will be made, if there is nothing to say about transferring your data to third parties, then you can make at least a web service, at least a program that will go to the telecom operator for the user and look into his personal account.
2. When installing the program or when registering in a similar service, we ourselves ask the user for permission to use his data (if any is planned), and if you store / process them in some way, then carefully read the Federal Law “On Personal Data”, 152 as far as I remember, I can make a mistake here, so google it.
3. If this is a web service or utility with some kind of centralized server, we mean that, for example, MTS will not like frequent going from one ip address to different personal accounts. If the utility is on the side of the user and goes to the operator from there, there will be no problems, except that you can run into a limit on the frequency of updates to your personal account.
And remember, if this is a utility that is represented by a browser (all possible libcurl, lwp), then as soon as the operator corrects something in his LC, it will break, I had a similar experience, so it's better to use the API if it exists.

Answer 11

I propose to translate the question in a specific direction. Let's take Yota's personal account.