# Refund Policy — release draft

**Product:** International Press Zone
**Status:** DRAFT — COMMERCIAL/LEGAL TERMS NOT YET APPROVED
**Technical alignment review:** 2026-08-19

The previous file contained historical package prices, customer activation-credential instructions, payment-provider assumptions, refund windows, trial periods, upgrade arithmetic, and support SLAs that are not authoritative for the current product. Those values have been removed rather than guessed.

## Final policy must be sourced from the live offer

Before commercial go-live, Press.Zone must approve and publish the actual policy covering:

- refund eligibility and any statutory rights;
- any voluntary money-back period;
- renewal-charge treatment;
- cancellation timing and effect;
- partial refunds, upgrades, downgrades, and credits if offered;
- chargeback handling;
- payment processor actually used in production;
- expected refund-processing times that Press.Zone can actually meet;
- customer support/contact route for refund requests;
- treatment of enterprise/custom agreements if such agreements are sold.

## Current architecture constraints

The final policy must use the current account/subscription identity rather than asking a customer for a retired activation credential. Customer identity should be resolved through the Press.Zone account and transaction/subscription records available in the production billing system.

Stripe production clearance is pending. Do not publish Stripe-specific refund instructions until the live processor/account behavior is available and verified. Do not restore historical payment-provider instructions as a temporary substitute.

## Product-data behavior after refund/cancellation

Any statement about what remains on the customer's WordPress site, what hosted account data is retained/deleted, whether connected credentials are revoked, and whether translation service access stops must be verified against the actual production backend before publication.

## Required approval before go-live

- [ ] Business owner approves refund/cancellation policy.
- [ ] Legal reviewer confirms required consumer-law treatment for target jurisdictions.
- [ ] Production payment processor behavior matches the written policy.
- [ ] Account/portal UI uses the same cancellation/refund terminology.
- [ ] Support route is real and monitored.
- [ ] Published policy version/date are recorded in the release receipt.