Privacy Policy
Last updated: 5 November 2026
This Privacy Policy describes how SkillQuest (“we”, “us”, “our”) collects, uses, and shares personal information when you use the SkillQuest websites and related services (the “Services”), including the SkillQuest product.
SkillQuest is operated from the United Kingdom. This notice is written with UK data protection law (including the UK GDPR and the Data Protection Act 2018) in mind. It is provided for transparency and does not constitute legal advice.
Who we are
The data controller for personal information processed through the Services is the organisation operating SkillQuest under the name SkillQuest (contact: use the channels published on our website, for example the contact or waitlist forms).
Information we collect
We may collect the following categories of information, depending on how you use the Services:
- Account and profile data — for example name, email address, organisation details, and authentication identifiers when you create or use an account.
- Pseudonymous visitor and identity graph data — for example
sqid, linked email from account, waitlist, or confirm flows, PostHog distinct ids and traits (hashed where applicable), UTM/referrer session attributes, and consent decision history (category, domain, version, timestamp, and source). - Waitlist and marketing requests — information you submit when joining a waitlist or requesting updates (such as email, role, or organisation type).
- Scheduling and sales chat bookings — when you book a call via our scheduling provider (for example Cal.com), we may receive your name, email address, booking times, and related booking metadata so we can run the meeting and follow up about SkillQuest. That provider processes the booking on our behalf; we may also store a copy of the booking webhook for operations, identity resolution, and analytics.
- Content you provide — text, files, or other materials you upload or generate while using product features (for example learning content, assignments, or chat messages where those features exist).
- Files you import through connectors — files you choose from Google Drive, Microsoft OneDrive or SharePoint, or LottieFiles, plus the connection details needed to reach them (see “Connected services” below).
- Generated learning media — for example AI-produced speech audio and caption files created from your authored topic content, stored in organisation-scoped storage tied to your content lifecycle.
- Technical and usage data — such as IP address, device and browser type, approximate location derived from IP, pages viewed, timestamps, and diagnostic logs needed to operate and secure the Services.
- Support communications — information you send when you contact us or share feedback.
We do not intentionally collect special categories of personal data (such as health data) unless a feature clearly requires it and we tell you separately.
Identity resolution and analytics
When analytics is enabled and you consent, we may: assign a browser continuity cookie (sq_sid); mint or restore a pseudonymous sqid on our servers; link an email address from account, waitlist, or confirm flows to that person record; and configure PostHog so we alias any prior anonymous analytics id to sqid and then identify on sqid. Your email is stored as a person property, not as the primary analytics user id. With analytics consent we may also use session replay (pseudonymous recordings of on-screen interactions via PostHog) to understand product usage and fix issues; replay does not run before you opt in and stops when you revoke analytics consent. Revoking analytics consent stops further capture and clears client identity keys tied to analytics.
How we use your information
We use personal information to:
- provide, maintain, and improve the Services;
- authenticate users, enforce security, and prevent abuse;
- schedule and run sales or onboarding chats you request, and follow up about those conversations;
- communicate with you about the product, your account, or support requests;
- comply with legal obligations and respond to lawful requests;
- analyse usage in aggregated or pseudonymised form to understand product performance (where permitted and configured).
We treat three kinds of email differently:
- Service messages are about your account, billing, security or access, for example a new invoice or a removal from an organization. We send them whatever your notification settings, because you need them to use the service.
- Notifications are about your learning and your work, for example progress, comments, things shared with you, or requests waiting on you. They are part of the service you use. You choose which of them reach your email in notification settings, and each one has a one-click unsubscribe link. Your choices are recorded as preferences, not as marketing consent.
- Offers and news are marketing, for example offers or reminders about items left in your shop basket. We only email them if you switch on "Offers and news" in notification settings, which records your consent. You can withdraw it at any time with the unsubscribe link in every such email, or in settings. We treat push notifications the same way as email.
These are separate from waitlist and newsletter marketing, which you sign up to on our website, and from the CMP marketing cookie category. Booking a sales chat is treated as a transactional / pre-contract interaction for that meeting; it is not, by itself, consent to unrelated marketing emails.
We process personal information where we have a lawful basis under UK GDPR, typically: performance of a contract with you, legitimate interests (such as securing our systems and improving the product, balanced against your rights), or consent where we rely on it (for example certain optional communications or non-essential cookies, where applicable).
AI-assisted content processing
Some product features send learning content you author (such as topic card text) and, for voice features, speech audio or spoken text to third-party AI service providers that process it on our instructions. Outputs may include chat replies, images/video, synthetic speech, timed captions, or other generated media used inside the learning experience.
- Processing is subject to appropriate contractual safeguards (including DPAs where required) with those providers.
- Material AI sub-processors (customer-visible inventory): fal.ai (and model providers invoked via fal, such as OpenRouter), Fish Audio (hosted text-to-speech, Discovery library reference ids, and instant voice-clone reference audio/transcripts sent at synthesis time), ElevenLabs (voice library and ElevenLabs-bound TTS; batch often via fal), LiveKit, LemonSlice, Baseten (Whisper speech-to-text and selected 3D scene workers only — not Fish TTS), Langfuse Cloud EU (when observability is enabled), and TypeSafe (when structured decision features are enabled). Hosting, database, and email providers are listed under “How we share information.”
- Batch AI processing (chat assistance, content generation, topic video, and related features) is primarily routed through fal.ai. We send prompts and content needed to produce the requested output; we do not store full prompt text in our primary usage database — we record lineage references (template keys and observability trace ids) for metering and operations. Where configured, we instruct fal not to retain request/response payloads on its platform (
X-Fal-Store-IO); generated media may still exist on CDN storage subject to lifecycle settings. - Batch and live speech-to-text use Baseten Whisper (audio is sent to our Baseten deployment via SkillQuest servers; API keys are not exposed to browsers).
- Batch narration and live avatar / Ask voice responses (TTS) are character-driven: default Fish Audio (hosted) or ElevenLabs, plus LiveKit and LemonSlice for the realtime session. What we send to Fish Audio may include: (a) text to synthesize; (b) for Discovery voices, a Fish
reference_id; (c) for organisation clones, reference audio and transcript on each synthesis (samples are stored by SkillQuest and processed by Fish at generation time — instant/inline, not Fish private model slots); (d) optional direction tags (Drama 3). There is no Fish GPU warm on Baseten. - Operational observability (Langfuse Cloud EU, when enabled) may store prompts and model inputs/outputs to debug and improve reliability; access is limited to authorized staff.
- We do not use your authored learning content to train public foundation models on your behalf. Whether a vendor may train on Customer Content under our account depends on SkillQuest’s agreements with that vendor (enterprise / DPA terms). Fish Audio free-tier or provider terms may allow use of requests to improve models unless a paid / zero-data-retention arrangement applies; SkillQuest pursues commercial terms at launch, with Enterprise ZDR as an optional upgrade. These opt-outs are not exposed as end-user or per-model toggles in the product; enterprise customers should contact us for DPA / security pack details.
- Generated media (for example narration audio and caption files) is stored in organisation-scoped storage and retained according to your content lifecycle (publish, republish, deletion) rather than indefinitely for unrelated purposes.
- Where supported by the provider API, we configure speech synthesis requests to minimise provider-side request logging (for example
enable_logging=falseon ElevenLabs batch and live TTS paths). Fish Audio logging and retention follow Fish’s DPA / terms of service (details on request). Enterprise zero-retention guarantees may depend on your organisation’s agreements with us and the provider.
Further technical detail about narration and voice processing is available to customers on request.
Connected services
Your organisation can connect third-party services to SkillQuest. Connecting is always optional and is started by a user or organisation admin.
File sources: Google Drive, Microsoft OneDrive and SharePoint
- What we access. Only the files you pick in the provider’s own file picker, plus your basic account identity (name and email) for the connection. For Google Drive we use the
drive.filescope, which limits access to files you choose or that SkillQuest creates. For Microsoft we use Microsoft Graph delegated permissions (Files.Read;Sites.Read.Allonly if your organisation’s admin approves the organisation-wide SharePoint connector). We do not browse, index or copy files you did not choose. - How we use it. Only to provide the feature you asked for: importing the files you chose and creating learning content from them. We send file content to the AI providers described under “AI-assisted content processing” (or your organisation’s own providers, see below) for that generation.
- What we do not do. We do not use data from Google or Microsoft APIs to develop, improve or train generalised AI or machine-learning models. We do not sell it, use it for advertising, or let people read it except with your permission, for security or abuse investigations, or where the law requires.
- Google Limited Use. SkillQuest’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- Microsoft. We access Microsoft Graph data under the same rules, and in line with the Microsoft APIs Terms of Use.
Bring your own AI provider
Your organisation can connect its own AI provider accounts (for example Anthropic, OpenAI, OpenRouter, fal, ElevenLabs or Fish Audio). When it does, we send the prompts and content needed for each request to that provider under your organisation’s own account and agreement with it. Your organisation chooses those providers and is responsible for its terms with them.
If your organisation’s provider fails (for example an expired key, quota or outage), we continue the request on SkillQuest’s own providers and credits so your work is not interrupted. This fallback is on by default. Admins can turn it off for any connector; when it is off, requests that fail on your provider stop instead of moving to SkillQuest’s providers.
Data flow, retention and deletion
- You pick files in Google Drive, OneDrive, SharePoint or LottieFiles.
- We copy them into your organisation’s SkillQuest storage, where they become content assets.
- When you generate learning content from them, we send the needed content to the AI providers above.
- Imported files stay in your organisation’s storage as content assets until you delete them. Deleting an asset in SkillQuest removes our copy. Deleting or editing the original in Google Drive or Microsoft does not change our copy, and deleting our copy does not touch the original.
- Connection credentials (OAuth tokens and API keys) are encrypted at rest and never shown in full after you save them. When you or an admin disconnects a connector, we delete its stored credentials straight away and stop all further access. Content already imported stays until you delete it.
- You can also revoke SkillQuest’s access from your Google Account permissions or your Microsoft account or organisation’s app settings; the connection then stops working, and you can remove it in SkillQuest.
Cookies and similar technologies
We use cookies and similar technologies as described in our Cookie Policy. Essential cookies may be set without consent where they are strictly necessary to provide a service you have requested. Optional categories cover preferences (including theme, cursor style, and topic learner settings such as captions and playback preferences — see the Cookie Policy for the current key list), analytics, and marketing.
Before a sqid exists, browser CMP storage (sq_consent / sq:consent:v1) is authoritative for your choices. After sqid exists and we successfully sync, our server consent state is authoritative for site CMP categories unless your browser copy is newer and is reconciled on the next sync.
When you view this notice on our website, you can reopen optional cookie categories using Manage cookie settings above (and via footer links or your account menu where we surface them).
How we share information
We may share personal information with:
- Services your organisation connects — your organisation’s own AI providers and file sources, as described under “Connected services”;
- Service providers who process data on our instructions (for example hosting, email delivery, database, error monitoring, scheduling providers such as Cal.com for sales chats, or PostHog for analytics when enabled, including EU hosting where configured), subject to appropriate contractual safeguards;
- professional advisers where required (for example lawyers or accountants);
- authorities when we believe disclosure is required by law or to protect rights, safety, or security.
We do not sell your personal information in the conventional sense of “selling” data for money.
International transfers
Where we use providers outside the UK, we implement appropriate safeguards (such as the UK International Data Transfer Agreement or UK Addendum to the EU Standard Contractual Clauses) where required by law.
Retention
We retain personal information only as long as needed for the purposes described in this policy, unless a longer period is required by law. Retention periods depend on the type of data and whether you maintain an active account. Imported connector files and connection credentials follow the rules under “Connected services”. Scheduling webhook records are kept only as long as needed for follow-up, operations, and identity resolution tied to that booking, then deleted or minimised. We keep an append-only consent decision audit trail and a materialised consent state per person; waitlist signup marketing fields may be cached alongside the ledger. On account deletion we redact or remove consent row personal data where appropriate.
Your rights
Depending on your situation, you may have the right to:
- access, correct, or delete your personal information;
- restrict or object to certain processing;
- withdraw consent where processing is based on consent (including via the CMP, waitlist unsubscribe, SaaS notification settings, or account deletion requests);
- lodge a complaint with the UK Information Commissioner’s Office (ICO) or another supervisory authority.
To exercise these rights, contact us using the details published on our website. Some requests can also be fulfilled from in-product account settings where available.
Security
We implement technical and organisational measures designed to protect personal information. No method of transmission or storage is completely secure; we encourage strong passwords and safe handling of your credentials.
Children
The Services are not directed at children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children.
Changes
We may update this Privacy Policy from time to time. We will post the updated version and revise the “Last updated” date. Material changes may be communicated by email or in-product notice where appropriate, and may trigger a consent re-prompt when the CMP or policy version changes.
Contact
For privacy-related questions, contact us via the contact options shown on our website.