Blame
|
1 | # Profiles |
||||||
| 2 | ||||||||
|
3 | Profiles are the public or semi-public representation of an AeThex identity. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Profile role</h2> |
|||||||
| 7 | <p>Profiles help people and systems recognize identity without exposing private account data.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | A profile is connected to [[Passport]], but it is not the same as authentication credentials. Profiles may include display names, avatars, public links, project associations, contribution history, or community context depending on platform settings. |
||||||
| 11 | ||||||||
| 12 | ## Profile data |
|||||||
| 13 | ||||||||
| 14 | - Display identity and avatar. |
|||||||
| 15 | - Public bio or ecosystem role. |
|||||||
| 16 | - Linked project or organization context. |
|||||||
| 17 | - Public contribution signals. |
|||||||
| 18 | - Optional linked accounts, when user-approved. |
|||||||
| 19 | ||||||||
| 20 | ## Privacy guidance |
|||||||
| 21 | ||||||||
| 22 | 1. Keep private account fields out of public profiles. |
|||||||
| 23 | 2. Let users control optional public information. |
|||||||
| 24 | 3. Separate profile visibility from authentication status. |
|||||||
| 25 | 4. Avoid exposing internal IDs unless needed for developers. |
|||||||
| 26 | ||||||||
| 27 | <div class="docs-grid"> |
|||||||
| 28 | <a class="docs-card" href="/Passport">Passport</a> |
|||||||
| 29 | <a class="docs-card" href="/Linked-Accounts">Linked Accounts</a> |
|||||||
| 30 | <a class="docs-card" href="/Security">Security</a> |
|||||||
| 31 | <a class="docs-card" href="/Policies">Policies</a> |
|||||||
| 32 | </div> |
|||||||