The contract between the developer and Google Play in Russian

If you have placed your application on Google Play and you are so lucky that it has started to bring some money, then sooner or later you will be asked how to get this money. On this occasion, many useful instructions have already been written, and their successful passage should guarantee that there are no problems with your bank’s currency control when receiving a payment from Google Wallet (formerly Google Checkout).

Understanding this issue recently, we were faced with the need to submit our agreement with Google Play to the bank. This agreement exists in the form of a public offer ( here is a link ) and the problem is that it is provided by Google only in English.

Having fairly rummaged in the depths of the Internet, we were able to find a good translation. However, it turned out that the translation from 2012 is already outdated, and in the current edition (August 5, 2013) there are moments that are not translated. As a result, we turned to professionals who transferred the missing pieces of the contract to us. The result is laid out here for universal use.
')
Link to the translation of the contract from August 5, 2013

Under the cut are interesting moments that, as we noticed, Google was added to the new edition of this agreement.



In the version dated September 19, 2012 in paragraph 2.3 it was written:

2.3 Limitations on the Use of Service. It is up to the Seller to comply with the limitation:
(i) the Integration Guidelines;
(ii) the Button and Acceptance Logo Guidelines and the Google Brand Feature Guidelines;
(iii) GPC requirements for data security;

In the version of August 5, 2013, Google decided to expand the concept in paragraph (iii):

(iii) GPC requirements for data security and privacy, including the Google Privacy Notice;

In the version from 2012 in paragraph 6.3 it was written:

6.3 Payment Adjustments. The seller acknowledges that he has to pay the bill (including a Carrier), and the GPC will accept the charge back. Seller if the transaction is not covered by the Payment Guarantee Policy. As a particular payment transaction, GPC may withhold payments or reverse payments if:
(i) A Buyer makes a claim for a GPC for a refund or other reversal or
(ii) the rules of this agreement, or otherwise violate this agreement, or not the Policies. It is possible that the seller agates to cooperate with him.

In 2013, one more phrase was added there:

(ii) the rules of this agreement, or otherwise violate this agreement, or not the Policies. It is possible that the seller agates to cooperate with him. It agrees to comply with the GPC.

Well, the third change affected section 7 (CONFIDENTIALITY AND PROPRIETARY RIGHTS)

It was:

7.1 Confidentiality. It shall be obtained through the Service, except for the use of it. Seller acknowledges that it has been subject to the Service Privacy Policy. It doesn’t matter that he has received his or her consent to receive his or her consent. third party confidential information. The seller agrees that the breach of this paragraph. In the case of the GPC, it’s third parties. "GPC Confidential Information" includes without limitation:

It became:

7.1 Confidentiality. This information is obtained through the Service Provider. Seller acknowledges that you are not subject to the Google Wallet and you are not allowed to use it . It doesn’t matter that he has received his or her consent to receive his or her consent. third party confidential information. The seller agrees that the breach of this paragraph. In the case of the GPC, it’s third parties. "GPC Confidential Information" includes without limitation:

In general, it is clear that nothing terrible in the license agreement has not changed, as expected. In any case, we hope that the document we have laid out will help you save time and quickly get your hard-earned money.

Have a nice day!