This is a placeholder template, not legal advice. Have an actual lawyer review and adapt this before you take real signups — requirements vary by jurisdiction and by what you actually promise users.
[Describe the alias-generation and forwarding service in plain terms.]
[Eligibility, account security responsibilities, acceptable use.]
[Price, billing cycle, renewal policy, refund policy — tie this to your actual Pesapal/payments-service configuration and the grace-period behavior described in README-deploy.md.]
[Cross-reference your Privacy Policy. Be specific that the operator holds each user's master seed and real inbox address server-side — see the architecture note in the main README for why.]
[Standard disclaimers, uptime expectations if any, liability caps.]
[Grounds for suspending/terminating an account, and what happens to existing aliases and forwarded mail on termination.]
[How and when you'll notify users of changes.]
[Support/legal contact address.]