Start with Source Notes Pack; keep clean export and glossary access later.
Delivery Readiness
WeAcuRe should define Source Notes Pack delivery before checkout is enabled. Delivery records should support access, refunds, and help requests without storing birth data, chart output, or private notes.
Delivery posture
Email or provider-hosted download can support the first paid product.
Delivery records should not contain birth data, chart output, or private notes.
Before paid delivery
- Define Source Notes Pack access period, file format, update scope, and support route.
- Confirm whether access is delivered by email, hosted download, member link, or provider receipt.
- Keep delivery status separate from chart input, browser-local output, campaign records, and source drafts.
- Review source copyright status before any study pack contains quotes, scans, or downloads.
- Review Source Download Boundary before delivering source files.
Before clean export or glossary access
- Explain what the export contains: chart labels, vocabulary notes, source status, and use boundaries.
- Do not include hidden tracking data, private fixtures, raw OCR files, or private Obsidian notes.
- Keep saved chart history disabled unless users clearly choose an account feature later.
- Review browser, privacy, and membership boundaries before persistent access is enabled.
Before refunds or access support
- Record payment status, delivery state, product name, support state, and refund state.
- Use the public support route for duplicate payment, unavailable access, and delivery questions.
- Keep provider receipts and support messages separate from birth data and chart output.
- Pause checkout if delivery or support questions cannot be answered clearly.
Related pages
Review Pricing, Payment Readiness, Provider Readiness, Membership Readiness, Refund Policy, Support Readiness, Source Copyright Readiness, Source Download Boundary, Privacy Boundary, and Terms before paid delivery.