Data & Privacy

A learning system raises a fair question: where does the data go? For the economy engine's learning, the short answer is that it stays on your server. The optional beta telemetry is the one exception, set out below.

Does the engine send my economy data anywhere?

Not to learn. The engine learns entirely on your own server, from your own trades, and the model it builds is yours and lives only with your data. Learning never uploads your market, shares it with other servers or pools it anywhere. The one thing that can send data outward is the optional beta telemetry below, which is on by default and can be turned off.

What about my players and their data?

The engine works with the same trade records your server already has: who traded, what, and for how much. It does not gather anything new about your players, and it does not send their information off your server as part of learning. The beta telemetry below is the exception, and it hashes every player's UUID on your server before anything leaves.

Then what is the telemetry I see in the config?

That is a separate, optional feature for the beta, and it is the only thing that sends anything outward. It has three levels, each switched under telemetry in config.yml, and the engine works exactly the same with all of them off.

Level	Default	What it sends
anonymous	On	Facts about the server and the plugin: the server software and version, Java and the operating system, the plugin version, the database type, whether Redis and barter are on, a rough player-count band, the player limit, how many plugins are installed, the economy engine's state and settings, the ids of the currencies in use, which integration switches are on, performance figures and a crash count. No player data.
economy	On	Every record the engine stores, in batches: auction sales, trades read from other plugins, server shop trades and money sent between players. Each record carries its time and type, the item with its custom name, its enchantments, including those stored in an enchanted book, and its custom model data, the item's rarity, the quantity, the price and currency and the converted price, the plugin it came from, its trust weight and the engine's flags for it, whether each side shared a connection with another player, never the address itself, and each side's trade count. Player UUIDs are hashed on your server first, with a random key that never leaves it. It also sends the hourly market snapshots and the engine's price suggestions.
playerBehaviour	Off	For each player, under a hashed id, how many searches they ran, how many times they opened the auction house and the claim screen, and how many claims they collected.

What does the engine actually store on my server?

A history of completed trades and a small learned model, kept on your server. It is the same trade information your auction house, and the plugins it reads, already record, so there is nothing in it about your players that your server did not already hold. Your auction data itself is encrypted to your installation, covered in Database Encryption.