> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/platform-guide/settings/profile-notifications-privacy.md). # Profile, notifications, and privacy The **You** group in Settings holds your profile, your alert choices and your data controls. Signing in gives you a profile and data controls. Alerts and watched addresses belong to an organization on Pro, so the Notifications page has something to set only inside one. **Where:** **Settings → You** · **You need:** sign in {% hint style="info" %} Sign in if you have early access. Otherwise join the waitlist from the same dialog, which offers **Join waitlist**. The Free path needs no account, is open to everyone, and loses nothing described elsewhere in this guide. {% endhint %} Signing in does not move your account list. It stays on this device, and paying for an organization does not copy it there. ## Profile Profile is managed by the sign-in provider inside the Platform. | Tab or field | What you can do | | -------------- | ------------------------------------------------------------------------------------------ | | Name | Change the display name shown in the Account menu. | | Email | Change the address that receives email alerts and invoices. | | Security | Manage sign-in methods and active sessions. | | Delete account | Deletes your hosted account. Your device list and your on-chain accounts are not affected. | Signed out, the page reads "Sign in to manage your profile and security." ## Notifications Signed out, the page reads "Hosted alerts are an organization service on Pro. This device workspace sends none." Signed in without an organization, there is nothing to set: the page reads "Nothing to choose here without an organization on Pro. Your device workspace sends no alerts." and the watched-addresses section reads "Create or switch to an organization on Pro to follow addresses for alerts." Inside an organization on Pro, you choose your channels and the organization's watched addresses. An organization that has not completed checkout, or whose plan lapsed, keeps its follows off until it is active again. ### Channels Your channel choice applies to the organization you are in. If you belong to two organizations, you choose separately in each. | Channel | Description | | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **In-app** | "Show alerts in the notification bell". The bell appears in the top bar when signed in. Turn it off and you get no security alerts from this organization. | | **Email** | "Send workspace alerts to your account email". | ### Watched Bloxchain accounts The organization follows addresses on mainnet chains, and every member sees the same list. Alerts cover security changes on Bloxchain accounts. 1. Choose the **Network**: Ethereum or Arbitrum One. 2. Enter the **Address** and an optional **Label**. 3. Click **Follow address**. Any member can follow an address or remove one. Following is capped per organization, and so are alerts per month; the cap is shared by all members. When the organization reaches it the page shows "Alert limit reached". Remove an address to free a slot. Watched addresses are mainnet only. They do not cover Sepolia accounts, which you operate directly from Accounts. ## Privacy Signed out, the page reads "Sign in to manage privacy and data export." | Section | What it controls | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Required data** | Always on. The minimum the hosted service needs to run your account (sign-in identity, preferences, memberships). | | **News and updates** | Toggle product news email on or off. | | **Export personal data** | Downloads a JSON file with your profile, privacy preferences, your notification choices in each organization, and your organization memberships. Watched addresses belong to the organization that follows them and are not in this file. | Account deletion is under Profile → Security, not under Privacy. ## What is not here * Your account list and custom networks: see [Backup and restore](/platform-guide/settings/backup.md). * Organization members and billing: see [Organizations and billing](/platform-guide/settings/organizations-and-billing.md). * Anything on-chain. Nothing in the You group touches a contract. ## Related * [Settings](/platform-guide/settings.md) * [Organizations and billing](/platform-guide/settings/organizations-and-billing.md) * [Free, sign-in and organizations](/introduction/free-sign-in-organizations.md) * [Security disclaimers](/security/audit-status/security-disclaimers.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bloxchain.app/platform-guide/settings/profile-notifications-privacy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.