> For the complete documentation index, see [llms.txt](https://docs.patcher.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patcher.xyz/core-workflows/account-and-privacy.md).

# Account and Privacy

This page covers the account choices that shape how public or private your Patcher workspace feels.

![Account page on iPad Pro](/files/iSzfjQVHl5jp1raJ8IEB)

## Browsing without signing in

You can explore the public side of Patcher without an account, including modules, public racks, public patches, and public profiles.

## What signing in unlocks

Once you have an account, you can:

* save modules to your collection
* build racks
* create patches
* use the full user area
* manage your public profile settings

## Public vs private

Profile visibility and item visibility are separate choices.

New racks and patches currently start public, so check their sharing toggle if you want to keep them private while you work.

For public discovery, both the item and the public profile need to be public.

## Public profile visibility

Your public profile can be switched on or off from your signed-in workspace.

When the profile is private, the public profile page is not available to other people.

## Username and profile basics

Your username is part of your public profile identity. If your profile includes a website, that can appear there too.

## Sharing carefully

Before making your profile public, review:

* which racks should be public
* which patches should be public
* whether your profile link is ready to share

## Support

If you need help with account-related issues, start here:

* [Contact us / Help / Community](/project/contact-us-help-community.md)
* [FAQ](/project/the-project.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.patcher.xyz/core-workflows/account-and-privacy.md?ask=<question>
```

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.