No login, saved profile, or member database is enabled in the current prototype.
Data Request Boundary
WeAcuRe should define unsubscribe, deletion, access, export, and support routing before email collection, checkout, member access, or persistent records are enabled. The current prototype has no live account database, no server-stored chart history, and no active email list.
Current status
The early access form is disabled and does not submit contact records.
Birth data is used locally for study output and should not be mixed into support requests.
Request types to support before launch
- Unsubscribe from email updates after email collection is enabled.
- Delete contact, support, or access records when a persistent provider is used.
- Access or export contact and paid access records after member or checkout systems exist.
- Correct email, market, product interest, or support routing records.
- Remove unsupported or misdirected sensitive requests from product support routing.
First email-list request path
Once an email platform is connected, every email should include its unsubscribe link.
Deletion should remove email, market, language, product interest, and consent status from the provider.
Email-list requests should not require birth data, chart output, or payment card details.
Request data separation
- Keep birth data, chart output, palace labels, star labels, and private study notes out of data request records.
- Keep payment provider references separate from chart input and campaign event records.
- Keep unsubscribe, deletion, access, export, refund, and support states traceable without storing card data or secrets.
- Do not ask users to provide passwords, recovery codes, cookies, identity files, or sensitive chart screenshots.
Before requests are accepted
- Publish a support channel and request type list.
- Document owner, response scope, retention period, provider location, and manual escalation path.
- Update Privacy, Contact, Terms, Support Readiness, Email Consent Boundary, and Membership Readiness.
- Run privacy, security, commerce, and static page checks before connecting any provider.
Related pages
Review Privacy Boundary, Support Intake Boundary, Email Consent Boundary, Membership Readiness, Payment Readiness, Provider Readiness, Policy Review Readiness, Contact, and Terms before enabling data request handling.