Membership Readiness

WeAcuRe should validate paid interest and user retention with the smallest account surface that can support access delivery, consent, support, and deletion requests. The current prototype has no live login, no stored profile, and no active member database.

Current status

Smallest useful membership model

• Email-based access can be enough for the first paid study packs.
• Route paid interest through Checkout Intent Boundary before live checkout.
• Review Delivery Readiness before paid access delivery.
• Paid access records should store product, payment status, delivery state, and support state.
• Birth data and chart output should stay separate from payment, campaign, and support records.
• Saved chart history should wait until users clearly choose to create an account feature.
• Any member area should explain export, deletion, refund, and support paths before launch.
• Review Data Request Boundary before persistent member records are enabled.

Before login is enabled

• Choose the account provider and document what it stores.
• Use hosted authentication or a managed identity service before custom password storage.
• Review the Provider Readiness checklist.
• Confirm rate limits, verification email, session expiry, and account deletion flow.
• Update Privacy, Terms, Contact, Payment Readiness, and Email Consent Boundary.
• Keep account identifiers out of static source files and public repository history.

Before member reactivation

• Collect email consent separately from product delivery notices.
• Do not require birth date, chart output, or private notes to receive product updates.
• Use clear unsubscribe wording before any reactivation email is sent.
• Treat SMS as a later optional channel with separate explicit consent.

Related pages

Review Pricing, Early Access, Checkout Intent Boundary, Payment Readiness, Delivery Readiness, Provider Readiness, Email Consent Boundary, Data Request Boundary, Birth Data Privacy, Privacy Boundary, Terms, and Contact before enabling member access.