# Security & Self-Custody ### Your Wallet Stays Yours Security matters more when real money is involved. That is why PolyKopy is built with a **self-custody-first** approach. When you first launch the bot, a wallet is created and assigned to you through **Polymarket’s builder program**. That wallet is a **self-custody Safe wallet** tied to your PolyKopy experience. That means the onboarding is smooth, but the wallet is still yours. **PolyKopy does not have access to your private keys.** That part is important. Very important. *** ### What Self-Custody Means Here A lot of people hear “bot” or “automation” and assume that means giving up control. That is not how PolyKopy is built. With PolyKopy: * your wallet is created for you when you first launch the bot * the wallet is assigned to you through Polymarket’s builder program * the wallet is self-custody * you remain the one in control of the wallet * PolyKopy does not hold your keys So while PolyKopy handles the copy trading automation layer, it does **not** take ownership of your wallet. That is a big difference. *** ### Why This Matters There are two things users usually want at the same time: #### 1. A smooth experience Nobody wants a painful setup just to get started. #### 2. Real control Nobody wants to feel like they had to hand their wallet over to a black box just to use a product. PolyKopy is designed to give you both. The wallet flow is simple and built into the launch process, but the wallet itself remains self-custody. That means the product can feel easy to start using without sacrificing the part that really matters: **ownership stays with the user.** *** ### PolyKopy Handles the Automation Layer It helps to think about the product in two parts: #### Your wallet This is yours. #### The automation layer This is where PolyKopy helps with wallet discovery, copy logic, rules, and execution flow. That is the right mental model. PolyKopy helps run the system.\ It does not own your wallet. That separation matters because it keeps the product aligned with how people actually want to use tools like this: fast, simple, and useful — without giving up control. *** ### Security Is Not Just About Storage When people think about security, they often only think about where the wallet lives or who holds the keys. That matters, of course. But good security is also about how the product is designed. A strong setup is one where users can: * understand how the wallet flow works * know who controls what * use the product without hidden confusion * set clear boundaries around their trading behavior * keep risk and permissions aligned with their plan In other words, security is not just a custody question. It is also a clarity question. And PolyKopy is built to keep that clear. *** ### Control Still Matters After Setup Just because the wallet creation is handled smoothly does not mean you should stop thinking carefully once you are live. Self-custody is strongest when it is paired with strong habits. That means treating your setup like something real, not casual. A good mindset is to stay clear on things like: * how much you are funding * how much you are allocating to copy trading * how aggressive your current rules are * how many wallets you are following * whether your setup still matches your risk tolerance The product helps with the system. You still stay responsible for how you use it. That is how it should be. *** ### PolyKopy Is Built for Control, Not Blind Trust This is really the theme behind the whole product. PolyKopy is not about asking users to blindly trust the bot, blindly trust the wallets, and blindly hope for the best. It is built around: * better wallet discovery * more structured copy trading * stronger risk controls * clearer visibility * self-custody user control That is the real difference. The product is trying to make copy trading smarter, not more careless. *** ### What PolyKopy Does Not Do To keep things simple, it helps to be clear about what PolyKopy is **not**. PolyKopy is not: * a custody service holding your wallet for you * a product that takes ownership of your keys * a magic system that removes trading risk * a blind “copy everything” engine with no user control What it does do is help you: * discover stronger wallets * set smarter rules * copy with more structure * manage the strategy through Telegram * stay in control of your own wallet setup That is a much better model. *** ### Security Also Means Staying Disciplined A lot of users think security ends once the wallet is created and funded. Not really. Security also includes how disciplined you are with the strategy itself. That means: * not overfunding recklessly * not copying without limits * not following too many wallets too quickly * not loosening settings just because you got impatient * not treating the product like it removes all risk A sloppy strategy can create just as many problems as a sloppy setup. That is why control is such a big part of the product philosophy. *** ### The Best Way to Think About It The cleanest way to think about PolyKopy is this: * your wallet is yours * your keys are yours * your strategy is yours * PolyKopy helps automate the copy trading workflow around that That is the model. Simple. Clear. Strong. And honestly, that is how it should be. *** ### The Bottom Line When you first launch PolyKopy, a self-custody Safe wallet is created and assigned to you through Polymarket’s builder program. That gives you a smoother onboarding flow without giving up control. PolyKopy does not have access to your private keys.\ Your wallet stays yours.\ And the automation layer is built around helping you trade smarter, not take control away from you. > **Self-custody first. Control stays with you.** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://polykopy.gitbook.io/polykopy-docs/telegram-bot/security-and-self-custody.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.