G2A has issued an official statement to the media in relation to accusations of TinyBuild about their role as facilitators of a ‘black market economy’ through the resale of games codes. According to G2A, his shop «is a point of sale legitimate and normal for lots of developers» and they are always willing to work with the creators to prevent illegal sales.
«Until tinyBuild came to contact with G2A», explained, «we had identified more than 200 suspicious transactions of products in the Marketplace of G2A tinyBuild and suspended all of them by violating the terms and conditions and security of G2A.COM processes».
«All G2A has requested was tinyBuild cooperation to rectify the incidence, proporcionandos the list of keys that have been classified as stolen without providing the tools to verify it. Only then G2A may check these keys with the Marketplace G2A confidential database and report data determined again to tinyBuild’, they lament.
G2A blames TinyBuild of having made «unjustified requests» about the possibility to eliminate store their games and receive compensation for sales made there from their own estimates. Although, they claim, responded to all requests for the study, TinyBuild did the same. «Unfortunately, tinyBuild never responded with the data needed to solve the problem».
It also accuses the study of inflating the figures of «losses», those $450,000 that holders of half the world toured recently. G2A wondered «why tinyBuild uses as reference the historical price higher than your product» rather than take into account estimates the discounts of up to 85% which can be found in some bundles, for example. «tinyBuild should explain to the media why omitted its benefits estimate sales figures “, said the statement.
«G2A.COM requests tinyBuild to provide the list of suspicious keys within a period of three days from the date of this communication», ends.
In response to the ultimatum of G2A, TinyBuild has published a list of three points that could form a solution to the problem. According to the study, G2A problems were so solve:
1 let the publishers to put a minimum price for products distributed.
2 establish a minimum part of all sales by third parties of those codes (this would be the part of the sellers).
3 check of truth to your vendors. I just made an account to me and in an hour I could sell a lot of codes, without verification of any kind. If eBay would allow you to sell merchandise without verifying the credentials of the seller (you ask for identification, confirmation of the address, which you associate a bank account, etc.), probably would be in the same situation by facilitating the marketing of stolen goods.
We have asked G2A his point of view on this proposal.
I reproduce below the full statement, dated June 21, 2016, such which has been sent to the media.
Declaration G2A.COM / tinyBuild
G2A requests tinyBuild to provide its list of suspicious keys in 3 days
G2A.com wants to inform its partners, gamers, developers, publishers and everywhere else interested about what happened now and in the past in relation to the incident with tinyBuild. G2A requested the cooperation of tinyBuild to investigate the matter and reach a quick and solid solution.
It is important to bear in mind that G2A is an open Marketplace where everyone can sell all kinds of products in digital format gaming. G2A is a legitimate and common for large number of developers, where they sold their keys out of retail distribution, and that more than 200,000 vendors have already joined. Before tinyBuild came to contact with G2A, already had identified more than 200 suspicious transactions of products in the Marketplace of G2A tinyBuild and suspended all of them by violating the terms and conditions and security of G2A.COM processes.
The origin of this case goes back to March 22, 2016, when the official tinyBuild Twitter account published a Tweet containing little reliable information regarding piracy of his latest title data, Punch Club. Naturally, our representatives were in contact with them to inform and assist developers.
This measure was followed by discussions via email. tinyBuild made several unjustified requests, related to the Elimination of stock of the G2A Marketplace sellers, as well as compensation for the value of the products that they had estimated. Answered all the questions asked to G2A (requested by tinyBuild data were sent by decision itself and G2A-free), including questions about the number of orders for its products and its average price during the life cycle of each product card (from your date of release until June 8, 2016).
All G2A has requested was tinyBuild cooperation to rectify the incidence, proporcionandos the list of keys that have been classified as stolen without providing the tools to verify it. Only then G2A can check these keys with the Marketplace G2A confidential database and report data determined again to tinyBuild. Unfortunately, tinyBuild has never responded with the data needed to solve the problem.
In relation to the 450 thousand dollars of potential losses of tinyBuild:
Why tinyBuild used as reference the historical price higher than your product? In the real market their products in a bundle with a 85% discount can be purchased as you can verify in https://steamdb.info/app/207140/ and https://isthereanydeal.com/. Find one price half more bass would give an overview of closest to reality. tinyBuild should explain to the media why he omitted its benefits estimate sales figures.
The question that the industry should be doing now is, why tinyBuild never we did respond with a list of codes that should be removed from the Marketplace of G2A?
In conclusion, G2A always has its doors open, supports developers with agile communication channels, uses advanced tools like blacklists, identification of sellers and suspicious offers and KYC (Know Your Customers) procedures, as well as offering protection solutions awarded as G2A Shield.
tinyBuild should return to contact us and give us a list of suspect keys to so carry out a research in depth. Subsequently, G2A is happy to publicly share the results of the investigation into this case with tinyBuild.
G2A.com requests tinyBuild to provide the list of suspicious keys within a period of three days from the date of this communication.
