Version date: 2026-09-01
This page documents exactly what Iso Analytics collects and why, matching the answers submitted in the App Store privacy questionnaire. It supplements the Privacy Policy.
| Data type | Collected | Linkage | Tracking | Purpose |
|---|---|---|---|---|
| Contact info (name, email) | Yes | Linked to identity | No | App functionality, account management |
| User content (coach evaluations, notes, missions) | Yes | Linked to identity | No | App functionality |
| Identifiers (user ID, org ID) | Yes | Linked to identity | No | App functionality, security |
| Usage data (screen views, feature use) | Yes | Not linked to identity | No | Analytics, product improvement |
| Diagnostics (crash and error events) | Yes | Not linked to identity | No | App performance |
| Purchases (subscription tier) | Yes | Linked to identity | No | Entitlements and billing support |
| Health, fitness, location, contacts, photos, browsing history, financial info, sensitive info | No | — | No | Not collected |
Fields: Name, email address, sign-in identity
Required: Required
Purpose: Authentication, account security and support
Who can access: The account holder and support staff under logged access
Retention: Kept while the account is active; subject to legal review
Fields: Organization name, team name, season, identity, staff roles
Required: Required
Purpose: Team organization and role-based access control
Who can access: Organization staff assigned to the team
Retention: Kept while the organization is active
Fields: Name, position, height, graduation year, dominant hand
Required: Name required; other fields optional
Purpose: Roster organization and development planning
Who can access: Assigned staff; the player and guardian see approved reports only
Retention: Kept while the player is on an active roster
Fields: Basketball evaluation scores, coach observations, movement observations
Required: Optional
Purpose: Player Role, Development Priority and Player Mission planning
Who can access: Assigned staff only; private by default
Retention: Kept while the player record exists
Fields: Player Role, Development Priority, Player Mission, progress history
Required: Optional
Purpose: Weekly development tracking and coach-approved reporting
Who can access: Assigned staff; player and guardian after coach approval
Retention: Kept while the player record exists
Fields: Guardian name, contact, consent method, status, date
Required: Required when the organization includes players under 13
Purpose: Evidence of guardian authorization for player access
Who can access: Head coach and organization admin
Retention: Retention period pending legal review
Fields: Event type, user, organization, record, timestamp, result
Required: Required
Purpose: Security, accountability and product improvement
Who can access: Organization admin and app owner under logged access
Retention: Retention period pending legal review
Fields: Plan tier, plan change history
Required: Required for paid plans
Purpose: Entitlement management and billing support
Who can access: Organization admin and billing support
Retention: Billing records retained per tax and accounting requirements
Iso Analytics does not use the App Tracking Transparency permission because it performs no cross-app or cross-site tracking. There are no advertising SDKs, no data brokers and no behavioural profiling of minors.
The app requests no camera, photo-library, microphone, contacts, location, health or notification-tracking permissions. There is no image, video or file upload surface anywhere in the product.
We reply within two business days.