3.1 Data you provide directly
When you create an account, book a lesson, use our AI features, or contact us, we may collect:
- Account data: Name, email address, password (stored as a cryptographic hash — we never see your actual password), role (skier, school owner, instructor), profile photo.
- Booking data: Lesson type, dates, experience level, number of participants, special requirements, goals and “anything else we should know” notes, and equipment sizing preferences. Free-text fields may contain health information, such as injuries, disabilities, or physical limitations. Providing health information is optional and requires the separate explicit health-data consent before it is processed and shared with the school for lesson planning. Entering text alone does not provide that consent. We treat this as special-category data under GDPR Article 9 and apply the health-data retention period in section 8.
- Communication data: Messages sent through our messaging system are available to the participants and authorised staff where needed for operation, support, moderation, or handling a report. Share health information only where relevant and with the appropriate consent. AI Concierge and school-chatbot conversations have different processing and storage arrangements, described in section 3.5.
- Read receipts: When you read a message, the sender is shown that you have read it, and you are shown the same for messages you send. This is on by default and you can turn it off at any time in your messaging settings — turning it off stops your read status being shared and stops you seeing anyone else's.
- Review data: Star ratings, written reviews, and the school or instructor they relate to. Reviews are published publicly under your first name.
- Gear profile data: Height, weight, ability level, gender, age group, and equipment preferences — used solely for gear recommendations. This data is not used to assess your health.
- Support data: Information you provide in support tickets, including screenshots and descriptions of issues.
- Payment data: We do not store your card details. When you pay online, you enter them in Stripe Checkout, and Stripe processes the payment to the Stripe account of the ski school or instructor you are booking with. We keep the references Stripe returns for the payment, any refund, and any dispute, together with the amount, the currency, and our own commission record for the booking. The ski school or instructor, as the seller, is the data controller for the payment taken on its Stripe account, and Stripe is an independent data controller for the card data it processes for its own fraud-prevention and legal-compliance purposes. See Stripe's Privacy Policy.
3.2 Data collected automatically
When you visit our website, we automatically collect:
- Device data: IP address, browser type and version, operating system, device type, screen resolution, language preference.
- Usage data: Pages visited, time spent on pages, clicks, scroll depth, referring website or search terms. Cloudflare Web Analytics records page views and referring websites without cookies. Google Analytics 4 records the rest, and only if you accept analytics cookies.
- Online status: While you are signed in, providers and instructors are shown in our directories as being online now, and visitors can filter for it. This is derived from when your account was last seen; nothing about your location or activity is collected. It is on by default and can be switched off in your settings.
- Cookie data: See our Cookie Policy for full details.
With Analytics consent, eligible public homepage visitors may see title A, B or C for the assistant orb. Testing is paused until Admin starts it; without Analytics consent you see A or the chosen winner, with no experiment identifier or metrics. A random browser identifier in local storage lasts 30 days and is cleared when Analytics consent is withdrawn. First-party server records retain its hash, experiment run, variant, language and assignment/event timestamps for visible impressions, clicks and successful text replies or voice connections for up to 90 days. They contain no IP address, account ID, profile, messages, transcripts or audio. Private previews, demos, administrators and impersonation sessions are excluded. This visual test does not require AI consent; actual chatting still does. The body and button stay the same, and Admin chooses a winner manually. Withdrawing Analytics stops new measurement; existing server records expire under this retention schedule.
3.3 GPS and location data
If you use our GPS Ski Tracking feature, we collect precise location data including GPS coordinates, speed, elevation, and route waypoints. This data is collected only with your explicit consent and only while you actively use the tracking feature. You can stop tracking at any time. GPS data is stored locally on your device when you're offline and synced to our servers when you reconnect.
You control who sees your GPS data and for how long through your privacy settings. You can delete your GPS data at any time from your dashboard.
3.4 Lesson notes, pre-arrival questionnaires, and progress data
When an instructor uses Quick Notes after a lesson, the recording is uploaded to private storage and sent to a configured speech-to-text processor. The raw transcript, together with any student name, activity and level supplied by the instructor, is then sent to the configured text-model provider to clean the note, generate a title and extract action items. The audio, raw transcript and generated outputs are saved with the note. Authorised instructors, relevant school staff and administrators can access it; the learner or parent can access it when the instructor shares it. Lesson notes may contain health, injury or fitness information and therefore require additional care.
Pre-arrival questionnaires: Some schools send a questionnaire before your lesson that explicitly asks about medical conditions, physical requirements, and equipment sizing. This data is shared with your instructor and school to ensure your safety. The medical fields are disabled by default — you must provide explicit consent before entering medical information. This data is retained for the duration of your booking plus 12 months, then deleted.
Quick Notes itself does not collect a learner consent record and does not offer a manual-only mode. Before recording, the school or instructor must inform the learner or parent and establish consent or another applicable lawful basis, including explicit consent where special-category data is involved. If you decline, ask the provider not to use Quick Notes and request a manually written recap through another agreed channel. Existing notes can be removed through a data privacy request or by contacting us. Removing the storage reference ends in-app access to the private audio; the underlying object is then handled under our private-storage lifecycle or an accelerated deletion request.
3.5 AI chatbot and AI feature data
Live voice and text assistant
The optional live assistant uses OpenAI for text and voice, listing searches and support in customer, school, instructor and administrator dashboards. With your AI & chatbot consent it processes messages, voice transcripts, microphone audio while connected, minimal page/language context and only the authorised records needed for your request. Its full conversation stays in page memory and clears on reload, reset, account change or consent withdrawal. FASS does not save full live transcripts or raw voice audio to its application database and does not use conversations to train or fine-tune models. Server security checks inspect submitted messages/transcripts in memory. OpenAI processing, retention and transfers depend on the applicable service, account settings and terms. Avoid payment credentials and sensitive health information.
After AI & Chatbot consent, the signed-in assistant may automatically send OpenAI your saved account name, self-reported activity and ability, piste comfort, up to eight currently public favourite schools, instructors and resorts per type, and limited completed-booking counts and scheduled hours for learner accounts. These are reference preferences, not verified skill or time skied; bookings may be for other people. Your current request takes precedence. Health information, contact details, birth dates, free-text bios, payment data and other people's profiles are excluded from this automatic context. Guests, demos and support-impersonation sessions do not receive a real account's saved preferences. Information is read for the request or tool; conversations do not train the assistant.
The optional trip brief contains details you apply, such as a country or resort, dates, activity, self-reported ability, adult counts, child ages you enter, lesson format and budget. After AI & chatbot consent, the applied brief can be sent to OpenAI with your next question or when you update a connected voice conversation. Child ages are not inferred from other people or automatically taken from their profiles. Your latest explicit request takes precedence. These are your stated requirements, not verified suitability, a booking quote or confirmed availability.
Saving a trip is a separate choice: you must confirm saving the structured brief and selected public listings to your own account. We store those details, your account reference and timestamps until you delete the plan or account; they are included in account export and erasure. The full conversation and audio are not saved with the plan. Saving or reading a plan does not itself call an AI provider or spend assistant credits. Public shortlist entries are checked again when saved or read and can become unavailable. Loading a plan does not book anything; applied details reach OpenAI only under the AI-consent rules above.
Answer feedback is optional and account-linked. By default we retain only your selected category and topic, an account reference and timestamps. You may separately choose an edited answer excerpt of up to 500 characters, review its redacted preview and explicitly confirm sharing it with FASS. Common contact details, links and credentials are removed, but names or other personal details may remain: check the preview. Authorised administrators review categories and deliberately shared excerpts; report displays omit account identities, but the underlying feedback remains linked to your account. Feedback is not sent to an AI provider or used to train models, and it does not create a support request. You can remove your feedback; retained reports are included in account export and erasure. Reports are excluded from ordinary feedback views after 90 days. Bounded hourly maintenance removes expired rows; physical deletion is not guaranteed at an exact deadline.
Voice requires a deliberate start and microphone permission. After 90 seconds of inactivity microphone input pauses; without continuing within another 30 seconds, voice ends. You can mute, end, reset, withdraw AI consent or download the available text/captions locally, without audio; captions may be incomplete and reset does not erase your downloaded file. The assistant can navigate, filter and highlight when requested. Supported account-name/bio updates, unpublished lesson drafts and authorised booking rescheduling require an exact preview and your separate explicit confirmation. It cannot perform every platform action. The Privacy Policy is a notice, not blanket permission to train. Standard search, forms and human support remain available. Admin can disable the assistant.
Full live history stays in current page memory, not browser local storage or the application database. Reset, reload, account change or withdrawing AI consent clears it. A local download is your copy and contains no audio. After assistant consent/start, an HTTP-only pseudonymous guest cookie (up to 90 days) and keyed network identifiers enforce free allowances and prevent abuse. Server usage/quota and credit receipts contain timestamps, durations, counts and charges, not full transcripts or raw audio; operational records are retained up to 90 days. Security flags contain keyed hashes, categories, counts and expiry, not raw IP or prompts; they expire after 24 hours and are removed by maintenance. Action previews expire after ten minutes, are scrubbed after execution and purged after 24 hours. Minimal audit and required financial records follow their separate retention rules. Account export/erasure includes account-linked operational data. Consent preferences are stored separately. OpenAI processing and retention remain governed by the applicable provider terms. Daily keyed network-quota records are retained for up to two days. Separately, essential assistant service-health statistics contain only hourly totals and coarse response-time distributions, retained for up to 30 days and removed by maintenance. They contain no account, session, guest or network identifiers, page URLs, messages, transcripts or audio; they support reliability and abuse monitoring, separately from optional Analytics measurement. Contextual support is separate from the live conversation. An inline offer does not save your draft text. If you choose Show me how, the selected issue context expires from use within 24 hours and is removed by scheduled maintenance, or scrubbed sooner when assistance ends. Account-linked guide steps, outcomes, a keyed issue fingerprint and event times are retained for up to 30 days, then removed by scheduled maintenance; account export and erasure include these records. Published guidance works without AI credits. An optional AI explanation requires AI & chatbot consent and a deliberate request before a bounded selection of the issue and customer-visible ticket text is sent to the AI provider; internal notes, private staff replies and attachments are excluded. No full live transcript or audio is stored for this feature or used for training. A handoff summary is sent only after you review and confirm it; it becomes an ordinary customer-visible support record subject to the existing support retention rules.
Navigation reliability checks use receipts that expire after 10 minutes and keyed hashes in server memory to bind them to the owner, offered action and access context. A 30-minute report for the current server process counts page loads, applied filters, highlights, failures and cancellations; it contains no routes, filter values, account identifiers, transcripts, audio or IP addresses and clears on restart. These are browser reports, not confirmation that a problem was solved. Streamed draft replies remain temporary page content under the conversation rules above.
An Admin-issued private preview link provides access in one browser for at most 72 hours. Its one-time redemption sets the signed HttpOnly fass_assistant_preview cookie. It grants no extra account or data permissions and bypasses neither AI consent nor credits, rates or safeguards. Server grant records contain hashes, labels and timestamps, not the raw link token; expired or revoked grants are removed after 24 hours by maintenance. Existing authorised QA demos use the signed HttpOnly fass_assistant_demo_scope cookie for at most 3 hours, a fixed fictional school and a separate Admin setting. These requested access/security cookies do not themselves permit optional AI processing or create a self-service temporary account.
When you use our AI-powered features, your queries are sent to the AI provider configured for that feature. The live voice/text assistant uses OpenAI: text and voice transcripts, microphone audio while connected, and the limited listing or permitted customer information needed for requested tools are processed to answer you. The live conversation stays in the current page's memory, and our application does not store raw voice audio. OpenAI's retention and processing depend on the applicable service, account settings, and terms. Other features and fallback routes can change; section 6 describes supported services, and you can ask us which recipients process a feature. What we retain depends on the feature. AI Concierge conversation history is kept in your browser and clears 24 hours after your last message; we do not store those conversations in our database. AI School and Resort Finder queries are different: we log the query text, generated summary, result count, IP address, and your user ID when signed in. If you save an AI search, we also retain its query, summary, filters, and result references with your account. Moderated popular search queries may appear as public search suggestions; your account ID and IP address are not shown with them. A school's own chatbot is different — those conversations are stored for up to 12 months so the school can review them, as described in section 8. You must agree to the chatbot privacy terms before starting a conversation. You are interacting with an AI, not a human.
Find a Ski School does not train AI models on your data — we do not run our own foundation models or fine-tune third-party ones. A provider’s use and retention of inputs and outputs depends on the service, account settings, and applicable contractual terms. Do not assume every supported provider has the same training or retention terms. Contact [email protected] for the active recipient and applicable terms. See section 7 for international transfers and our AI Transparency page for the plain-language breakdown plus opt-out toggles.
3.6 Data from third parties
We may receive personal data from:
- Ski schools: When a school adds instructor profiles or imports student booking data.
- Stripe: Confirmation that a payment, refund, or dispute has taken place on the ski school's or instructor's Stripe account, with its reference, amount, currency, and status, and, for a dispute, the reason and the evidence deadline — never your card number.
- Public sources: Resort, altitude, and weather information, and unclaimed school information discovered through search engines such as Google and collected from school websites or other public professional sources. This can include personal professional information; see section 14.