# Stage 2 — Blank-field and decision index

The owner directed: **leave unresolved details blank for later completion, with space and an index**. No choice of jurisdiction, age threshold, legal entity, pricing/refund policy, warranty allocation, liability cap or arbitration has been inferred from the device location, language choices, app name, repository account or Japanese reference prices.

Fill each field below and replace its matching token in [03-TERMS-OF-SERVICE.md](03-TERMS-OF-SERVICE.md). The same field ID always has the same value. A blank is **unresolved**, not a waiver, a zero-dollar cap or a statement that the rule is unnecessary. F16, F22 and F23 are reviewer/future-release decisions rather than current user obligations.

| Field | Fill in | Location / decision needed |
| --- | --- | --- |
| F01 | ______________________________ | Terms opening: effective date and version identifier; do not backdate acceptance. |
| F02 | ______________________________ | Terms opening/§16: full legal name of contracting operator and, if applicable, trading name/registration identifier. “CRZ Training” is only the established product name. |
| F03 | ______________________________ | Terms §16: registered/contact postal address; add developer telephone contact if required by the chosen distribution/legal arrangement. |
| F04 | ______________________________ | Terms §§10, 16: monitored legal/privacy/support email for requests and complaints. No address is established by source. |
| F05 | ______________________________ | Terms §16: HTTPS support/contact URL and the actual process staffed behind it. |
| F06 | ______________________________ | Terms §2: minimum age. Consider contract capacity, airsoft use, local safety rules and chosen launch markets; code has no age gate. |
| F07 | ______________________________ | Terms §2: whether minors may use the app; if yes, guardian agreement, supervision and verification arrangements. Do not describe a guardian mechanism that has not been implemented. |
| F08 | ______________________________ | Terms §2: offered countries/territories and any legally necessary eligibility restrictions. No geographic blocking is proven by the audit. |
| F09 | ______________________________ | Terms §1: exact mechanism/location for making terms available and obtaining acceptance, including optional account use and records of document version. Current onboarding does not implement acceptance. |
| F10 | ______________________________ | Terms §8: published Privacy Policy HTTPS URL. The policy must match current automatic session sync, provider processing, derived waveform/video audio, retention and deletion operations. No Privacy Policy is drafted by this package. |
| F11 | ______________________________ | Terms §14: public Terms HTTPS URL and version archive/location. App configuration exists, but no publication is established. |
| F12 | ______________________________ | Terms §6/reviewer notes: decide service-terms vs software-EULA arrangement, confirm App Store/TestFlight/internal distribution, any Apple Standard/custom EULA selection, IP chain of title and required license notices. Current draft preserves separate licenses; it is not a custom Apple EULA. |
| F13 | ______________________________ | Terms §11: approved warranty/disclaimer language, applicable statutory guarantees, beta availability/support posture. No blanket “as is” allocation has been selected. |
| F14 | ______________________________ | Terms §12: legally permitted categories of excluded/limited damages and necessary carve-outs. Consider injury, fraud, intent/gross negligence, privacy and non-excludable consumer rights under actual law. |
| F15 | ______________________________ | Terms §12: liability-cap formula, period, amount/currency and treatment of Free/beta users; exceptions. No cap is assumed. |
| F16 | ______________________________ | Terms reviewer notes only: decide whether an indemnity is needed at all; no indemnification, defense-cost transfer or operator control of users' claims is in the operative draft. If requested later, counsel must scope it to actual service risks and applicable law. |
| F17 | ______________________________ | Terms §15: governing law; retain mandatory consumer protections. The user's Japan timezone is not a jurisdiction instruction. |
| F18 | ______________________________ | Terms §15: courts/venue and any pre-dispute process. No arbitration, class-action waiver, claim deadline or exclusive foreign venue has been assumed. |
| F19 | ______________________________ | Terms §13: beta/cloud access restriction or withdrawal policy, grounds, notice, emergency handling, complaint/review route and treatment of retained data. Operator grant revocation exists; general moderation/appeals do not. Avoid remote-local-wipe or offline-disable claims. |
| F20 | ______________________________ | Terms §10: actual identity/media cleanup timetable, worker owner/schedule, retained-data purposes/categories/durations, provider-backup treatment and privacy request handling. Resolve failed/blocked deletion before promising a deadline; no indefinite retention authority is supplied by this blank. |
| F21 | ______________________________ | Terms §14: how material changes are notified, advance notice period and when renewed acceptance is needed. Publish/implement the chosen method; no mass email, push notification or assent tracking mechanism is proven. |
| F22 | ______________________________ | **Future paid launch only:** approved products, monthly/annual storefront prices/currencies, taxes, auto-renewal timing/authorization, price-change notices, trial policy (if any), entitlements and expiry. Source UI's ¥900/¥9,000 reference is not a confirmed price. No paid terms activate through filling this field alone. |
| F23 | ______________________________ | **Future paid launch only:** cancellation effective date, Apple refund route plus operator remedies/statutory withdrawal rights, restore/account linking, family sharing, grace/billing retry and handling of retained data. Do not choose a blanket no-refund policy or cancellation penalty by default. |
| F24 | ______________________________ | Terms §17: controlling contract language and market-specific consumer addenda/disclosures. EN/JA/zh-TW app translations do not establish legal translations or precedence. |

## Assumptions used in the draft

These are labeled drafting choices, not facts supposedly proven by code:

1. The agreement describes the **currently implemented offline app plus configured private-beta account/session-sync offering**. Paid checkout, AI Coach, cloud-video services and unverified future capabilities are not included as purchased benefits. This follows release gates and the current source, not a prediction about launch.
2. Users retain whatever rights they have in their material. Permission for the operator/providers is narrow and limited to delivering selected features and approved retention. No transfer of ownership, promotional use or AI-training permission is proposed. Legal chain of title still needs review.
3. Acceptable-use language addresses lawful/safe airsoft activity, recording permissions, unauthorized account/data access, entitlement evasion and service disruption. It is a proposed contractual boundary; the app does not automatically monitor or enforce every prohibition.
4. Separate software/open-source/provider agreements remain applicable to their subject matter. This service draft does not cancel the root MIT notice, select a custom App Store EULA or require users to accept infrastructure vendors' business contracts.
5. Mandatory consumer/privacy rights remain protected; no indemnity, arbitration, class waiver, paid-trial conversion or blanket non-refund term has been selected. Warranty and liability allocations await F13–F15.

## Before publication

- Fill applicable fields, including actual contact/privacy URLs and the agreed acceptance/change mechanisms. Remove internal preparation text and reviewer notes from the version shown to users, retaining a reviewed copy here.
- Resolve the audit's misleading sync, backup/import and local deletion descriptions; document reliable cloud/identity cleanup and statutory request handling. Contract disclaimers do not fix these product gaps.
- Review eligibility, safety, consumer/digital-service guarantees, subscription rules, privacy requests and any mandatory seller disclosures for the actual markets. App language choices alone do not determine these obligations.
- Confirm distribution-license compatibility and open-source/font/model/brand permissions. If designating a custom Apple EULA, obtain a reviewed agreement containing all required minimum provisions; do not upload this service draft unchanged as one.
- Before accepting payment, complete F22/F23, revise the terms around the actual checkout/renewal/refund experience and validate store/RevenueCat flows. Before enabling Coach or cloud video, reassess limits, content/provider rights, privacy, retention and safety/output disclaimers.
- Have a qualified attorney review the completed documents and the shipping product before publication. These blanks intentionally prevent an unsupported claim that the current draft is legally final.