App Store privacy declarations for STATIQ

Version 1.4 (draft) · Owner: JIWA HOLDING AS · Last updated: 2026-10-07 · Source: actual data processing in the app

This is the basis for the next native build. App Store Connect readback on 7 October 2026 shows eleven published data types, including Fitness, Performance Data and Other Diagnostic Data. Purchase History is missing from both the published label and build 20's manifest. The table below includes the correction; its publication has not been confirmed. The App Privacy answers and manifest must be checked against the exact next native build before submission.

useSessionDiagnostics sends one minimized row per signed-in startup to pilot_feedback. The row contains the app version, platform, previousSessionUnclean flag and unsyncedEvents counter. It is linked to the account's workspace. It contains no crash report, performance measurement, player identity or free text. The startup event is declared as Product Interaction, while the technical flags and counters are declared as Other Diagnostic Data. Optional product analytics also uses Product Interaction, with Analytics as an additional purpose.

Performance Data comes from a separate server flow: game_events retains the device event time and server receipt time. ops_metrics calculates the median and 95th percentile of sync delay. The account/workspace link remains even though the operational view shows aggregates. This supports Performance Data for App Functionality, including without an analytics SDK. Fitness covers recorded individual basketball activity and performance; this does not mean the app collects medical information or uses HealthKit.

The StoreKit flow sends transaction references to the server, which retains the product, subscription status and period linked to the workspace. Purchase History is therefore declared for App Functionality, linked to the user, without tracking. Apple handles the payment card; STATIQ does not receive card data. Supabase Auth security logs process the account, timestamp, IP address and User-Agent, among other fields. These network and security signals support Other Data Types; IP is not used for the country selection in product analytics.

The user may also send manual feedback containing free text. This is stored separately as kind = feedback in pilot_feedback and linked to the workspace. In App Store Connect it is declared as User Content → Customer Support, collected and linked to the user, with App Functionality as the purpose and no tracking. The guidance asks users to avoid names and other personal data, but the field is still free-form user content and must be declared.

The app can display multiple workspaces to which the account has been invited. Workspace ID, role and read-only status are processed as app functionality linked to the user. The invitation token is used only during redemption and is not stored on the device afterward. This introduces no new Apple data type beyond the identifiers and user content already declared in the table.

• Tracking and ATT: No. STATIQ uses no advertising ID and does not track users across other companies' apps or websites.
• Kids Category: No. The app is for adult team managers. Game statistics use jersey numbers and optional nicknames. Optional player names may be imported on the web into a separate protected roster; the App Store disclosure must be checked against this before submission.
• In-app account deletion: Yes, under Account and privacy → Delete account, with a cancellation period.
• Privacy notice: https://statiqsport.com/legal/personvernerklaering.
• Terms: https://statiqsport.com/legal/vilkaar.
• Support: https://statiqsport.com/stotte.
• Website: https://statiqsport.com/.
• App Review account: Planned address: review@statiqsport.com. No working reviewer account has been confirmed. An account with synthetic data must be ready and tested in the latest native build before submission.

The production and native build 20 basis is source 6c0b6ff2deaafc4bf500ffe2cdaa50f3539eb16d. Build 20 has been uploaded and has Validated status in App Store Connect. This does not confirm physical acceptance testing or App Review approval. Build 21 with the corrected purchase history manifest is planned; a signed build, upload and provider readback remain pending. Sign-in with the App Review account must be tested in the build to be submitted.

Optional product analytics (2026-10-05)

These data are linked to your account and available only to the platform administrator with two-factor authentication. The purpose is to improve the product, based on your voluntary consent. Country is your own selection, not GPS or inferred from an IP address. No analytics SDK, analytics cookies, screen recordings, keystroke content or player data are included. Your choice is saved to your account. Measurements are deleted after 90 days, immediately on withdrawal or when you request account deletion. Your measurements are included in your account export. Name, email, access and last known sign-in are used separately for necessary access administration.

Apple: Product Interaction, User ID → Analytics; Coarse Location (optional country) → Analytics. Linked to user: yes. Tracking: no.

Ongoing collection after an initial consent must still be disclosed. See Apple App Privacy, Apple's manifest guidance and Supabase Auth Audit Logs.