Privacy Policy

Who We Are and What This Policy Covers

Laaunch ("Laaunch," "we," "our," or "us"), a division of Morgan Ventures, Inc., lets domain owners publish focused pages on domains they already own, capture leads from those pages, and see how the pages perform. This Policy explains what we collect through www.laaunch.com, the Laaunch dashboard, and the pages published with Laaunch, how we use it, and the choices you have.

Two roles matter here. For our own website and for Laaunch accounts, we decide how data is used. For pages that our customers publish on their own domains, the page owner decides why visits and leads are collected, and we process that information on their behalf. If your question is about a page you visited or a form you submitted on someone else's domain, the page owner is usually the right first contact, and we will help route requests we receive.

Information We Collect

Accounts. When you create an account we store your email address and name, and then the information you add while using Laaunch: your pages and their content, the domains you connect, images you upload (such as favicons and backgrounds), notification email addresses, webhook URLs, and settings. If you buy a paid plan, our payment provider handles your payment details and we keep your plan, billing status, and the customer reference it gives us. We do not store full payment card numbers.

Signing in. We do not use passwords for accounts. When you sign in with your email address, we send you a one-time code and link, and we store the email address, the time, your IP address, and a scrambled (hashed) copy of the code so it can be checked once. If you choose to stay signed in on a device, we store a scrambled copy of that device's sign-in key along with its IP address and browser details. We keep a record of each sign-in, including the time, the method you used, your IP address, and an approximate location, for security and troubleshooting.

Signing in with Google or GitHub. If you choose to sign in through Google or GitHub, that provider asks for your permission and then tells us your email address, whether it has verified that address, and your name. From Google we request only basic sign-in permissions (your name, email address, and profile). From GitHub we request permission to read your profile and email addresses, and we use your primary email address only when GitHub has verified it. We use this information only to create your Laaunch account, fill in your name, and sign you in. We never receive your Google or GitHub password; we do not request access to your contacts, files, messages, calendar, or code repositories; we do not store the provider's access token once sign-in is complete; and we do not keep the other profile details a provider may return.

Visits. When someone visits our website or a page published with Laaunch, we record technical information about the visit: the page, the time, the IP address, an approximate location (such as country, region, city, and postal area, derived from the IP address by our network provider and never precise GPS location), the device type and browser, the referring website, and any campaign tags in the link (UTM parameters). We also keep short-lived security records of requests, which can include browser headers, to detect bots and abuse. Page owners see visit counts, trends, and summaries in their dashboard; they do not see the IP addresses of visitors who do not submit a form.

Leads. When a visitor submits a form on a For Sale or Waitlist page, we store what the visitor entered (such as a name, email address, phone number, company, title, and message, depending on the form) together with the page, the time, the IP address, approximate location, device and browser, the referring website, and the page address. We share the lead with the page owner as described below; the owner can see the details recorded with it, including its IP address and approximate location.

Email. We keep a record of the emails we send, including the recipient, subject, and content, for a short period so we can confirm delivery and troubleshoot problems. Our email provider also tells us whether a message was delivered, bounced, or marked as spam.

Cookies and Similar Technologies

On laaunch.com, we use first-party cookies to keep the site working and to keep account holders signed in: a session cookie; a device cookie if you choose to stay signed in (for up to 30 days from your last visit); a cookie that recognizes a browser that has signed in before so it is not asked to prove it is a person every time (for up to 30 days); and a cookie that limits abuse from a browser after an account is suspended. Sign-in forms use Cloudflare Turnstile, and our network provider, Cloudflare, may set its own security cookies to block automated traffic.

Pages published with Laaunch use a session cookie so their forms work and can be protected from abuse. If a page owner adds their own Google Analytics tag to a page, Google Analytics runs on that page under the owner's Google account and its own cookies and policies.

We do not currently use analytics or advertising cookies on laaunch.com, and we do not use visitors' information for advertising or to follow them across other websites.

How We Use Information

• To operate the Services: create accounts, sign you in, publish and serve your pages, connect your domains and obtain security certificates for them, store leads, and deliver the notifications and webhooks you configure;
• To show page owners how their pages are doing: visits, leads, conversion, trends, and summaries of countries, devices, and campaigns;
• To secure the Services: rate limiting, bot and abuse prevention, investigating reports, and protecting accounts (this is what IP addresses and security records are used for);
• To communicate with account holders: sign-in codes, service notices, security alerts, and delivery-failure notices;
• To process payments for paid plans;
• To fix defects and improve reliability, using aggregate or de-identified information where practical;
• To comply with law and enforce our Terms of Service.

We do not sell personal information, and we do not use leads or visit information for advertising.

How Information Is Shared

With page owners. Leads submitted on a page are shared with that page's owner in their dashboard and exports, and through the notification emails and webhooks the owner configures. Owners are responsible for the destinations they configure and for how they use the leads they receive.

Service providers. We use a small number of providers to run the Services, and they process information only to provide their services to us: our hosting provider (servers and databases in the United States); Cloudflare (network delivery, security, approximate location, Turnstile, and issuing and serving security certificates for connected domains); Amazon Web Services (storage and delivery of uploaded images); Resend (email delivery); Stripe (payments for paid plans); and Rollbar and Sentry (error monitoring, which can include technical details of the request that caused an error).

AI features. Anthropic's Claude writes the notes we show owners about their domains and about companies that ask about them. For those we send it domain names and figures about the owner's own domains. We do not send it a visitor's name, email address, or message, and it does not train on what we send.

Sign-in providers. If you sign in with Google or GitHub, that provider knows you used it to sign in to Laaunch and handles your information under its own privacy policy. We do not send your pages, leads, settings, or other Laaunch data to the provider.

Legal and safety. We may disclose information to comply with law or lawful process, to protect the rights, safety, or property of any person, or to enforce our agreements. Business transfers. If our business is sold, merged, or reorganized, information may transfer as part of that transaction under this Policy's protections.

Google User Data

Laaunch's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use the information Google provides (your name, email address, and whether Google has verified it) only to create your account and sign you in. We do not transfer it to others except as needed to provide the Services, comply with law, or as part of a business transfer described above; we do not use it for advertising; and we do not allow humans to read it except with your permission, for security purposes, or to comply with law.

Retention and Deletion

We keep account data, pages, and leads for as long as your account is open. Sign-in codes are deleted after two days. Remembered devices are forgotten when you sign out or 30 days after their last use. Short-lived security records of requests, form logs, and the record of emails we send are kept for about 30 days. Records of visits to a published page are kept while its owner's account is open so the owner can see trends over time, and records of visits to our own website and of account activity are kept for up to three years. If you ask us to delete your account, we delete or de-identify your account data, pages, and leads, except information we need to keep for legal, security, billing, or fraud-prevention reasons. Deleted information may persist briefly in backups before they roll off.

Your Rights and Choices

You may ask to access, correct, or delete your personal information, or to delete your account, by contacting us at hello@laaunch.com; we respond as applicable law requires. You can update your name and email address in your account settings. If you signed in with Google or GitHub, you can remove Laaunch's access at any time in that provider's account settings; this stops future sign-ins through it but does not delete your Laaunch account, which you can ask us to do. If you submitted a form on a page published with Laaunch, the page owner controls that lead; we will direct your request to them where required and help them fulfill it.

Security

We take reasonable technical and organizational measures to protect information. Sign-in codes, links, and remembered devices are stored only in scrambled (hashed) form and expire; sign-in forms are protected against automated abuse; dashboard access requires authentication; and visitors' IP addresses are used for security and abuse prevention and are shown to page owners only for leads submitted on their pages. No method of transmission or storage is completely secure, so please keep the email account and any sign-in provider account you use with Laaunch secure.

International Processing

We store and process information in the United States. If you use the Services from elsewhere, you understand your information will be transferred to and processed in the United States.

Children

The Services are not directed to children. If you are under 18, or the age of majority where you live, use the Services only with the consent of a parent or legal guardian.

Changes to This Policy

We may update this Policy from time to time. When we do, we will revise the "last updated" date at the top of this document. Your continued use of the Services after changes are published means you accept the revised Policy.

Contacting Us

Questions or requests about privacy? Contact us at hello@laaunch.com and we will respond as required by applicable law.