Privacy Policy

This Privacy Policy explains how LaunchFar ("we", "us") collects, uses, and protects your personal data when you join our beta waitlist or use launchfar.com. We handle your data in line with the EU General Data Protection Regulation (GDPR).

Who is responsible

The data controller is Jam with AI, operated by Shirin Khosravi Jam and Shantanu Ladhwe, Ulmenallee, 14050 Berlin, Germany. For any privacy question, or to exercise a right, contact contact@jamwithai.com.

What we collect

• Waitlist email. When you join the waitlist we store the email address you provide, via our authentication provider Clerk.
• Account data. If you are invited and sign in, Clerk stores your name, email, and authentication identifiers on our behalf.
• What you tell the product. Your onboarding profile (role, skills, target), your roadmap, and anything you type into the career mentor, course lessons, exercises, or community features.
• AI conversations and long-term memory. We store your chat history and derive a summary profile and discrete "facts" from it (for example a stated goal or a preference) so the mentor can remember you between sessions. This is described below.
• Learning activity. Course enrolment, lesson progress, exercise submissions, assessment answers, and practice results.
• Community content. Posts, comments, and any images you upload to community features. Images are stored in Google Cloud Storage and screened by OpenAI’s moderation before they appear.
• Course video playback. While a course video plays, our video provider Mux collects playback-quality and viewing telemetry with a player identifier so streaming works. This is part of delivering the video, not optional analytics, so it is not covered by the analytics choice below.
• Usage analytics. Optional, and only if you accept them: analytics about page views and product usage (via Vercel Analytics and PostHog). If you accept while signed in, those events are linked to your account identifier and basic profile flags (role, onboarding status, account tier). Session recording and autocapture are off, and PostHog stores its identifier in your browser’s local storage rather than in a cookie.
• Error diagnostics. Optional, and covered by the same choice: when something breaks, we send the error and the page it happened on to Sentry so we can fix it. Feedback you send through the in-app form also goes to Sentry — that one works even if you declined analytics, because delivering a message you chose to send us is your request, not measurement of you.
• Technical data. Standard server logs (IP address, browser, timestamps) used for security and abuse prevention.

We collect no payment data. The beta is free, checkout is switched off, and no card or billing details are requested, processed, or stored.

AI conversations, memory, and moderation

What you write to the mentor, to a lesson assistant, or to the course personalisation chat is sent to OpenAI, which generates the reply on our behalf as a processor. The same applies to the text we turn into embeddings for search and to the moderation check that screens messages — and community images — for harmful content. Under OpenAI’s API terms, content sent this way is not used to train their models.

To make the mentor useful across sessions we keep more than the raw transcript: a structured profile of you and individual facts extracted from your conversations, both of which are rewritten automatically as you talk to us. Your conversations and the prompts and replies around them are also sent to Opik, our LLM-observability provider, so we can debug and improve quality during the beta.

Because this is a personalised, long-term profile built partly from free text, please do not enter special-category data (such as health, political, or religious information), credentials, other people’s personal data, or your employer’s confidential information. You can ask us to delete stored memory at any time.

How we use your data

• To operate the beta and contact you when an invitation is available.
• To personalise the mentor, your roadmap, and course recommendations.
• To moderate content, keep the service secure, and prevent abuse.
• To debug, measure, and improve an unfinished product.
• To comply with legal obligations.

We do not sell your data, we do not use it for targeted advertising, and we do not make automated decisions with legal effect about you.

Legal bases (GDPR Art. 6)

• Consent — for joining the waitlist, for beta updates we send, and for optional analytics and error diagnostics.
• Contract — to provide the beta once you have an account.
• Legitimate interests — security, abuse prevention, moderation, and improving the product.

Processors and third parties

We share data only with processors who help us run the service: Clerk (authentication and waitlist), Vercel (frontend hosting and analytics), Google Cloud (backend hosting, storage, logging, and monitoring), Neon (database), OpenAI (mentor replies, embeddings, and moderation of text and images), Opik (LLM tracing), Mux (course video delivery and playback, including the playback telemetry described above), Cloudflare (bot protection on sign-in and sign-up, which sees your IP address and browser signals), Tavily (web search for the content feed — it receives search queries derived from profile interests, never your name or account), PostHog (product analytics), and Sentry (error diagnostics and in-app feedback). PostHog receives nothing unless you accept optional analytics; the same goes for Sentry’s error reports, except feedback you deliberately send us.

Some processors handle data outside the EEA; where they do, transfers are covered by Standard Contractual Clauses, the EU-US Data Privacy Framework, or an equivalent safeguard.

Data retention

We keep waitlist emails until you ask us to remove them or the beta closes. Account data, conversations, memory, and learning activity are kept while your account is active and are deleted on request. A minimal residue survives deletion: a hashed identifier that stops a deleted identity from silently re-registering, security audit logs, and anonymised usage-metering entries — none of it linked to your name. Because this is a test environment, we may also reset or delete beta data ourselves as the product changes, so do not treat LaunchFar as storage for anything you need to keep.

Your rights

You have the right to access, rectify, erase, restrict, and port your data, to object to processing, and to withdraw consent at any time. You can delete your account and its data from your account settings, and you may lodge a complaint with a supervisory authority — for us, the Berlin Commissioner for Data Protection and Freedom of Information. To exercise any right, email contact@jamwithai.com.

Cookies

We use strictly necessary cookies for authentication (set by Clerk when you sign in). Our optional analytics set no cookies — PostHog keeps its identifier in your browser’s local storage instead, which is why it is covered by the choice below rather than by the cookie banner alone. Your consent choice itself is also stored in your browser, and accepted analytics are sent through a first-party proxy on our own domain. We do not use advertising or tracking cookies.

Changes to this policy

We may update this policy as the experiment evolves. We will revise the "last updated" date above and, where appropriate, notify you.