How SkiIntel handles planning data.

SkiIntel uses account information such as name, email, role, team or academy, and saved profile preferences.

Athlete planning information may include disciplines, points entered by the user, home location, preferred race regions, travel preferences, goals, notes, selected races, and coach availability.

Account connection information may include parent, guardian, coach, academy, or athlete request status, relationship notes, request messages, requested access scopes, approved access scopes, and the accounts involved in an approved connection.

Race-calendar information may include provider-sourced race names, dates, locations, disciplines, timing links, registration links, source credits, and confidence labels.

Suggestions and corrections may include the message submitted by the user, optional name or email, the related page or race link, and basic browser information used to investigate issues.

Profile and planning information is used to personalize race rankings, calendar planning, coach views, and account dashboards.

Approved account connections are used to let a parent, guardian, coach, academy, or admin follow only the athlete profile categories the athlete approved, such as profile basics, points, planning preferences, selected race calendar, or opportunity notes.

Shared race-calendar access shows selected race names, dates, planner status, and official source links. Private planner notes and raw race snapshots are not shared through the account bridge.

SkiIntel uses saved preferences to explain why a race appears relevant or why it may not be practical for a specific athlete.

The platform does not claim a live FIS profile connection unless permitted data has been separately imported or connected.

Feedback submissions are used to review corrections, improve race data, investigate bugs, and prioritize product improvements.

SkiIntel may organize data from approved providers, public calendars, user-entered information, and team-supplied planning details.

Race entries, points, dates, venues, and registration details should be checked against the official organizer, timing provider, federation, coach, or race announcement before final decisions are made.

When data is incomplete or estimated, SkiIntel should show that uncertainty in the product experience.

User-submitted suggestions are not treated as verified platform data until they are reviewed.

Users should only enter athlete information they are allowed to use for race planning.

Parent and coach accounts should request athlete access only when they have a real relationship with that athlete. Athlete profile access should be approved through the in-app request process, and athletes can decline or revoke access.

Account owners can edit profile and planning fields inside SkiIntel. Deletion and export workflows should be handled by the SkiIntel operator until automated account controls are added.