Privacy Notice
Beta. Last updated October 1, 2026.
This notice explains how LD Engage (the “Product”), the hub LaunchDarkly Professional Services uses to deliver customer engagements, collects, uses, and shares personal data. If you use the Product as part of an engagement, your organization’s agreement with LaunchDarkly also applies, and it controls if the two conflict. See the Terms of Use for more.
Who is responsible for your data
LaunchDarkly’s Professional Services team operates the Product. For any privacy question or request, contact bnorman@launchdarkly.com or your LaunchDarkly contact.
Personal data we collect
- Account data: your name, email address, and job title, the engagements you’ve been invited to and your role on each, and, if you sign in with Google, the name, profile photo, and sign-in tokens Google provides.
- Sign-in and acceptance records: the one-time codes we email you, which expire after 10 minutes, and the date, revision, and IP address from which you accepted these terms.
- Engagement content: what you and your colleagues add, such as prerequisite answers about your teams, applications, and tools, decisions, action items, comments and mentions, uploaded files and links, and the participants you list. It may include personal data about you or others.
- Activity: who added, changed, completed, or resolved something, and when. This is how the engagement’s history and timeline show who did what.
- Learning records: your knowledge check answers and results, and the badges and credentials you earn.
- Preferences and feedback: your email notification settings, your notifications, and any feedback you send, along with the page you sent it from.
- Technical data: limited logs, such as IP address, browser, and error details, kept by our hosting provider to run, troubleshoot, and secure the Product.
How and why we use it
We use personal data to deliver your engagement and tailor it to your organization, to sign you in and keep your account secure, to send the notifications you’ve asked for, and to improve the Product and our professional services. LaunchDarkly staff see delivery and learning statistics across engagements, such as the sessions each team member delivered and knowledge check results. For users in the EEA and UK, our legal bases are performance of the agreement with your organization, our legitimate interests in delivering, securing, and improving our services, and your consent where it’s required.
We email you sign-in codes, invitations, and notifications about your engagements. Notifications include a short excerpt of what happened, such as a comment that mentions you or an action item assigned to you, so they’re useful on their own. Once delivered, an email is kept by your email provider under your organization’s policies. You can turn notification emails off for any engagement from the link at the bottom of each one.
Who can see it
Everyone on an engagement, including your colleagues and the LaunchDarkly team, can see its shared content. LaunchDarkly staff can see every engagement’s full record, including private session notes. People on other engagements can’t see yours. If you share a credential, anyone with its link can see your name, the credential, and the date you earned it. That link never shows your email address or engagement details.
Service providers
We use these providers to run the Product: Vercel (hosting), Neon (database, including uploaded files), Resend (email delivery), and Google (sign-in for LaunchDarkly staff). LinkedIn receives your credential only if you choose to add it to your profile. The Product doesn’t send your content to AI providers. We don’t sell your personal data or use it for advertising.
International data transfers
LaunchDarkly and these providers are based in the United States. If you use the Product from the EEA, the UK, or elsewhere, your personal data may be transferred to and processed in the United States and other countries whose data protection laws may differ from yours. Where required, these transfers are covered by appropriate safeguards, such as Standard Contractual Clauses.
How we protect your data
The Product is served only over HTTPS. Customers sign in with one-time codes that expire quickly and stop working after a few wrong guesses. Staff sign in with their LaunchDarkly Google accounts. Access is checked on every request and scoped to the engagements you belong to, and uploaded files are stored privately and served only to engagement members and LaunchDarkly staff. No system is completely secure, and because the Product is a beta, we can’t guarantee the security of your data.
Retention
We keep engagement data for as long as the engagement runs and afterward as the record of the engagement. Archived engagements are read-only. Deleted comments are kept for LaunchDarkly staff as part of that record. If your organization’s agreement with LaunchDarkly sets different retention terms, that agreement controls. You can ask us to delete your account and personal data at any time (see below).
Your rights
Depending on where you live, you may have the right to access, correct, delete, or export your personal data, to object to or restrict certain processing, and to withdraw consent. To exercise these rights, email bnorman@launchdarkly.com. EEA and UK users may also complain to their local data protection authority.
Cookies and local storage
The Product uses only strictly necessary cookies, such as the ones that keep you signed in and protect sign-in from forgery, and a short-lived one that remembers the address a sign-in code was sent to. Your browser’s local storage keeps your theme and layout preferences and some workshop drafts on your device. We don’t use advertising or analytics cookies.
Changes to this notice
We may update this notice. If we make a material change, we’ll update the date above and ask you to accept the new version the next time you open the Product.