PrimeSync Studio

Studio data policy · September 1, 2026

Your strategy code is processed, not collected.

PrimeSync Studio needs the content you explicitly send to calculate a response. The MCP service is designed not to retain strategy inputs or outputs after the request completes.

What is processed

Depending on the tool, the request may contain your idea, Pine Script or Python, TradingView List of Trades CSV rows, visual-behavior notes, validation settings, and chronological trade returns. This content is held in request memory long enough to produce the result.

What PrimeSync stores

  • OAuth client name and registered redirect URI.
  • Your Whop user identifier for the connection owner. Login cookies may contain your Whop name or email in encrypted form.
  • Hashed authorization codes and tokens, approved scopes, creation, expiry, use, and revocation times.
  • A one-way hash of the connecting IP for OAuth client-registration abuse prevention, retained for no more than 24 hours.
  • For 30 days: tool name, required scope, client name, time, and status. The audit log does not store tool inputs, strategy code, CSV data, or tool outputs.

Training and sharing

PrimeSync does not use Studio strategy inputs or outputs to train models and does not sell them. Your chosen MCP client still receives the conversation and tool result; that provider's own privacy and retention terms apply. Whop processes sign-in, and the hosting provider transports and runs requests.

Operator and contact

PrimeSync Studio is published by PrimeSync Project and legally operated by Nabeh Kheir in Israel. Privacy, access, and deletion requests can be sent to [email protected].

Control and deletion

You can revoke a connection immediately from Account & activity. Expired audit metadata is deleted after 30 days during normal service operation. For an access or deletion request, contact [email protected]. The broader PrimeSync website policy remains available at primesync.me/privacy ↗.