Your account
HOL-D106Story implementation: Planned

Understand and control what my profile shares

account · Proposed launch phase 1

Start from Home

Review as Registered user · Full workflow planned

User story

As a registered member, I want to understand which profile information is private and which I publish so I can make an informed choice about what others see.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Provide a dedicated Privacy page explaining owner-only account fields and separately published professional fields. Private email, interests, activity, addresses and financial information never appear in public projections.
  • Offer only controls backed by actual publication/access rules. An old Members only label must not imply ordinary Member profile sharing that does not exist.
  • Link to the existing Professional draft/public preview/publication flow for Guide/Creator/Athlete information. A private account edit must not silently publish or overwrite public identity.
  • Changing privacy presentation does not revoke org access, paid membership or staff permissions. General member-directory visibility, profile unpublication, account deletion/export and real-tester recovery require separately defined policy before new actions are built.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin on this account’s permitted Home. For a local review use Sign in → Try a demo account → Alex Morgan → Free Member Home. Settings belong to this same personal account; keep Professional/organization/staff authority separate.

Navigation from sign-in

  1. 01Open the fictional Registered user account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02Begin at this role’s Home, open its account/workspace menu, then Profile & settings when that navigation is delivered. Follow the section named in the checks; stop if a planned destination is unavailable.

Feature checks start here

Understand and control what my profile shares · Full workflow planned

Planned follow-up. Requirements are recorded; the dedicated settings page and backend workflow are not implemented. Current navigation/editor work does not implement this outcome.

  1. 03From the role Home open account menu → Profile & settings → Privacy when available; the dedicated experience is planned.
  2. 04Compare private-field explanations with public Professional preview where one exists; do not publish, unpublish or alter someone else’s profile just to review.
  3. 05Check only delivered controls, saved state and public projection on a dedicated account; record unavailable policy-dependent controls as planned.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Keep private owner RLS and explicit professional/org published projections separate. A stored visibility string is not a data-access policy.
  • Define allowed privacy choices and owner patch semantics against existing actual policies before implementing controls; reject unsupported values.
  • No new ordinary-member public projection, bulk disclosure, unpublication/removal or account deletion/export is authorized by this planned story.

How to verify when implementation is approved

  1. Compare anonymous/owner/other-account projections and verify private fields remain absent.
  2. Verify privacy edits preserve identity/grants/entitlement and cannot bypass explicit publication.

Before this can work

  • Use an existing fictional account; keep its current role/entitlement and selected Home. No profile/preference reset is required to review requirements.
  • Dev only. No real card/address/recipient data, provider setup, outbound delivery or publication is part of this review.

Connected stories