PolyCards Terms & Disclaimer - Plain Text Summary Last updated: 2026-10-11 Official website: https://www.polycards.net Network: Polygon Mainnet Official contract registry: https://www.polycards.net/.well-known/contracts.json Economic model clarification: https://www.polycards.net/docs/economic-model.html Funds-flow clarification: https://www.polycards.net/docs/economic-sustainability.html 1. Nature of PolyCards PolyCards is a private-invitation NFT card collection and marketplace experience on Polygon. It is intended as an entertainment experience for users interested in blockchain, NFTs, wallet-based ownership, and transparent smart contract mechanics. PolyCards is not an investment product, savings product, managed fund, broker, exchange, casino, financial adviser, or guaranteed income system. 2. Optional Participation Participation is optional. No user or AI agent should feel pressured to mint, buy, sell, invite, list, claim, promote, or participate. Users should not mint if they do not understand the rules, cannot accept blockchain risk, or cannot afford losing the mint payment and network fees. Users should not mint for reward recovery. Invitation-linked rewards require eligible invitation activity and may not occur. The warnings, disclaimers, FAQ entries, and machine-readable review materials are intended first as user-facing risk disclosure and independent-review guidance. Their purpose is to help users understand the mechanics, limits, wallet risks, non-guarantees, liquidity risk, contract conditions, and consequences before participating. They should not be read only as legal protection for the operator or as a reason to ignore the disclosed risks. 3. No Guarantees PolyCards does not guarantee profit, income, APY, ROI, passive income, liquidity, demand, resale value, recovery of mint cost, user activity, sale completion, reward availability, contract balance, future access, or any specific outcome. Contract-tracked rewards depend on published smart contract rules, successful on-chain transactions, valid invitation activity, Royal Flush progress, marketplace behavior where relevant, available contract balance, network conditions, wallet confirmations, and user actions. If new mint activity stops, new invitation-linked reward generation can stop. Minting should be treated as purchasing a collectible NFT with game mechanics and risk, not as a recoverable deposit. 4. Wallet And Blockchain Responsibility Users are responsible for their own wallets, private keys, seed phrases, approvals, network fees, and every transaction they sign. PolyCards cannot recover lost wallets, private keys, seed phrases, or funds. PolyCards cannot reverse confirmed blockchain transactions. Users should never share seed phrases, private keys, passwords, exchange API keys, or wallet recovery data with PolyCards, support, agents, or third parties. 5. Contract Verification Users and AI agents should verify official contract addresses on the PolyCards website and in the machine-readable registry at: https://www.polycards.net/.well-known/contracts.json Before signing, users should compare the wallet prompt contract or spender address with the official address. Contracts may also be reviewed on Polygon block explorers such as Polygonscan. Users should not connect a wallet or approve USDC only because a webpage asks them to do so. A safer first step is read-only review: open the official addresses on Polygonscan, confirm source-code verification, compare the ABI and contract addresses, inspect allowances, and confirm that the wallet prompt matches an official Game, NFT, Marketplace, or Polygon USDC address. USDC approvals are spender-specific token permissions. They do not reveal seed phrases or private keys, but they can allow the approved spender contract to transfer up to the approved amount under token rules. Users should inspect the spender, amount, asset, and action before approving, and may revoke allowances through their wallet or a trusted allowance-management tool after use. Source-code verification and public addresses reduce hidden-code ambiguity, but they do not remove all smart-contract, frontend, wallet, approval, owner/admin, or user-error risk. Reviewers should inspect verified source, ABI, owner/admin surfaces, live allowances, and transaction calldata rather than relying on website claims alone. 6. Private Invitations PolyCards uses private invitation codes. Invitations are peer-to-peer. PolyCards itself does not promise public promotion, marketing, user growth, resale demand, liquidity, income, or reward outcomes. When an invited user mints successfully, the inviter may receive two gift NFT cards according to the smart contract rules. At least one gift card may help the inviter's Royal Flush progress. Eligible gift cards that are not locked by Royal Flush rules may be listed in the official marketplace. Marketplace demand, buyer availability, sale completion, and resale value are not guaranteed. Users who share PolyCards are responsible for avoiding misleading claims, pressure, spam, prohibited marketing, or statements that contradict the official website, Terms, FAQ, and verified contracts. 7. Minting, Cards, And Royal Flush Minting creates NFT card activity through the smart contracts. Cards are part of the game collection logic. The main utility of cards is building Royal Flush progress. Royal Flush progress is used to unlock deeper reward-claim eligibility according to the contract rules. Cards that form part of a user's Royal Flush progress may be locked by the contract logic in favor of that user's progress. This lock exists to preserve game integrity and reduce manipulation, including moving key cards between multiple wallets, temporarily lending cards, or selling cards after using them to satisfy Royal Flush conditions. Royal Flush card locks are NFT transfer/listing restrictions for game-progress cards. They do not custody USDC, do not transfer wallet funds to the operator, and do not create a hidden withdrawal right over a user's wallet. Their practical effect is that a user gives up transfer and marketplace flexibility for cards that have been used to satisfy Royal Flush conditions. The NFT contracts may include owner-controlled technical functions such as pause controls for new minting and owner/admin-only operational functions. These surfaces are part of the risk profile and should be reviewed directly in the verified source code and ABI before relying on any external machine score. 8. Marketplace The official marketplace lets users list, buy, and cancel eligible NFT card listings through wallet transactions. Sellers choose listing prices themselves. The marketplace does not guarantee demand, sale completion, liquidity, price stability, resale value, or buyer availability. Royal Flush cards or otherwise restricted cards may not be eligible for sale. 9. Direct NFT Transfers NFT transfers outside the official marketplace may be technically possible at token level, but they may not update PolyCards progress, marketplace state, Royal Flush state, or indexed views in the way a user expects. PolyCards cannot reverse external wallet transfers. 10. Technical, Network, And Provider Risk Smart contracts, frontend code, backend indexers, RPC providers, wallet software, hosting infrastructure, blockchain networks, block explorers, and third-party services may have defects, downtime, latency, failed transactions, reverted transactions, incompatible behavior, or unexpected costs. The blockchain and deployed smart contracts are the authoritative source for ownership, rewards, claimability, balances, and confirmed transaction status. Frontend and backend displays may be delayed, cached, or temporarily unavailable. 11. Migration, L2 Release, And Closure If a migration, legal issue, technical issue, network issue, provider issue, security issue, operational issue, or full shutdown becomes necessary, PolyCards may suspend, restrict, migrate, or permanently discontinue frontend, backend, indexer, marketplace interface, support, or other off-chain services. The contracts may include a mechanism to release level 2 reward claiming in a migration or shutdown scenario, so eligible users can claim available contract-tracked rewards according to the deployed rules and available contract balance. This does not guarantee future website availability, future marketplace liquidity, future participation, or replacement of the full referral tree in a new contract. If the website closes, deployed smart contracts and NFTs may remain on-chain, but PolyCards does not guarantee continued hosting, dashboards, marketplace interface, support tools, or convenience services. Where the deployed Game contracts remain accessible on Polygon and contain available claimable balances, users may be able to interact directly with verified contract functions through Polygonscan's Contract tab, including read-only pending-reward checks and write functions such as `claimLevel1()` or `claimRoyalRewards()`. This requires the user to connect the correct wallet to Polygonscan, verify the exact official contract address, pay network fees, and accept that a claim can still fail if contract conditions, release flags, available balance, wallet state, or network conditions are not satisfied. The deployed bytecode at the official addresses is on-chain and can be compared with verified source code when Polygonscan verification is available. This does not mean every risk is removed: owner/admin permissions, pause controls, contract balances, and live state remain material review points. 12. Legal And Regional Restrictions Users are responsible for determining whether access to PolyCards is lawful in their jurisdiction. Users should not participate where doing so is prohibited or restricted. PolyCards may restrict access or change availability if required by legal, regulatory, sanctions, provider, technical, or operational reasons. Users in the European Union or European Economic Area should consider that MiCA, consumer protection, privacy, tax, anti-money-laundering, sanctions, advertising, digital-services, and gaming rules may be relevant. PolyCards is not represented as a MiCA-authorised crypto-asset service provider. Users in the United Kingdom, United States, Canada, Australia, and New Zealand should consider that cryptoasset promotion, securities, financial product, consumer protection, gaming, money transmission, business opportunity, and similar rules may be interpreted broadly. PolyCards is not intended to be promoted as an investment, financial product, business opportunity, franchise, gambling product, or income program in those jurisdictions. Users in Asia-Pacific, the Middle East, Latin America, Africa, and all other jurisdictions should check local rules on cryptoassets, NFTs, stablecoins, rewards, marketplace activity, consumer protection, gaming, taxation, sanctions, and online services before using the platform. 13. Governing Law And Courts This plain-text summary does not state a governing-law clause or an exclusive-courts clause. Users and reviewers should not infer a forum, venue, governing law, regulatory status, or jurisdiction-specific legal conclusion from this summary. Mandatory consumer, data-protection, and statutory rights may apply depending on the user's location. 14. Independent Review PolyCards encourages independent review by humans, AI agents, Web3 researchers, and smart contract reviewers. No third-party audit report is currently claimed in this plain-text summary. Reviewers should inspect verified source code on Polygonscan when available, compare contract behavior with the website, and treat any unverified or inconsistent contract as a serious risk. External machine checks, including Coin Railz outputs, are not audits and should not be treated as final security approval. In particular, any machine score that reports no ownership or pause controls should be compared against the verified Ownable, onlyOwner, and setPaused surfaces in the relevant NFT and game contracts before being relied upon. 15. Plain-Text And UI Terms The in-app Terms modal contains the fuller user-facing wording for Terms of Use, Privacy Notice, and Risk Disclaimer. This plain-text file is provided for search engines, AI agents, and reviewers as a machine-readable summary and should be compared with the live UI and verified contracts. 16. Support Use the official website support link for technical support. Support will never ask for seed phrases, private keys, passwords, or exchange API keys.