Loading
Loading application
Last updated August 6, 2026
This policy explains how PolyVexa handles account, trading, billing, wallet, and operational data for its automated Polymarket copy-trading software.
PolyVexa processes account identifiers, login details, session data, invite status, plan access, support state, and settings needed to operate the application.
When you use trading workflows, PolyVexa stores user-scoped leaders, configurations, risk limits, Paper Mode trades, Paper Mode positions, Live Trading records, execution logs, notifications, and activity records.
Wallet addresses, ownership verification records, managed trading account status, deposit instructions, withdrawal requests, and readiness checks may be stored when you use wallet or Live Trading workflows.
PolyVexa does not ask for seed phrases and must not receive private keys. Secrets and credentials are handled through controlled application flows and are never intended for public logs.
Billing access, subscription tier, usage limits, checkout return state, and Stripe-linked status may be processed to enforce plan limits and access controls.
Payment card details are processed by the payment provider, not stored directly in the PolyVexa application database.
PolyVexa records audit logs, authentication events, admin actions, worker health, execution telemetry, and error diagnostics to protect accounts and keep the service observable.
These records are used for debugging, incident response, abuse prevention, billing support, and reliability monitoring.
PolyVexa provides separate choices for necessary, analytics, and marketing storage. Optional first-party product analytics, Google Analytics, and Reddit campaign tags are designed to remain blocked until the corresponding choice is granted, and the choice can be changed through Cookie settings.
First-party analytics uses random visitor and 30-minute browser-session identifiers, normalized page paths, referrer hostnames, limited campaign fields, and allow-listed product events. It does not use fingerprinting, full IP storage, form contents, trading credentials, or session replay. Raw first-party events have a configurable retention period; the technical default is 90 days. This summary is a technical draft and must be legally reviewed before production activation.
PolyVexa uses information to provide the dashboard, Paper Mode, Live Trading, leader analysis, scanner workflows, billing access, readiness controls, notifications, support, and operational safety checks.
PolyVexa does not sell personal information. Data is shared only with service providers needed for hosting, email, authentication, payments, analytics, security, and product operations.
Account, trading, billing, audit, and support records are retained for as long as needed to provide the service, meet operational requirements, resolve disputes, prevent abuse, and satisfy legal or accounting obligations.
Users can request account support through the support channel available in the product. Some records may need to be retained where security, financial, operational, or legal requirements apply.