Section 01
Who we are and what this policy covers
Rocket Launch is a Los Angeles digital agency operating rocketlaunch.io. In this policy, “Rocket Launch,” “we,” “us,” and “our” refer to the agency operating this website. This policy explains how we handle personal information through our website, inquiries, Nova chat, support, workshops, applications, purchases, and related agency communications. Contact us at hello@rocketlaunch.io for privacy questions or requests.
Personal information means information that identifies, relates to, describes, or can reasonably be associated with a person or household. Business contact information can be personal information even when it is provided in a professional capacity. Information that has been properly deidentified or aggregated may be treated differently under applicable law.
This policy describes our handling of information for our own business purposes. When we build or operate a website, CRM, automation, or AI assistant for another business, that business may determine why and how its customer information is processed. Its privacy notice and our service agreement govern that relationship. Product descriptions do not mean that every advertised integration is enabled for every visitor or customer.
A workshop, application, client service, or third-party checkout may present an additional notice. Read those notices alongside this policy. A specific notice explains the particular activity; it does not remove rights available under applicable law. Visiting this website does not by itself constitute consent to every processing activity described here.
Section 02
Information we collect and where it comes from
Contact and identity information. You may provide your name, email address, telephone number, company or business name, website, role, and other contact details when requesting a project, speaking with Nova, seeking support, applying to a program, or communicating with our team.
Project and business information. Forms and conversations may include goals, budget or timing information, business stage, project descriptions, desired milestones, existing tools, website addresses, service preferences, and operational challenges. We receive the content you choose to submit, including personal information about other people that you include.
Communications and support information. We may receive chat messages, inquiry details, correspondence, support topics, impact descriptions, troubleshooting steps, responses, and records of follow-up. Chat systems also use session identifiers and credentials that allow a conversation to resume. Information supplied during a human handoff may be available to the team handling the conversation.
Workshop and application information. This can include registration or notification requests, business details, waitlist or attendance status, marketing preferences, review requests, application answers, invitation status, enrollment records, and private access or management tokens. Event-specific recording and access information will be provided through the relevant event notice.
Transaction information. When you purchase or enroll in a paid offer, we and payment providers may process your name, email, billing details, selected offer, purchase amount, payment status, transaction identifiers, subscription or enrollment status, and related correspondence. Payment credentials submitted through Stripe are handled through Stripe’s payment interface. Do not send card numbers, bank credentials, or payment security codes through general inquiry forms or chat.
Device, connection, and security information. Website hosting, security, and service providers may process IP addresses, browser and device information, request timestamps, page URLs, error reports, traffic patterns, verification results, and related connection information to deliver the site and detect abuse. Approximate location may be inferred from network information; this does not require access to your device’s precise location.
Usage and attribution information. When configured and permitted by your preferences, analytics may collect page views, referral information, interactions, outbound contact clicks, form events, performance measurements, and browser or session identifiers. Some analytics can connect earlier browsing activity to contact information you later submit. See the analytics section for the details and choices.
Sources. We receive information directly from you, automatically from your browser and service interactions, and from providers that help deliver payments, email, security, analytics, and connected services. A client or authorized colleague may also provide business contact or project information about you. We do not need sensitive personal information to respond to a typical sales inquiry.
Section 03
How and why we use information
We use information to respond to inquiries; understand your goals; prepare proposals; scope and deliver services; configure agreed integrations; manage accounts, applications, invitations, enrollment, and billing; provide support; and communicate about the work you request.
We use workshop information to send opening notifications, manage registrations and waitlists, deliver access and reminder messages, provide worksheets or replays when available, and respond to systems-review requests. A notification or waitlist request does not reserve a seat. Optional marketing preferences are separate from registration administration.
We use service and security information to operate the website and chat, preserve requested sessions, verify submissions, prevent spam and fraud, troubleshoot errors, protect private links and administrative access, investigate misuse, and maintain the reliability of our systems.
Where analytics are enabled, we use usage and attribution information to understand which pages and offers are useful, evaluate how visitors reach us, identify confusing interactions, measure inquiries and conversions, and improve website performance. We use submitted feedback and support patterns to improve services.
We may use contact information for marketing where you have requested it or another lawful basis permits it. Consent to be contacted about an inquiry is not the same as consent to unrelated marketing. We also use information for accounting, tax, contractual administration, dispute resolution, lawful requests, and protecting legal rights.
We do not treat this policy as permission to use information for an unrelated purpose without considering the notice, consent, and other requirements that apply. If we need to collect new information or use it in a materially different way, we will provide an appropriate notice and obtain consent where required.
Section 04
Nova, AI processing, and human conversations
Nova is our website’s AI-assisted chat and lead-capture system. Messages and submitted contact details are processed through the Nova service, which uses Cloudflare infrastructure, including Workers, AI services, and database storage. Lead notifications may be delivered through Resend. Authorized team members may review inquiries and participate in a live handoff through our team workspace.
Your messages may be used to generate a response, understand your request, identify a relevant service, summarize a conversation, qualify an inquiry, and help our team follow up. AI responses can be incomplete or incorrect. Request human assistance when a response affects an important decision, and do not use chat to submit passwords, private keys, financial account details, health records, government identity documents, or confidential customer lists.
The browser may retain a chat session identifier and a resume token so you can return to a conversation. It also stores interface preferences such as sound settings and session flags for welcome messages. Clearing browser storage may prevent that browser from resuming the conversation; it does not delete server-side conversation or lead records.
If a client enables voice services, telephony may involve Telnyx and voice or chat AI processing may involve Cloudflare Workers AI. Telephone numbers, call routing information, audio, transcripts, or summaries may be processed according to the enabled service and the notices supplied for that interaction. Voice availability, recording, and integrations are configuration-dependent; using this website alone does not mean your microphone or calls are being recorded.
AI provider handling depends on the provider, service, and applicable agreement. This policy does not promise that every provider has identical retention or model-training terms. Contact us about the specific service if those terms matter to your project. Any recording or additional use that requires notice or consent must be addressed for the relevant interaction.
Section 05
Cookies, browser storage, analytics, and replay
The website uses browser storage and may use cookies or similar technologies for functionality, security, and analytics. Functional storage supports chat continuity and preferences, private workshop-management access, administrative authentication, and remembering an analytics opt-out. Some storage lasts only for the browser session; other storage remains until cleared or changed.
Google Analytics 4 is available when configured to measure acquisition, page activity, and conversions. The website’s Google integration defaults advertising storage, advertising user data, and advertising personalization to denied. Analytics storage is granted unless the site detects an analytics opt-out or Global Privacy Control signal. Direct names and email addresses are not intentionally sent to Google Analytics by our lead-identification code.
PostHog is available when configured for product analytics, page views, interactions, performance measurements, error reporting, heatmaps, and session replay. Session replay reconstructs website interactions; it is not a webcam or microphone recording. Our replay configuration masks input values and elements marked as containing private chat or form information. Masking reduces exposure but does not mean every piece of information displayed anywhere on a page is necessarily excluded.
If you submit a form or chat lead and analytics are enabled, PostHog may receive your email address, name, company, and lead source to associate the inquiry with browsing activity. Browser and session identifiers may also be sent with the inquiry to Nova. This means analytics may become linked to an identifiable lead rather than remaining anonymous.
Our analytics code avoids capture on designated private enrollment routes and removes invitation parameters from captured URL properties. These protections apply to the specified integrations; they are not a guarantee that infrastructure logs or every external provider omit all request information. Do not put confidential information into ordinary URLs.
Use the analytics control below to save an opt-out in this browser. The page will reload to apply it. The opt-out applies to our optional analytics capture and lead identification; it does not disable service-essential storage, security checks, payment processing, or records needed to answer your inquiry. Google’s script may still load with analytics storage denied and may send consent-mode signals.
Your choice is browser- and device-specific. Clearing browser storage can remove the saved preference, and another browser needs its own choice. Browser settings may also let you delete cookies, block storage, or restrict third-party content; doing so can affect chat, private links, checkout, or other functionality. An opt-out does not erase information already collected. You can request deletion separately.
Our analytics code recognizes the Global Privacy Control signal as an opt-out. A saved preference cannot override that signal. Other browser signals, including older Do Not Track settings, may not be interpreted in the same way. Where prior consent is legally required for nonessential technologies, an applicable consent mechanism is required in addition to this policy; publishing a notice is not itself consent.
Your analytics choice
Save an opt-out for this browser. This reloads the page and leaves essential service and security processing available.
Section 06
Providers, recipients, and disclosures
We disclose information as needed to providers and authorized people who help perform the purposes described here. The information a recipient receives depends on its function. Access to a full inquiry is not necessary for every provider, and the fact that a provider is listed does not mean it receives every category of information.
Website and content infrastructure: Vercel hosts the website; Cloudflare supports network security, Turnstile verification, Nova, and workshop or enrollment infrastructure; Sanity supports website editorial content. These services may process request, operational, or content information relevant to their function.
Communications and customer operations: Resend delivers service and lead-notification emails. Inquiries may be delivered to our business inboxes and reviewed by authorized staff or collaborators. Nova and our connected team workspace support conversations and handoffs. If you email us directly, your email provider and ours also process the message.
Payments: Stripe processes payments and provides transaction, billing, and payment-status information needed to administer the selected offer. Stripe’s own privacy notice explains its processing, including processing it performs for its own payment, fraud-prevention, and regulatory purposes.
Analytics: Google and PostHog receive the information described in the analytics section when their integrations are configured. Voice and telephone services: Telnyx and Cloudflare Workers AI may process relevant information when those services are enabled. Scheduling, streaming, calendar, or other client integrations may introduce additional recipients that are identified in the relevant workflow or service agreement.
Professional and legal recipients: We may disclose relevant information to accountants, legal advisers, insurers, auditors, or authorities when reasonably necessary for their work, a legal obligation, investigating fraud or abuse, resolving a dispute, or protecting people and rights. We may also disclose information at your direction or with your consent.
Business transitions: If the business or a relevant part of it undergoes a merger, acquisition, financing, reorganization, or asset transfer, information may be disclosed for evaluating or completing that transaction, subject to applicable requirements. This provision does not authorize an unrelated use that would otherwise require additional notice or consent.
Providers may act on our instructions for some activities and as independent controllers or businesses for others. Their notices and agreements explain their own practices. Publicly posted content, external links, and third-party services require additional care, as explained below.
Section 07
Workshops, marketing, and communication choices
Workshop registration, notification requests, waitlists, and systems-review forms collect the details needed for the requested activity. Optional marketing consent is collected separately. Where a private management link is provided, you can use it to change the marketing preference or cancel a signup. Treat that link as confidential because it can provide access to your registration information.
You can ask us to stop optional marketing at hello@rocketlaunch.io, use an unsubscribe option in a marketing message where provided, or update the relevant workshop preference. Allow the request to be processed; a message already queued or sent may still arrive. We may retain a limited suppression record to avoid contacting you again.
Service communications are different from promotional communications. We may still send messages needed to respond to your request, deliver an active service, manage payment or enrollment, provide security information, or comply with an obligation. Cancelling a registration or opting out of marketing does not automatically erase transaction or administration records.
Event recording arrangements, attendance visibility, live questions, and replay availability depend on the event. Read the event-specific notice before participating. Avoid sharing another person’s confidential information in questions or discussions. Use a private channel if your question includes sensitive business or customer information.
Section 08
Payments, enrollment, and private access
Checkout and enrollment workflows use the selected offer, contact information, payment-provider identifiers, payment status, and administrative records to process the purchase and manage access. Payment authorization and refunds are governed by the applicable offer and terms; a privacy request does not itself cancel a purchase or subscription.
Invitations, registration-management links, and enrollment tokens can function as access credentials. Do not forward them or post them publicly. We may store token hashes or related identifiers, authenticate administrative sessions, limit repeated requests, and log status changes to protect the workflow.
If you report a payment or access problem, provide an email address, offer name, approximate date, and transaction reference where available. Do not send a full card number or login credential. We may need to match your request to the payment or enrollment record before changing access or disclosing information.
Section 09
Information handled for client businesses
When a client uses a website, CRM, automation, or AI service that we help deliver, its own visitors and customers may provide information to that client. The client ordinarily determines the business purposes and appropriate notices for that information. Our processing responsibilities depend on the service agreement and any applicable data-processing terms.
If your information was collected by another business using Rocket Launch technology, contact that business first to exercise your rights. We can help identify the appropriate route when possible, but may need the client’s instructions before accessing, exporting, correcting, or deleting its records.
Clients should provide only information they are authorized to use and share, configure access appropriately, give required notices, obtain necessary consent, and avoid putting unnecessary sensitive information into connected systems. We do not treat access needed to deliver a client service as general permission to market to the client’s customers.
Section 10
Retention, deletion, and backups
We retain information according to its purpose, the service relationship, operational needs, and applicable obligations. There is no single retention period for every category. Relevant factors include whether an inquiry is active, whether a service or account remains open, whether a workshop or follow-up is ongoing, and whether a billing record or dispute must be preserved.
Inquiry and support records may remain available for follow-up and continuity. Workshop and application records may be retained for administration and requested communications. Billing and contractual records may need longer retention for accounting, tax, legal, or dispute purposes. Security logs, analytics, email delivery records, and provider-held data may follow different schedules.
When responding to a deletion request, we consider what can be removed and what must be retained for a lawful reason. Deletion from active systems may not immediately remove copies in backups, previously delivered emails, or systems controlled independently by another provider. Retained copies remain subject to the applicable restrictions and restoration practices.
Clearing local browser storage, cancelling a registration, closing chat, or unsubscribing does not automatically delete server records. To request deletion or ask about retention for a particular record, email hello@rocketlaunch.io and identify the relevant interaction without sending unnecessary sensitive information.
Section 11
Security and your responsibilities
Our implemented safeguards include security verification for submissions, restricted administrative access, private access tokens, authenticated workflows, rate limits, and privacy masking in designated analytics surfaces. Safeguards vary by service and provider. We do not claim that every system has the same controls or that any online service is immune from unauthorized access.
Protect your email account, private links, account credentials, and devices. Send secrets only through a channel agreed for that purpose. If you suspect a private link or account has been exposed, contact us promptly with the affected service and a description of the issue; do not include the exposed secret in an ordinary message.
We investigate reported privacy and security concerns and address notification obligations when applicable. This policy does not represent a certification, an independent security audit, or a guarantee of a particular security standard.
Section 12
International processing and legal grounds
Rocket Launch operates in the United States. Information may be processed in the United States or other countries where relevant providers operate. The laws and government-access rules in those places may differ from those where you live. Provider selection or a website visit does not guarantee storage solely in your country.
Where European, UK, or other laws require a legal basis, the appropriate basis depends on the activity: steps you request before a contract and performance of a contract; legitimate interests in responding to business inquiries, supporting services, preventing abuse, and improving operations, balanced against your rights; compliance with legal obligations; or consent where required for marketing, nonessential technologies, or other activities.
Where transfer safeguards are required, the applicable arrangements must be determined for the actual provider and service, which may include contractual safeguards or a valid adequacy framework. Contact us to ask about safeguards for a particular service. We do not assert that one transfer mechanism applies to every provider or every interaction.
You may withdraw consent for processing that relies on consent without affecting processing that occurred lawfully before withdrawal. Other lawful grounds may still support limited processing, such as retaining a payment record. Depending on your location, you may object to processing based on legitimate interests or request additional information about that assessment.
Section 13
Your privacy requests and choices
Depending on your location and the laws that apply, you may have rights to know or access the personal information held about you; obtain a copy in a usable format; correct inaccurate information; request deletion; restrict certain processing; object to processing; withdraw consent; or opt out of specified uses. These rights have conditions and exceptions and do not apply identically to every activity.
Email hello@rocketlaunch.io with the subject “Privacy request.” Tell us the right or change you are requesting, the email address or contact detail used in the interaction, and whether the request concerns chat, an inquiry, support, a workshop, enrollment, a purchase, or a client-operated service. You do not need to provide a government identity document in your initial request.
We may ask for proportionate information to verify identity, locate the records, or confirm authorization before releasing information or making a change. Where possible, we use information already associated with the interaction. An authorized agent may need to show permission, and we may need to confirm that permission with you.
We will assess and respond within the time required by applicable law, including any permitted extension and required explanation. If a request cannot be fulfilled in full, we will explain the applicable reason where required. Exceptions can include security, another person’s rights, legal retention requirements, and information held on a client’s behalf.
You may contact us to challenge a response or request an appeal where available under applicable law. You may also complain to the appropriate privacy regulator or supervisory authority. Exercising a privacy right should not result in unlawful discrimination, although a requested restriction or deletion may make a particular service impossible to provide.
Section 14
California and other U.S. state disclosures
California and other U.S. state privacy laws may provide additional rights where their scope and business thresholds apply. This section explains how the categories in this policy relate to those rights; it does not claim that every state privacy statute applies to Rocket Launch.
The information described above can fall into categories including identifiers; contact and customer-record information; commercial and transaction information; internet or electronic-network activity; approximate location derived from network information; professional or business information; communications; and inferences such as a stated service interest or inquiry summary. Audio information applies only where an enabled voice or recording service actually processes it. Collection depends on the interaction, not every category for every person.
The sources, purposes, and recipient categories are described in the collection, purposes, and providers sections. Those disclosures also explain the practices relevant to a request about information collected or disclosed during the preceding 12 months, to the extent records are available and the applicable law requires that period.
Where applicable, California rights can include knowing categories and specific pieces of information; deletion; correction; opting out of a sale or sharing for cross-context behavioral advertising; limiting certain uses of sensitive personal information; and nondiscrimination. Other state laws may provide comparable rights, rights concerning targeted advertising or certain profiling, and a right to appeal.
The website code does not implement a direct sale of visitor information or an advertising audience upload. However, legal definitions of “sale,” “sharing,” and “targeted advertising” can include arrangements beyond a payment for data. Provider settings, contractual terms, and actual use matter. Do not interpret an analytics disclosure as a guarantee that every downstream arrangement falls outside those definitions.
To opt out of optional website analytics, use the control in this policy or a recognized Global Privacy Control signal. To request an opt-out relating to sale, sharing, targeted advertising, or a limitation on sensitive information where applicable, email hello@rocketlaunch.io with “Privacy opt-out” and identify the relevant interaction. We will evaluate the request under the law that applies. Do not send sensitive information just to submit an opt-out.
We do not request sensitive information for an ordinary inquiry. If you voluntarily include sensitive content in a message, it may still be processed to handle the message, protect the service, or meet a legal obligation. A provider processing a payment or security request may handle information subject to its own responsibilities. Ask us before sending regulated or highly sensitive records.
Section 15
Public content, external services, and children
If you submit a review or story for publication, the details approved for display may become public. Public content can be copied, indexed, or retained by others. Do not include another person’s private information without authorization. Contact us to ask about correcting or removing content under our control; removal does not guarantee deletion from independent archives or copies.
Our website may link to external websites, calendars, streaming platforms, social networks, payment interfaces, or client sites. When you follow a link or use a third-party service, that service may collect information under its own notice. We do not control every practice of an external service, even when it is linked from our website.
Our website and business services are intended for adults and business users, not children under 13. Do not submit a child’s personal information through general forms or chat. If you believe a child has provided personal information to us, contact hello@rocketlaunch.io so we can investigate and take appropriate action under applicable law.
Section 16
Changes to this policy and contacting us
Effective date and last updated: October 11, 2026. We may update this policy as our services, providers, practices, or legal requirements change. The date on this page identifies the current version. For material changes, we will provide additional notice or obtain consent when required by applicable law.
Contact Rocket Launch at hello@rocketlaunch.io for privacy questions, access or deletion requests, corrections, marketing preferences, or concerns about a particular service. Include enough context to locate the interaction, but avoid sending passwords, card information, or other unnecessary sensitive data. If you require a different communication method or an accessible copy of this policy, request one through that email address.
Provider privacy information
These notices explain the providers’ own practices. A provider’s notice does not replace our responsibilities for information we control.