> For the complete documentation index, see [llms.txt](https://docs.familio.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.familio.trade/the-product/public-vs-private.md).

# Public vs private families

Visibility is **off-chain**. The vault is the same; every deposit, trade and exit is still on Robinhood Chain. Private only changes what the **website** shows a stranger.

The head sets it at creation (launch step) and can flip it any time from **Manage → identity**, with a wallet signature. No transaction, no gas.

## What an outsider sees

A private family is still **listed**. It has a page, a card, a leaderboard row, coins in the bag list, a crew card, a member count, trade and payout counts, age, notes and reaction counts.

What is **blurred** for anyone who is not inside:

* vault value and free cash,
* bag sizes, cost basis and marked value,
* 7D / 30D / all-time PnL,
* payout and fee totals,
* members' wallets and slices (crew keep their names, lose their slice; everyone else is an anonymous seat),
* feed amounts, realised PnL, transaction hashes,
* non-crew actors on the feed (they show as "someone").

Private families are `noindex`. Link previews (Open Graph) render a generic "private family" card unless the reader can view.

The home tape and leaderboard **rank** private families on their real figures (order is the one thing a private family gives away), then strip the numbers for outsiders.

## Who counts as inside

The server shows full numbers if any of these is true:

* the family is public (or preview/demo),
* you are the **head**, a **co-pilot**, or a **mod** (any wallet linked to your signed-in profile),
* you **hold shares**,
* you have a **pending join request** or a raised hand on the waitlist (so you can watch the door),
* you present a **valid invite code** for this vault (head-signed on-chain, or a crew-signed link for page access).

## How to prove you are inside

Connect a wallet and **sign in**. That is a free EIP-712 / personal signature. It sets a session cookie. No ETH moves. A wallet with no profile gets the **claim your name** sheet first — same kind of free signature, permanent handle plus avatar. After that, `/me` includes private families you ride; without a session they are omitted or blurred.

A profile can **link extra wallets**. If any linked wallet is in the family, you see it. Unlinking never removes the primary.

Invite links (`/join/<code>` or `?invite=` on the family page) count even before you join, so a closed private family can still show the books to someone holding a code.

## How to toggle

**Manage → identity → public page.** Sign the visibility message. Reversible. The on-chain vault does not change. People who already saved the page still need to be inside (or hold a code) to see numbers after you go private.

{% hint style="info" %}
On-chain, nothing is private. Explorers, the factory's `families` list, and anyone watching logs can still reconstruct deposits, trades and wallets. Private is a website courtesy, not a mixing service.
{% endhint %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.familio.trade/the-product/public-vs-private.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.