# ABSTRACT In a world where nearly 2.5 billion people are using various social networking media, user data and account information is not only easily accessible, but also owned by large companies. This means that any information about anyone is publicly accessible and search engine indexed. This can be worrying for users in terms of privacy and data ownership. Enter BumbleBot App – a new generation of cryptocurrency-focused web3 social network that provides privacy and security for all. It is a decentralized social network that encrypts all data and multimedia uploads, securely storing them around the world. By decentralizing the storage of user data, BumbleBot App prevents search engines from viewing user profiles or displaying them in search results. BumbleBot App also takes privacy and ownership rights to another level. The platform does not claim ownership of any data or multimedia uploaded to the system. All information uploaded belongs to the user, giving them full control of the content they post. To ensure the best user experience and the highest level of safety, BumbleBot App also has additional features such as a screening wallet, an anti-scam and a rugpull bot and a good ecosystem. The screening wallet ensures that all transactions are secure, the anti-scam bot identifies and alerts for suspicious activity, the rugpull bot prevents any malicious activity and the good ecosystem includes a community of verified users who can help identify potential scams. --- # 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://bumblebot-app.gitbook.io/bumblebot-whitepaper/abstract.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.