Who provides SKIORA
SKIORA is provided by Watson Studio. Questions about this policy or your data can be sent to support@watsonstudio.app.
Location and background recording
SKIORA requests precise location when you tap Start, before ride recording begins. While that ride is active, your device may continue recording after the app is sent to the background. Recording stops when you finish or discard the ride, revoke permission, or the operating system stops it.
SKIORA does not request Android background-location permission. On Android, an active recording uses a visible foreground-service notification. On iOS, location recording can continue for the active ride under the permission shown by the operating system.
Data stored on your device and GPX export
Raw coordinates, sample timestamps, altitude and GPS accuracy are kept in a protected local SQLite ride journal and are not uploaded automatically. You can explicitly choose Export GPX for a completed ride and then select a recipient in the operating-system share sheet. The selected app, service or person receives and processes that user-shared GPX file under its own terms; SKIORA does not choose the recipient or automatically send the file to Watson Studio. Language, selected resort, trip plans, checklists and app preferences are also stored locally for offline use. Local data remains until you erase it or remove the app, subject to your device backup settings.
Maps, assistant and network providers
Interactive online maps request vector tiles and styles from OpenFreeMap and display-only elevation tiles from the Mapzen Terrain Tiles dataset hosted by AWS Open Data. Those providers may receive normal network information such as your IP address and the tile coordinates requested by your device. If the online basemap cannot load, bundled piste and lift geometry, the bounded display route and current live-group points remain visible over a local fallback. SKIORA does not use the public OpenStreetMap tile service for offline or bulk downloads.
Canonical provider, policy and source documents: OpenFreeMap service; OpenFreeMap Terms of Service; OpenFreeMap Privacy Policy; AWS Open Data Terrain Tiles registry; and Mapzen joerd attribution and source licences. These external pages describe the relevant service and dataset terms and attribution requirements. Linking to them does not create an SLA, a continued-availability promise, or permission for bulk or offline tile downloading.
After sign-in, SKIORA loads the current public Georgia resort and place catalog, including published resort status and prices, through an unauthenticated HTTPS GET request to watsonstudio.app. The request has no body and omits cookies and Firebase credentials; it does not include your Firebase UID, precise device location, ride routes, assistant question or advertising identifier. The server necessarily receives normal network information such as the IP address to return the catalog, but does not write routine request/access logs. A server-provided ETag can be sent back only to check whether this shared catalog version changed; it is not a user or device identifier. The last successfully validated catalog can be stored on your device for availability and offline fallback.
When you ask the assistant while online, your question, selected resort, app language, a random request ID and the client time are sent over encrypted HTTPS only to the SKIORA service at watsonstudio.app to retrieve and validate a source-backed answer. Precise location, Firebase UID and ride routes are never included. Version 1 answers only from SKIORA-reviewed data and does not forward the question to DeepSeek or any other third-party AI or model provider. The request body is not logged and is discarded after answering. The service keeps the IP address only in memory for abuse-rate limiting and deletes its bucket when the five-minute rate-limit window expires; it does not write routine request/access logs. If the assistant service is unavailable, SKIORA answers from bundled reviewed data. Opening a cited source sends a normal web request to the selected external website.
Resort piste and lift geometry is derived from OpenStreetMap data under the Open Database Licence and is shown with attribution. Applicable basemap and Terrain Tiles credits are shown directly below every map and remain available through the map attribution control.
Firebase account, cloud sync and private groups
SKIORA requires a Firebase-backed account. You can register with email and password or sign in with Google or Apple. Firebase processes your permanent UID, sign-in provider, email address and any name or photo supplied by the provider, together with limited app, SDK, device and operating-system metadata needed to provide and protect the service. SKIORA does not use these identifiers for advertising or cross-app tracking.
Firestore links cloud data to your UID and syncs profile preferences, trip data, ride summaries, ride start and end times, statistics and a bounded display route. The display route contains precise coordinate pairs so your completed ride can be shown on a map, but excludes raw sample timestamps, GPS accuracy and altitude. Raw ride samples and the full local journal remain on your device unless you explicitly export a GPX file as described above.
Private-group membership includes the resort, private invite code, account member IDs and expiry time. Security rules end invite and membership access within eight hours. Only after separate in-app consent, the single current live-group record contains exact latitude/longitude, an expiry of up to two minutes, a coarse piste/lift/freeride/stopped/unknown state, a sharing marker and, when available, a human-readable piste or lift name. Every update replaces the previous point. Raw sample time, GPS accuracy, ride/session IDs, classification confidence, internal matched-object IDs, consent timestamps, routes and location history are not included. Sharing can be stopped at any time.
Firebase Crashlytics collection is disabled by default and remains off unless you give consent. SKIORA does not sell personal information.
Published reviews and safety controls
Version 1.0 does not allow users to accept the review-creation policy, submit a new review or edit review content. It can display already-published first-party place reviews. For a foreign published review, an authenticated user can select Report, Hide review or Block rider. Report sends the review ID, reporter UID, one bounded selected reason, status and timestamps privately to moderation. Hide and block store reversible owner-scoped review or author identifiers so those filters sync across the user's signed-in devices.
Report, hide and block are independent: reporting does not silently hide or block, and hiding or blocking does not create a report. A deterministic report path limits one report per account and review. A human operator can approve a reported published review in place or hide it; an explicit later decision can unhide it. The moderation audit stores an operational review identifier, canonical content hash, policy version, action, bounded reason, operator identifier, report count and timestamp. It does not copy review text, profile data, email addresses or separate author/reporter fields.
Account deletion removes reports created by the account, owned hide/block choices and stale hide/block references to the deleted account. If review creation is enabled in a later release, this policy will be updated to cover policy acceptance and submitted review data before that feature is made available.
Purchases
When subscriptions are available, Apple or Google processes payment and provides purchase status to Adapty so SKIORA can link access to your signed-in account and restore it on your devices. Store account and payment-card details are not provided to SKIORA. The store confirms the final price, renewal period and any trial before purchase. Deleting your SKIORA account does not cancel an Apple or Google subscription; subscriptions must be managed separately through the store.
Your controls
- Deny or revoke location access in system settings.
- Pause, finish or discard an active ride from the app.
- Explicitly export a completed ride as GPX and choose its recipient in the operating-system share sheet.
- Use “Erase all local data” to sign out and remove local rides, raw tracking samples, trip plans and preferences from that device without deleting your Firebase account or cloud copy.
- Use “Delete account” in the app to reauthenticate and request permanent deletion of the Firebase account and account-scoped cloud data. This does not cancel an Apple or Google subscription.
- For a foreign published review, use Report for moderation, Hide review for one item, Block rider for that rider's reviews, and the account controls to restore or unblock.
- Request deletion, privacy or moderation assistance by emailing support@watsonstudio.app.
- Remove the app and its remaining local data through the operating system.
Children, retention and changes
SKIORA is not directed to children under the minimum digital-consent age applicable in their country. Local ride data is retained on the device until you remove it as described above. Account-linked cloud data, including review safety controls and reports, is retained while the account is active or until deletion is requested, subject to applicable legal obligations. Private-group membership access ends within eight hours and live-point access ends within two minutes.
We may update this policy as the product changes. The effective date at the top will be revised, and material changes will be presented in the app where required.