Safety Tips
Keep these safety tips in mind when using CookAI Bots to protect your assets and privacy.
🔴 Wallet Security
Never share your private key or seed phrase with your Bot
Bots have code execution capabilities and can theoretically read anything in chat history. Never send wallet private keys, seed phrases, or passwords in conversation.
Use a dedicated deposit wallet
We recommend creating a wallet dedicated to CookAI deposits. Don't use your main wallet with large holdings. Only deposit the amount you plan to use.
Verify deposit address
Always verify the contract address when depositing. The official CookAI contract address is displayed on the homepage and in docs. Verify the contract is verified on BSCScan.
🟡 Bot Usage Safety
Don't let your Bot run code you don't understand
Bots have code execution privileges in private chat. If you ask your Bot to run scripts or install software, make sure you understand what it's doing. When in doubt, ask the Bot to explain first.
Monitor Bot behavior in groups
Bot capabilities are restricted in group chats (no code execution, no file access). However, Bots can still see all messages in the group. Don't discuss sensitive information in groups with Bots.
Regularly check balance and usage
Use the /status command or Dashboard to regularly check your wallet balance and Bot usage. If you notice unusual consumption, stop the Bot immediately.
🟢 Account Security
Automatic Owner Lock Protection
The first person to send a private message to a Bot is automatically locked as the Owner. Only the Owner can control Bot settings and advanced features.
Auto-stop on zero balance
When wallet balance reaches 0, the Bot automatically stops responding with no additional charges. It resumes automatically after recharging.
14-day auto-expiration
Bots unused for 14+ days enter hibernation. Your data and balance are preserved, and the Bot auto-recovers when you send a message.
🚨 High-Risk Operations
The following operations may lead to fund loss or data leaks. Exercise extreme caution:
Sending private keys/seed phrases to Bot — Bot may store them in memory, making complete deletion impossible
Asking Bot to perform fund-related operations — such as transfers, signing transactions, etc.
Using Bot to discuss sensitive business information in groups — everyone and the Bot can see it
Giving Bot access to your other services — such as server SSH, database connections, etc.
Sharing Bot Token with others — they can control your Bot and consume your balance