Privacy policy
Scope
This policy describes PolyForge workspace data. The workspace administrator controls access and the deployment. It does not describe Polymarket's own website or the independent practices of another provider. Review the terms of use for the virtual-account and execution model.
Information used by the workspace
Account records include your display name, login identifier, password hash, role, grants, access expiry and session/device associations. Trading records include virtual allocations, orders, fills, positions, result observations and relevant audit entries. Your saved research may include public wallet addresses, labels, notes, alerts, resources and manual journal entries.
When a community feature is enabled, it processes the messages, files and visibility choices you submit. That feature is not enabled merely by its inclusion in a roadmap. Public market, wallet and news information is fetched from its identified external source.
Purposes and visibility
Data is used to authenticate access, enforce permissions, calculate and explain internal trading results, preserve your research, operate integrations and maintain the workspace. Shared market data is separate from account-owned records. A community ranking, shared message or exported file may reveal the information shown in its publication or export interface; do not treat intentionally shared material as private.
Cookies and connections
Essential cookies support sessions and remembered accounts on the current device. Secure cookie transport requires HTTPS. Remembered-account access can be forgotten or revoked. Authenticated WebSocket and fallback event connections use the current account/session policy; they are not advertising identifiers.
Network addresses can be processed for request routing, rate limits and operational diagnostics. This policy does not assert that an analytics, advertising or third-party tracking service is installed when it is not configured.
External integrations
Polymarket and other source requests fetch identified public information. Configured AI analysis sends the analysis context required by that tool to its selected provider; do not submit confidential information without understanding the context being sent. Provider/model availability and retention depend on that provider's terms.
Google connections use the OAuth permissions presented when connecting; the current workspace metadata integration does not imply permission to read every document's contents. Discord alert delivery sends the configured notification to the selected webhook destination. An external resource link opens a separate service with its own policies.
Storage and administration
Account and workspace records are stored in the database configured for this deployment. Passwords are stored as salted hashes, not readable passwords. Access controls, backups and secret-storage protections depend on the deployed version and configuration; this policy does not promise encryption or a completed migration that has not actually been enabled.
Administrators manage access and may inspect operational/audit information needed for that role. They must not treat a balance correction as an exchange result. Backups and audit history may retain records after an active entry changes; there is no automatic promise that an exported copy held by another person can be recalled.
Requests and retention
Use the available export tools for your permitted records and contact the workspace administrator through the established private channel for access, correction, deletion or retention requests. Retention and legal obligations vary by deployment; a specific retention period or regulatory certification is not claimed without a configured policy.