docs(qa-261): ajoute documents conformité et scripts QA pour release Android

- Ajoute privacy-policy-v1.md et release-compliance-checklist.md
- Ajoute documents QA gates #238-#243
- Ajoute scripts de validation repo-only et device runbooks
- Prépare checklists exécutables avant upload Play fermé

Ticket #261

docs/legal/privacy-policy-v1.md

@@ -0,0 +1,91 @@
+# GameTime Privacy Policy
+
+Version: 1.0
+Effective date: 2026-08-22
+Status: repo reference draft for release preparation
+
+## Scope
+
+This policy covers the GameTime mobile app, including the Android phone app,
+the optional Wear OS companion, account features, sharing, synchronization,
+purchase entitlement checks, and optional Health Connect integration.
+
+## Data We Handle
+
+GameTime is designed as an offline-first workout tracker. Depending on the
+features used, the app may handle:
+
+- workout library content created by the user, including exercises, programs,
+  workout templates, timers, scores, repetitions, session history, and local
+  media selected for exercises
+- account identifiers such as email address and authentication tokens when the
+  user creates an account or signs in
+- shared workout resources and recipient email addresses when the sharing
+  feature is used
+- purchase entitlement status needed to determine whether the account is on the
+  Free or Pro plan
+- optional workout telemetry such as heart rate, distance, calories, and
+  exercise records when the user explicitly enables Health Connect integration
+- optional live workout state and commands exchanged with the Wear OS companion
+
+## Free and Pro Features
+
+Sharing remains free. The Free plan limits the editable workout library, not
+basic workout execution. Imported or shared resources count toward the
+receiving account's quota when accepted. Pro provides unlimited library capacity
+and synchronization.
+
+The Wear OS companion and Health Connect integration are free features and are
+not paywalled.
+
+## Local Storage and Offline Use
+
+Workout data is stored locally on the device first. The app is intended to keep
+working without network access, including before any server synchronization has
+been configured.
+
+## Synchronization and Sharing
+
+When synchronization is enabled, workout library and account data may be sent to
+the GameTime server so the account can restore or synchronize data. When sharing
+is used, the selected resources and recipient identifiers are sent to the server
+so recipients can receive, accept, decline, or revoke shares.
+
+## Health Connect
+
+Health Connect access is optional. GameTime requests only the health permissions
+needed for the enabled workout features. Health data is used to support workout
+tracking and export flows shown in the app. The user can revoke Health Connect
+permissions from Android settings.
+
+## Wear OS Companion
+
+The Wear OS companion exchanges live session state, commands, and available
+metrics with the phone app. The companion is optional and depends on the Android
+Wear Data Layer between paired devices.
+
+## Purchases and Entitlements
+
+Purchase and entitlement data is used to unlock Pro functionality such as
+unlimited library capacity and synchronization. GameTime does not use purchase
+state to restrict sharing, the Wear OS companion, Health Connect, or basic
+workout execution.
+
+## Data Retention and Deletion
+
+Local workout data remains on the device until the user deletes it or removes
+the app. Server-side account, synchronization, sharing, and entitlement data
+requires an operational account management process before public release.
+
+## Security
+
+Release Android builds must use HTTPS for remote GameTime server traffic.
+Cleartext HTTP is permitted only for local debug/profile development builds.
+Authentication tokens are treated as sensitive credentials and should be stored
+through the platform secure storage adapter.
+
+## Contact
+
+Before public distribution, replace this section with the legal support contact
+and the public URL that will be submitted to the Play Console.
+