The current early access form is disabled and does not submit an email address.
Email Consent Boundary
Email can invite early users back when study products are ready, but only after clear consent, an unsubscribe path, and a documented provider boundary are in place.
Current status
Future messages should stay limited to early access, product readiness, and study updates.
SMS stays separate and requires its own explicit consent before use.
Before email collection is enabled
- Use a public support email on the WeAcuRe domain.
- Review the Support Readiness path.
- Choose a hosted form or email platform that records consent.
- Review the Provider Readiness checklist.
- Explain what users will receive before email submission.
- Provide an unsubscribe path before sending any update.
- Review Data Request Boundary before accepting unsubscribe or deletion requests.
- Keep email interest separate from birth data, chart output, and payment support.
First email fields
Collect email, explicit consent, source, and date in the provider record.
Collect product interest, market, and language only to route readiness updates.
Do not collect birth date, birth time, chart output, or private study notes in the email form.
Consent wording
The first live form should use a clear checkbox such as: I agree to receive WeAcuRe early access and product readiness updates by email. Each message should include unsubscribe wording, and support must process deletion requests.
Unsubscribe and deletion path
- Every email should include a provider unsubscribe link once connected.
- Before provider automation is ready, requests should route to the public support email.
- Deletion requests should remove the email contact record and preference fields from the provider.
- Payment receipts, support records, and email records stay separate unless the user asks for access support.
Reactivation boundary
Future reactivation messages should be sparse, product-related, and easy to leave. They should not include chart details, private birth data, or personal outcome claims.
Reactivation cadence
- Send only after explicit email consent and provider review are complete.
- Limit early reactivation to product readiness, study pack access, glossary updates, or support notices.
- Keep birthday input, chart output, palace labels, and private study notes out of email segments.
- Include unsubscribe wording in every reactivation message.
- Pause reactivation if support, refund, privacy, delivery, or policy questions increase.
- Review the Email Reactivation Runbook before sending notices.
Reactivation record
- Record consent source, message purpose, market, send date, and unsubscribe path before sending.
- Record whether the message points to Pricing, Early Access, Learning Hub, or a study product notice.
- Do not use birth data, chart output, paid support records, or campaign identifiers to create message groups.
Related pages
Review Early Access, Email Reactivation Runbook, Payment Readiness, Provider Readiness, Privacy Boundary, Data Request Boundary, Birth Data Privacy, and Support Readiness, and Contact.