Privacy Layer

The privacy layer lets an andee decide who can see parts of their identity context.

It is built around three andee-facing ideas:

A connection exists when one person sends an invitation and the other person accepts it. The connected level uses that accepted relationship as the sharing boundary.

Signals belong to categories. A category setting lets someone choose visibility for a group of related signals at once.

When a category is set to connected, signals in that category are shared with accepted connections. When it is set to public, signals in that category can appear on supported public read surfaces. When it is set to private, signals in that category stay owner-only.

Category settings are useful when many signals should follow one privacy rule.

A signal setting applies to one specific signal.

Use it when one signal needs different visibility than its category. For example:

When a signal has its own setting, that signal setting determines what other people can see.

Owners can see their own signals while managing their identity context. Privacy settings control sharing with other people, not the owner's ability to review their own data.

Accepted connections can see signals whose visibility allows connected access. They do not see owner-only signals.

Public viewers can see signals marked for public access on supported public read surfaces. They do not see connected-only or owner-only signals.

Privacy settings decide who is allowed to see a signal. Shared views also respect signal approval state. A signal should be approved before it appears to someone else through shared profile or read surfaces.

The current privacy layer supports category-level visibility and per-signal visibility with three levels: private, connected, and public.