> For the complete documentation index, see [llms.txt](https://docs.floral.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.floral.fun/api-v2/v2-privacy.md).

# Privacy and visibility

Every V2 response applies each person's current settings when it's made. **Your application always counts as a signed-out stranger.** A user's consent lets you verify their actions under V1, but it doesn't open anything in V2, even for that user's own account.

## What's public

| Data                         | Public when                                                                                  | Otherwise                   |
| ---------------------------- | -------------------------------------------------------------------------------------------- | --------------------------- |
| A post                       | Anyone signed out could read all of it, including the thread above it                        | `404`                       |
| A profile                    | The account is active                                                                        | `404`                       |
| Follower and following lists | The account is public and hasn't hidden its lists                                            | `403 visibility_restricted` |
| Someone inside a list        | They're public, and haven't hidden their own lists                                           | Left out                    |
| A person's activity          | The account is public                                                                        | `403 visibility_restricted` |
| A person's communities       | The account is public and hasn't hidden them. Paid and gated communities are always left out | `403 visibility_restricted` |
| A community's content        | It's free, open to anyone, has no token or NFT gate, and allows discovery                    | `403 visibility_restricted` |
| Search results for people    | They've chosen to be discoverable                                                            | Left out                    |

**Counts stay public**, including follower counts for accounts with hidden lists.

**Never available:** who liked a post, community member lists, membership changes, private messages, wallet addresses, balances, positions and email addresses.

Replies by private accounts are left out, so a post's `comments_count` can be higher than the replies you can read.

## Not found, or restricted?

A post that isn't public returns `404`, exactly like one that never existed, so you can't confirm a private post is there.

`403 visibility_restricted` is only for something the profile or community already shows as hidden. It doesn't say which setting caused it, or who can still see it.

## When something changes

Changes apply to the next response and the next webhook delivery. A webhook or bulk event recorded while a post was public isn't sent once it stops being public, and a delivery waiting to retry is checked again before it's sent.

Floral also tells you when to drop what you've stored:

| Event              | Meaning                                                | What to do                                                                                                                    |
| ------------------ | ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| `post.unavailable` | The post was deleted, or is no longer public           | Delete your copy                                                                                                              |
| `user.restricted`  | This account's visibility decreased, or it was deleted | Fetch the profile again, and remove anything you can no longer read. If it returns `404`, delete everything you hold about it |

These say nothing about why it changed. Act on them promptly, because your users expect their choices to reach the copies you hold.

## What you can't work out

Don't try to rebuild what's hidden. Hidden lists are left out of other people's lists and of follow events, and follower history is only available by day for accounts whose lists are public. Trying to get around these rules can get your application suspended.


---

# 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.floral.fun/api-v2/v2-privacy.md?ask=<question>&goal=<user_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.