What this build stores, and why

1. Information collected in the current build

The product currently stores account and access information necessary to run the platform, plus moderation and creator-review data that keep the adult-content surface governable.

• Account data such as email address, username, password hash, display name, bio, and email-verification state.
• Safety and trust data such as 18+ acknowledgment, VRChat-linked or manually reviewed age-verification state, creator-application details, reports, block relationships, moderation status, and audit history.
• Product data such as follows, creator posts, uploaded media metadata, and session records used to keep accounts signed in.

2. Why the data is used

Data is used to operate the service, authenticate users, support creator onboarding, personalize discovery, enforce policies, investigate abuse, and comply with legal or platform-safety obligations. The adult-platform part is not optional background flavor; it changes what the system must remember.

• To create and secure accounts, sessions, verification flows, and password recovery.
• To review creator applications, validate publishing rights, and handle moderation or copyright issues.
• To shape feed and discovery surfaces using follows while suppressing blocked or moderated accounts from view.

3. Sharing, access, and retention posture

The current build is self-hosted and intentionally light on third-party integrations. Access to stored data should be limited to administrators or reviewers who need it to operate the service. Moderation and review records may be retained longer than ordinary session data when needed for safety, repeat-offense handling, or legal process.

• Sensitive identity details should be minimized and only kept when operationally necessary.
• Moderation, report, and takedown evidence may need longer retention than casual profile data.
• Dedicated production retention rules still need legal review before public launch.

4. What this build does not do yet

This policy is intentionally honest about scope. The current product slice does not yet include payments, public messaging, ad-tech tracking, or a finalized third-party analytics stack.

• No payments or subscription billing are active in this build.
• No user-facing DMs or group chats are live yet; those remain a later safety-heavy phase.
• No final vendor-backed email, storage, CDN, or analytics commitments should be treated as locked until adult-content policy review is complete.

5. User controls and pending launch work

Users can currently update profile basics, block creators, request password resets, and report accounts or posts. Before public launch, HomieHoppers still needs dedicated privacy-contact instructions and a formal deletion / data-request workflow instead of leaving that topic to improvisation.

If this product proceeds to public launch, privacy rights handling should be revisited with counsel for the target jurisdictions and vendor stack actually chosen.