The live assistant uses OpenAI for text and realtime voice. Voice mode sends microphone audio while connected, and supported tools retrieve listing data or permitted customer information to answer a request. The current conversation stays in page memory; our application does not store raw voice audio. OpenAI processing and retention depend on the applicable account settings and terms. Other AI features use configurable providers. Quick Lesson Notes sends recordings to its speech-to-text service and transcripts/context to its selected text-model provider. Supported providers include Anthropic, OpenAI, Google, Groq, Together AI, Mistral, DeepSeek, OpenRouter and xAI. Ask us for the active subprocessor list.
Find a Ski School does not train AI models on your data. We don't run our own foundation models, and we don't fine-tune third-party models on your queries, conversations or profile. That promise doesn't depend on any third party and stays constant.
What the providers do with the inputs we send is governed by the contract and Data Processing Addendum for the provider active at the time. The provider can change, so the links below are examples rather than a complete current list. Contact [email protected] for the active provider and applicable terms.
Training and provider-side retention terms differ by provider and may change. The applicable contract for the active provider is authoritative; do not assume the same retention period applies to every supported provider.
What crosses the boundary:
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.
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.
We keep limited technical records to investigate assistant connection failures: a random support reference, observation times, the type of assistant operation, and fixed diagnostic codes, stages, status and configuration-field names. We do not attach account, guest, session, call or IP/network identifiers, page URLs, messages, prompts, transcripts, audio or raw provider/error responses. Shared storage holds at most 1000 references; authorised Admin views show the latest 40. Records are excluded from those views 24 hours after the last observation; bounded scheduled maintenance removes expired records without guaranteeing deletion at the exact expiry time. If shared storage is unavailable, this server may show a five-minute local fallback that is lost on restart and labelled incomplete. These records are not sent to an AI provider or used for model training. A reference you supply in a support request may connect that failure to your case under the ordinary support-retention rules.
- To providers: entity facts used for overviews, AI Finder queries, gear-questionnaire answers, chatbot messages and, when Quick Lesson Notes is used, the audio recording, raw transcript and any student name, activity or level supplied. The text provider receives the transcript to clean it, generate a title and extract action items. When an instructor asks for a profile draft (a bio, a summary, or a speciality line), the text provider receives facts from their saved profile, such as their bio, specialities, qualifications, languages, where they teach, and when they started. The live assistant also receives microphone audio while voice is connected, text and voice transcripts, page context, requested listing data and limited details of your own upcoming bookings when requested.
- Not to providers: payment card details or GPS lesson-tracking data. The live assistant's automatic own-account personalization is limited to the fields described in this section. Other account information is sent only when you supply it, an authorised tool needs it for your request, or it is supplied as lesson-note context. Quick Lesson Notes shares recordings, transcripts and supplied context as described above.
Technical AI usage records can include feature, provider, model, token counts, timing and success or error details. These usage records contain metadata, not the content of your conversation. Conversation storage, Finder query logs and saved searches differ by feature. See the Privacy Policy section "AI-powered features & automated processing" for the full legal-basis breakdown.