Security and data handling

How we plan to handle exchange data while we build digital twins for testing responsible-trading policies. PlayMind is pre-seed and the product is in development; these are the terms we commit to in each data agreement.

  • Historical exports only. Twins are built from a historical export of session data (trades, deposits, withdrawals, resolutions). Nothing sits in your trade path, and nothing we do touches your traders: we never contact them, block or place trades, or change the trading experience.
  • Pseudonymous data. No direct identifiers; tokenized account IDs only. We do not accept names, contact details, payment data or device identifiers. Reports are designed to describe twins and groups of traders, never to identify a real person.
  • Each exchange's data stays separate. Your data is isolated and used only to build twins and run policy tests for you. It is never joined with, or used to model, another exchange's traders.
  • Scope, retention and deletion are in the agreement. Each data agreement sets what data is shared, how long it is kept, and how and when it is deleted or returned.
  • Human approval on calibration. Twins are calibrated per exchange, and a person signs off on each calibration before it is used. No automatic model changes.
  • No marketing output. Twins are for testing policies. They are not used to target, contact or market to anyone, and we do not build marketing lists.
  • Encrypted in transit. Data moves to us over TLS.
  • Compliance status. We don't hold SOC 2 yet. Security questionnaires: info@playmindlabs.com.

Security questionnaires and data-handling questions: info@playmindlabs.com.