# Your account Who you are signed in as, which plan you are on, and the sign-in methods and private tree forks attached to the account — all fetched in the browser. The address, the plan and the attached sign-in methods are one visitor's, so they are requested from the API after the page loads rather than built into it. ## What the account holds Three things the public site has no place for: the plan and its quotas, the API keys that authenticate the hosted MCP endpoint, and the private tree forks whose changes are proposed back rather than published. Deleting the account revokes every key with it.