Estate MVPThis is a pre-launch policy draft, not a commercial promise. Estate MVP is using test-mode billing. The operator must choose the positions marked below and counsel must approve the final policy before a live charge is accepted.
Information shown before purchase
Checkout should clearly display the selected plan, price, currency, monthly billing interval, trial terms, recurring renewal, included limits, any usage-based charge, and how to cancel. A customer should affirmatively authorize the subscription before Stripe creates it. The application should retain the plan and policy version associated with checkout.
Trial
The current product configuration provides a 7-day trial without requiring a card. At the end of that trial, a workspace without an active paid subscription loses paid write access; it is not silently charged. Counsel should confirm how trial reminders, conversion, data export, and deletion are described.
Monthly renewal
The intended plans renew monthly until canceled. Before launch, Stripe prices and the customer-facing pricing page must agree exactly. The final policy must state the renewal date, failed-payment treatment, how price changes are announced, and whether taxes are additional. A first failed payment does not immediately erase customer data.
Cancellation
Customers should be able to cancel through Stripe's billing portal or by contacting billing@estatemvp.com. The intended default is to stop renewal and preserve access through the already-paid period. Counsel and the operator must approve that position, define exceptional immediate termination, and state how long exports remain available.
Refund decision still required
Before launch, the operator must choose and counsel must approve whether ordinary monthly charges are non-refundable, whether a short first-purchase window is offered, and whether unused time is prorated. Regardless of that choice, duplicate charges, unauthorized charges, technical billing errors, and rights that cannot legally be waived need a clear review path. No unstated refund promise should be made by support or marketing.
Usage-based messaging charges
Only provider-confirmed delivery can become billable usage. Prepared, queued, blocked, failed, suppressed, or expired-before-send messages are not billable. If a confirmed delivery later hard-bounces, the usage entry is reversed while preserving the audit record. The final policy must state the measurement period, included quantity, overage price, customer spend cap, correction procedure, and treatment after cancellation.
Billing questions and disputes
- Email billing@estatemvp.com with the account email, invoice date, amount, and reason for the dispute.
- Do not send full card numbers, bank credentials, passwords, or API keys.
- Estate MVP should acknowledge the request, preserve relevant records, and investigate the Stripe event and application usage record.
- The final policy must set a reasonable response target without restricting non-waivable chargeback or statutory rights.
Changes required before launch
- Insert the exact LLC legal name and mailing address.
- Approve a refund rule and any first-purchase exception.
- Confirm cancellation timing, access after cancellation, and export availability.
- Confirm tax, price-change, failed-payment, and usage-adjustment language.
- Test trial, checkout, renewal, cancellation, refund, payment failure, and dispute flows in Stripe test mode.