# Terms of Service — release draft

**Product:** International Press Zone
**Status:** DRAFT — NOT APPROVED FOR CUSTOMER USE
**Technical alignment review:** 2026-08-19

This file is an internal release draft. It intentionally does not invent pricing, trial periods, refund windows, support SLAs, payment methods, jurisdiction clauses, liability caps, or other legal/commercial terms that have not been approved for the current Press.Zone offer. Qualified legal review and business approval are required before customer publication.

## Current product facts that final terms must match

International Press Zone is commercial WordPress software supplied by Press.Zone. The current plugin architecture:

- installs as an authorized plugin ZIP and supports authenticated plugin updates;
- connects a WordPress site to Press.Zone through the current Connect/social-auth flow;
- stores a backend-issued per-site credential server-side in WordPress rather than exposing a customer activation key;
- sends translation requests to the Press.Zone service for AI-assisted translation when the customer uses connected translation features;
- supports synchronous and asynchronous/bulk translation workflows;
- may expose account/billing surfaces when the corresponding commercial backend capability is available.

Stripe checkout/billing is currently waiting on external production clearance. Final terms must describe the payment processor and billing behavior that actually ships. No retired payment architecture or historical activation-credential flow should appear in the final terms.

## Commercial terms to be supplied by business/legal

The final Terms of Service must define, from the live commercial offer rather than this repository:

- contracting entity and customer eligibility;
- current packages, prices, billing period, taxes, renewal behavior, and currency;
- payment processor actually used at launch;
- cancellation and subscription-management behavior;
- refund rights and policy;
- support channels and any response-time commitments;
- permitted number/types of sites or other entitlement limits;
- beta/pre-release treatment where applicable;
- suspension/termination rules;
- warranty/disclaimer language;
- limitation of liability;
- governing law, venue, dispute process, and required consumer-law carve-outs;
- notices and contact details.

## Software and account access

Final terms should distinguish between:

1. the WordPress plugin installed on the customer's site;
2. the customer's Press.Zone account and subscription/entitlement;
3. the per-site credential issued by Press.Zone and stored by WordPress;
4. Press.Zone hosted translation/account services used by the plugin.

They should not instruct customers to share, copy, or manually manage the per-site credential.

## Customer content

Connected translation features can transmit content selected for translation to the Press.Zone service. Final terms must accurately define ownership, permitted processing, retention, deletion, confidentiality, and any subprocessors for that content. Do not use historical statements that claim customer post/translation content is never transmitted: AI translation necessarily sends selected translation content to the service.

## Updates

The plugin contains an authenticated update mechanism. Final terms should state the actual update entitlement and support policy for the purchased package. Technical update integrity and release behavior are governed by the release evidence contract, not by promises invented in this draft.

## Supported scope

Commercial feature commitments must match `docs/launch/FIRST-CUSTOMER-SCOPE.md` for the relevant release. Code existing in the repository, a historical plan, or a dormant UI is not automatically a contractual feature commitment.

## Required approval before go-live

- [ ] Business owner confirms current commercial packages and billing terms.
- [ ] Stripe/payment details match the processor actually cleared for production.
- [ ] Refund/cancellation terms are approved and consistent with checkout/account UI.
- [ ] Support commitments and contacts are approved.
- [ ] Privacy/data-processing terms match the production service and subprocessors.
- [ ] Qualified legal reviewer approves the final customer-facing terms for relevant jurisdictions.
- [ ] Published terms version/date are recorded in the release receipt.