CordEx
CordEx Privacy Policy
- Operator
- Pixelated Dev Limited
- Version
- 1.0
- Effective date
- 27 September 2026
- Contact
- gamestudiomin3@gmail.com
1. Who we are and what this policy covers
Pixelated Dev Limited, a For-Profit Corporation, operates the CordEx software services described in this policy. “CordEx,” “we,” “us,” and “our” refer to Pixelated Dev Limited, not to Privy, Polymarket, Discord, Google, a Discord server owner, or another independent provider.
Our registered address is Beta Building, Oficina 6 Próspera ZEDE St. John's Bay, Roatán, Islas de Bahia 34101 Honduras. Our permit number is 89343265339856 and our registration date is 29 April 2026. Contact us about privacy, security, complaints, or data requests at gamestudiomin3@gmail.com.
This policy covers the CordEx Discord prediction-market bot, the CordEx Prediction Extension for Chrome, and the connected CordEx account, authentication, wallet-onboarding and withdrawal portal services supporting those products. It also covers those services when presented through an identified partner or white-label Discord bot. A different operator must be clearly identified where a partner independently determines how it uses data.
We are responsible for personal information whose purposes and means of processing we determine. Depending on the applicable law, this role is described as a controller, business, or responsible party. Our providers may process information on our instructions or independently for their own services, as explained below.
This policy explains information handling. It is not a waiver of privacy rights, a wallet-signing authorisation, or an agreement that removes legal responsibility. Our separate Terms of Service govern service use. Acknowledging this policy is not consent to every possible use of personal information. References to privacy rights in a country do not make our trading services available there.
2. Our role, Privy, and the location of digital assets
CordEx supplies an interface and supporting software for interacting with third-party prediction-market infrastructure, including Polymarket. Depending on the feature, our systems retrieve market information, maintain account records, prepare and transmit user instructions, request authorised signatures, and support order, position, redemption and withdrawal workflows.
We use Privy for authentication and wallet/key-management and signing infrastructure. Use of Privy does not mean that Privy holds your trading balance as a bank deposit or acts as your funds custodian. Digital assets and positions are recorded on the relevant blockchain and may be associated with an embedded-wallet address, a Polymarket deposit or smart-contract wallet, or other supported contracts. A signing-wallet address and the address holding trading assets may be different.
Where you grant delegated authority, our backend can request signatures through Privy within the permissions and policies configured for that wallet. This can allow authorised operations without a separate signing prompt for every operation. Depending on the implemented workflow and authorisation, these operations can include orders and related contract interactions, redemptions, approvals, transfers or withdrawals. The applicable permission notice must identify the operations actually enabled; this policy does not itself authorise any of them.
We process the identifiers, instructions and audit records needed for these functions. A signing service can produce a signature without sending a complete wallet private key to the CordEx application. That does not mean CordEx has no signing authority. We do not ask you to send seed phrases, complete wallet private keys, passwords or one-time login codes through Discord messages or support email.
Privy has its own Privacy Policy, User Terms and Acceptable Use Policy. These do not replace our obligations for information or permissions we control.
3. Information we process
Account and authentication information
We process your Discord user identifier, available username, display name and profile information supplied through the authorised login flow; CordEx account and session identifiers; your Privy user identifier and linked-wallet identifiers; and records of authentication, account linking, consent, notices and terms acceptance. We receive an email address or other contact information when you give it to us or an authorised account flow supplies it; Discord's basic identity permission does not by itself mean that we receive your email.
The bot, extension and portal can use the same underlying CordEx account, including across supported partner servers. This account linkage does not give a server owner access to your unrelated activity in other servers. Authentication involves OAuth authorisation codes or tokens, CordEx session credentials, and related security records. The extension stores a CordEx session token in browser extension storage to keep you signed in. These are sensitive access credentials, even though they are not the complete private key to a wallet.
Discord interactions and community information
We process commands, button and menu selections, modal submissions, market links, trading instructions, relevant message identifiers, and the user, server and channel identifiers accompanying an interaction. Server membership, role or permission information may be processed to determine which functions you can use or to deliver a feature you request.
Depending on the permissions enabled for the bot, Discord may also deliver message content, member events and presence information in accessible spaces. Access to that information is not a right to retain unrelated conversations or build profiles about community members. We limit use to the disclosed, necessary bot functionality and security purposes permitted by Discord. We do not use Discord message content to train AI or machine-learning models.
Public commands, alerts, published predictions, leaderboards and copy-trading features can expose information to other people. Private or ephemeral responses reduce ordinary channel visibility but are not end-to-end confidential communications and do not prevent recipients from taking screenshots.
Wallet, transaction and automation information
We process wallet and deposit-wallet addresses, chain identifiers, wallet aliases and account status; delegated-signer identifiers, policy references, authorisation and revocation status; signed messages and transaction identifiers; and Polymarket API credentials necessary for supported operations. Our Polymarket credential-storage implementation encrypts API keys, secrets and passphrases in its database. Encryption does not make information anonymous or eliminate access by authorised systems.
Trading records can include the selected market and outcome, order side, price, quantity, value, timestamps, execution status, fills, cancellation requests, balances, positions, profit-and-loss calculations, redemption status and fees. Funding and withdrawal records can include amounts, source and destination addresses, networks, tokens, bridge addresses, transaction hashes, relayer status and error information.
When you enable automated or copy-trading features, we process the chosen source, strategy settings, sizing and price limits, activity and execution results, and the status of your continuing authorisation. We also process the originating Discord server, partner, client surface and builder attribution needed to operate and account for the transaction.
Chrome extension information
The extension accesses the active supported Polymarket page URL and relevant page context, such as market links, event or outcome information and page elements needed to show the companion panel and trading controls. It observes changes to supported pages so those controls can update. Market identifiers and requests may be sent to CordEx and the relevant market-data provider to resolve the selected context.
The extension uses browser storage for the session token, preferences, trading presets and, where used, demonstration-trade records. It may keep current or recent market context in memory. It is not intended to collect a complete browser-history database or unrelated browsing activity.
Its permissions serve these functions: identity supports the login flow; storage maintains local state; sidePanel displays the companion interface; activeTab and scripting support the requested interaction with a page. Host access covers the supported Polymarket domains and APIs, Discord authentication, and the BO3 esports-data API. The public permission and recipient disclosures must be updated before materially expanding this access.
Technical, security and eligibility information
Our websites, APIs and infrastructure may receive IP addresses, approximate country or region, browser and operating-system information, timestamps, request identifiers, authentication and authorisation events, error reports and service-performance information. Infrastructure providers also receive network information necessary to deliver their services.
Where geographic, sanctions or other eligibility checks operate, we process the minimum information required for the check, such as a country or residence declaration, IP-derived location, wallet address, screening result and the time and basis of a decision. A browser check concerns that browser connection; a Discord command is not a reliable statement of the user's current physical location. We do not rely on a Discord profile or nationality assumption to establish eligibility.
Support and analytics information
We process information you send in support requests, including contact details, descriptions and attachments. Redact credentials and unrelated personal information before contacting us.
Operational monitoring can include errors and request context. Optional portal analytics, when enabled, may record onboarding, deposit and withdrawal events and their properties. The portal's analytics integration can process account or wallet identifiers, amounts, recipient or bridge addresses, network identifiers and outcome/error information. We must identify and minimise the fields actually sent; we will not describe transaction-level analytics as anonymous merely because a name is omitted.
Non-essential analytics or similar browser tracking will run only after the required choice or consent has been obtained. Rejecting optional analytics does not prevent access to an otherwise available core service. We do not sell personal information, use it for cross-context behavioural advertising, or use Discord or extension data for unrelated advertising or commercial profiling.
4. Where information comes from
Sources include you and your device; Discord and Privy through authorised integrations; Polymarket and its APIs; public blockchains and the infrastructure used to query them; the servers or partners through which you use CordEx; and our hosting, security, analytics and support providers. We combine these sources only as necessary for the purposes described here and permitted by the relevant platform rules.
A public wallet address may become associated with an identifiable person when linked to a Discord account or other account information. Public availability does not make every further use lawful or remove the need to protect our off-chain account linkage.
5. Purposes and legal grounds
Where a law requires us to specify a legal ground, we use the following grounds only to the extent they are available and appropriate for the particular processing.
Providing the service you request: necessary processing to authenticate you, link the correct wallet, execute your instructions, display your account, maintain settings and respond to essential support requests is based on performing our contract with you or taking requested steps before that contract.
Security and service integrity: proportionate monitoring, access control, fraud prevention, troubleshooting and defending legal claims may be based on our legitimate interests in operating a secure service, after considering the effect on your rights. This does not authorise unrelated Discord profiling or uses prohibited by extension-platform rules.
Legal compliance: processing required by an applicable legal obligation, court order or lawful regulatory requirement is based on that obligation. A contractual provider restriction is not automatically a statutory obligation; where appropriate, enforcing it instead relies on the service contract or a properly assessed legitimate interest.
Optional features: where consent is required, it covers the specific optional purpose disclosed when you choose it, such as non-essential analytics or publishing identified performance information. Consent can be withdrawn for future processing. A signing delegation, acceptance of contractual terms and consent to optional analytics are separate choices.
Some account, wallet, transaction and eligibility information is required to deliver or lawfully make a feature available. Without it, the relevant feature may not work. We explain the consequence at collection rather than seeking blanket permission for unrelated data.
6. Recipients and disclosures
We share only the information needed for the stated function and apply the stricter limitations in Section 7 where they apply.
Privy receives information necessary for its authentication, wallet, recovery, authorisation and signing services, including relevant account and wallet identifiers, device/security information and signing requests. Its own processing is described in its privacy notice; its role also depends on our contract and the particular service.
Discord receives communications and interaction responses delivered through its platform and handles its own account and platform data. We must not send sensitive financial information through Discord unless the applicable Discord terms or a specific permission allow it. A user's choice to use the bot is not an exception to Discord's restrictions. Unsupported sensitive workflows must take place on a permitted, secure surface instead.
Polymarket, its APIs, relayer and bridge services receive information needed to retrieve account data and process the requested orders and blockchain operations, including wallet addresses, signed instructions, amounts, market identifiers, credentials and builder attribution as applicable. Blockchain networks, validators and public indexers can receive and expose transaction data. RPC providers receive the addresses, queries and transactions sent to them. BO3 supplies esports data and receives the requests and associated connection information sent directly to its API.
Hosting, storage, delivery and operational providers used by the supporting application include Fly.io, Vercel, Cloudflare and Neon. Sentry supports error reporting where enabled. PostHog supports portal analytics where enabled. Telegram may carry configured internal operational alerts; such alerts must be limited and redacted. Google processes support emails sent through our Gmail address and independently provides Chrome and any Chrome Web Store services you use. Each provider receives only the data required by its actual configured function; client-side requests can disclose your IP address directly, while backend requests ordinarily disclose the server's connection information.
The deployment-specific recipient register must identify the actual RPC, cache/queue hosting, telemetry-export and screening providers, and any additional recipients before those integrations process personal information. It must also distinguish direct CordEx providers from subprocessors of another provider. Contact us for the current register and the transfer arrangements applicable to your information.
Partners and other users: a relevant Discord server or white-label partner may receive information needed to deliver the feature you selected or account for its service, including relevant server attribution and permitted reports. We do not grant a partner unrestricted access to your account, complete cross-server trading history or credentials merely because you used its server. Identified public performance, copying or trading disclosures require an appropriate, specific user choice and platform permission. Private information is not published simply because a partner could earn fees from your activity.
Legal and professional recipients: we may disclose necessary information to advisers under appropriate confidentiality obligations, or to competent authorities where disclosure is legally required or otherwise lawful and necessary. We assess and limit requests and notify you where permitted and appropriate.
Business changes: a restructuring or business transfer does not remove privacy protections. Where Chrome's Limited Use rules apply, a merger, acquisition or asset-sale transfer of covered user data requires explicit prior user consent. Other transfers remain subject to applicable law, notice and the restrictions of the originating platform.
7. Additional Chrome and Discord data protections
CordEx's handling of information obtained through Google APIs and the extension is subject to the Chrome Web Store User Data Policy, including its Limited Use requirements. We restrict collection and use to the disclosed user-facing purpose and its permitted operational needs. Restrictions continue to apply to information derived from that data.
Covered extension data is not used for personalised advertising, data brokerage, creditworthiness or lending decisions. Access by a human to identifiable extension data is limited to specific user-authorised assistance, necessary security work or legal compliance; genuinely anonymous aggregate information may be used for permitted internal operations. Transfers are limited to the purposes allowed by the originating platform, not every general business purpose listed elsewhere in this policy.
Discord API data is used only for the disclosed and permitted bot functionality. We do not sell or license it, scrape Discord for unrelated purposes, build prohibited profiles about users or their relationships, or send unrelated marketing using it. Necessary disclosure to an operational provider is not permission for that provider to reuse it for advertising or unrelated monetisation.
These commitments concern data handling. They do not represent Chrome Web Store approval, Discord approval of a financial workflow, or authorisation to offer a prediction-market service in a particular territory.
8. International processing
We are established at the address in Section 1 and use international infrastructure. Information may be processed in Honduras, the United States and other countries where an identified provider or authorised team member operates. The recipient register should identify the relevant processing locations, rather than treating a provider's headquarters as the only location.
Where applicable law requires a transfer mechanism, contractual safeguards, a transfer assessment or other protection, those arrangements must be in place before the restricted transfer occurs. We do not treat continued use of the service as blanket consent to every international transfer. Contact us to obtain information about the actual mechanism and available safeguards, subject to lawful redaction of confidential material.
9. Retention, deletion and public records
We retain personal information for no longer than the relevant purpose justifies, subject to applicable law and stricter provider requirements. Account and wallet-linking information is retained while needed for an active account or an unresolved account request. Session and access credentials are kept only while necessary for authorised access and are invalidated or removed when no longer required. Operational logs and message context are kept for the shortest justified troubleshooting or security period, not as a permanent archive of unrelated activity.
Transaction, fee, authorisation, eligibility and complaint records may need to be retained after account closure where a specific legal requirement or a documented and proportionate legal-claims need applies. We retain only the necessary fields, restrict their use and delete them when that basis expires. We do not label every record as subject to an indefinite financial-compliance obligation.
Backups are subject to a defined expiry cycle and restricted access. Where immediate selective deletion from a protected backup is impracticable, the information is put beyond ordinary use, expires under that cycle, and deletion instructions are reapplied if the backup is restored. We can explain the applicable retention period or criteria when you request it. Shorter Discord or other platform deletion requirements remain applicable except to the extent a binding legal obligation requires otherwise.
Deleting a CordEx account, uninstalling the extension, disconnecting Discord, revoking a signing delegation and cancelling an order are different actions. Uninstalling does not itself cancel an order or an automation running on our servers. We will help distinguish those actions when handling your request and will not require you to abandon lawful access to your assets to exercise privacy rights.
We cannot alter a confirmed public blockchain record or guarantee removal of copies made independently by other people. We can still delete or restrict our own off-chain information where required, including the link between an account and a public wallet. The permanence of blockchain data is not a blanket exception for our internal records.
10. Your choices and rights
Depending on applicable law, you may request information about processing; access and a copy; correction; deletion; restriction; portability; objection to legitimate-interest processing; withdrawal of consent; review of qualifying automated decisions; or other applicable rights, including limits on sensitive-data use. You may complain to the competent privacy authority and use any applicable appeal process. These rights are subject to the relevant legal conditions, not a contractual waiver in our Terms.
Email gamestudiomin3@gmail.com with the subject “Privacy request” and a description of your request. You do not need to supply a private key, seed phrase or password. We use proportionate identity verification and may ask you to verify control through a secure account flow. An authorised representative may act where applicable law permits. We respond within the applicable legal deadline and explain any lawful limitation, extension or refusal. Requests are free unless the law specifically permits a fee.
You can also use available account, browser and permission controls, revoke relevant authorisations, turn off an optional feature, or ask support for assistance. Essential transaction records and access to a third-party platform cannot necessarily be changed by deleting browser storage. Exercising privacy rights will not attract an unlawful penalty or discriminatory treatment.
11. Automated functions and decisions
User-configured trading and copying can run automatically and can produce financial losses. The selected source, rules, limits, authorisations, available balance, market conditions and third-party execution determine what the feature attempts; it does not guarantee that a copied order matches another person's outcome.
Eligibility or security systems may restrict a function based on location or other relevant compliance and security signals. Where we make a solely automated decision with a legally significant or similarly significant effect and the law requires additional information or safeguards, we provide them, including an available human-review and challenge route. Contact us about an incorrect restriction. We do not promise to override a binding legal or provider restriction.
12. Security, age restrictions and changes
We use measures appropriate to the data and risks, including access controls and protection of access credentials. No system can guarantee complete security. This statement does not excuse inadequate safeguards or remove our duties to investigate and notify incidents under applicable law or provider requirements. Report a suspected issue to gamestudiomin3@gmail.com without including secrets.
Trading features are intended only for people aged at least 18 and any higher age required by applicable law or the relevant provider. They are not directed to children. A mixed-age Discord server does not make its members eligible to trade. Where we learn that an ineligible child has supplied personal information, we restrict the relevant access and take appropriate deletion and safeguarding steps, subject to lawful obligations.
We will publish the effective date of a revised policy and give appropriate notice of material changes. A new optional purpose requiring consent will not be activated by silently changing this policy. Earlier disclosures and permissions remain relevant to information already collected. Questions, requests and complaints should be sent to the company contact in Section 1.