Privacy Policy

Overview

Launxe is a startup-launch workspace. This policy explains the information Launxe processes when you create an account, analyze a public startup website, generate assets, share launch links, or connect Google Analytics.

Information you provide

• Account details such as your email address, name, authentication provider, and session information.
• Startup details such as a website URL, product summary, audience, positioning, launch goals, budget range, and progress.
• Content you create or edit, including generated launch copy, campaign details, social profile URLs, ratings, comments, outreach actions and results, and task status.
• Startup profile images or logos you upload and the brand color you select.

Public website analysis and generated content

When you submit a URL, Launxe retrieves public pages and may inspect page text, metadata, links, social links, analytics identifiers, robots information, and sitemaps. Private network addresses, unsafe redirects, unsupported content, oversized responses, and other unsafe targets are blocked.

Relevant public page content and your approved startup profile may be sent to OpenAI to improve analysis and draft marketing content. Launxe also has deterministic fallbacks when AI processing is unavailable. Review generated content before publishing it; Launxe does not intentionally invent customer claims, metrics, or product capabilities.

Outreach Agent and optional assistant

Launxe stores your outreach strategy, public research sources, prepared drafts, opportunity decisions, feedback, and outcomes with your startup. Relevant startup details, saved messaging, and outreach history may be sent to OpenAI to research public business opportunities, prepare drafts, or answer your questions. These records remain private to your startup workspace. Research can run when you request it or return; scheduled research requires an available scheduler and your opt-in. You can pause the agent.

The agent does not send emails, publish community posts, or submit directory listings for you. You review sources and choose whether to act. Public research and inferred relevance may be incomplete or incorrect; they are not verified buying intent.

Usage measurement on Launxe

Launxe uses Google Analytics to measure visits and navigation on this website. This is separate from the Analytics accounts founders connect for their startups. Our page-view events remove query strings, fragments, private startup identifiers, and share tokens from page addresses. Funnel events include allowlisted action names, launch steps, opportunity types, counts, outcomes, and elapsed time. They exclude startup identifiers, prospect details, email addresses, message text, and private feedback. Google Analytics may use cookies and process device, browser, and approximate geographic information.

Private tester feedback and payments

For Live Test Rooms we store your display name, US-adult declaration, devices, use case, relationship disclosure, consent version, task drafts, submitted versions, optional screenshots, quality review, appeal, and payment status. Stripe receives identity, tax, bank and card details through its hosted pages. Launxe stores provider identifiers and accounting records, not raw card numbers, bank credentials or identity documents.

The beta operator may review submissions and screenshots. Founders receive the exact accepted, funded feedback versions and a summary linked to those originals. They do not receive tester email addresses, bank details, payout identifiers, rejected drafts or private appeal records. Relevant task text and submitted feedback may be sent to OpenAI for a tool-free quality recommendation and an evidence-linked summary. AI cannot accept work or move money. Do not include private or sensitive information in submissions.

Optional screenshots use a private bucket, are decoded and re-encoded to remove metadata, and are served through short-lived links after an access check. Unresolved work, appeals and unpaid earnings can prevent deletion until they are resolved. Financial counterparties, consent and decision evidence, ledger entries and provider reconciliation records survive permitted startup deletion. Their retention is reviewed for applicable accounting and dispute requirements before the live beta. Request account access or deletion using the contact below.

Public prospect contact information

Launxe may store a deliberately published business email or official contact page with its public source, excerpt and verification date. It does not guess email patterns or verify inbox deliverability. Public listing does not establish consent to receive a message. Contact failure, competitor, already-contacted and do-not-contact feedback creates private owner-level suppressions. A contact is checked again after seven days before opening a new draft. Unused contact details expire after 90 days; minimal suppression identifiers remain to avoid repeating excluded recommendations.

Google user data: access and use

Google sign-in and connecting Google Analytics are separate, optional features. Google sign-in uses Supabase authentication to establish your account, using the basic account information Google supplies, such as your email address and name.

For a startup’s Analytics connection, Launxe requests only https://www.googleapis.com/auth/analytics.readonly. It reads the identifiers and display names of GA4 properties available to your Google account, and the timezone of the property you select. It retrieves aggregate reports for that property: users, new users, sessions, page views, engagement, key events, and breakdowns by date, traffic channel, source/medium, page path, country, device category, and campaign.

Launxe uses this information to display your startup’s traffic and launch results, compare reporting periods, and provide rule-based guidance within your private Analytics dashboard. It updates saved reports when you open or return to the dashboard or request a refresh. This permission cannot change your Google Analytics account, properties, events, or configuration. Launxe does not request Gmail, contacts, or Google Drive access.

Who receives Google user data

Launxe shares, transfers, or discloses Google user data to the following service providers as necessary to operate the features you choose:

• Google: receives authorization requests and access or refresh tokens to grant or renew permission, list accessible GA4 properties, and return the selected property’s reports. If available, your Launxe account email is sent to Google as a sign-in hint when you start connecting Analytics.
• Vercel: hosts Launxe’s website and server functions. Those functions process the Google authorization response, use tokens to request reports, and deliver the results to your authenticated browser. Tokens are decrypted in server memory when needed to call Google.
• Supabase: provides authentication and database storage. It processes Google sign-in account information and stores encrypted Analytics credentials, accessible property identifiers and names, selected-property details, and cached reports for your startup.

Your connected Analytics reports are available in your authenticated workspace. Launxe does not publish them on your public startup listing or share them with other founders. It does not sell Google user data, transfer it to data brokers, or use it for advertising, ad targeting, or advertising profiles.

Launxe does not automatically send connected Google Analytics tokens, property lists, or reports to OpenAI, the Outreach Agent’s research service, or Launxe’s own website-usage Analytics property. The optional chat sends the text you choose to type and saved startup context to OpenAI; avoid pasting information you do not want processed there. Connected Google Analytics data is not used by Launxe to train AI models.

Launxe’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google data storage and retention

Analytics access and refresh tokens are encrypted with AES-256-GCM before being stored in Supabase. The application keeps them, the available-property list, and selected-property details while the connection exists. It keeps a saved overview and up to 32 cached report variants per connection, replacing older cache entries as new reports are saved. There is no fixed time-based expiry for these saved records. They may remain until you reconnect, change the selected property, disconnect, delete the startup, or request account deletion. Reconnecting or changing properties clears the old reports; disconnecting removes both credentials and reports.

Deletion from the active application database does not necessarily immediately remove copies in service-provider backups or infrastructure logs. Their retention follows the provider’s configured backup and log lifecycle; Launxe does not promise a fixed deletion period for those copies.

Revoke access or delete Google data

Open Integrations, select the startup, and disconnect Google Analytics to delete that startup’s saved Google credentials, property details, and reports from Launxe. Other startups’ connections stay separate. Deleting a startup from the dashboard also deletes its connection and reports.

To revoke Google access for Launxe entirely, open your Google Account’s third-party connections, select Launxe, and remove its access. Revocation stops future authorized access and may affect every startup using that Google account. Revoking in Google alone does not delete reports already saved in Launxe; also disconnect in Launxe or request deletion as described below.

Campaign and usage analytics

Launxe creates tracked share and campaign links. It may record a link visit, an outbound click, source and campaign labels, and related timestamps so you can understand which launch activity sent interest to your startup. Launxe also records operational events such as sign-in, analysis, task completion, asset generation, and integration status.

Cookies, sessions, and logs

Launxe and Supabase use cookies or equivalent browser storage needed for authentication, security, and session continuity. Server and hosting logs may contain request timing, route, status, browser information, truncated error details, and security events. Secrets and OAuth tokens should not be written to application logs.

We keep chat-hint cooldowns and last-visit timestamps in this browser’s storage to avoid repeated prompts and recognize returning workspace sessions. Notifications and their read state are stored with your account in Supabase. Clearing browser storage resets local hints; it does not delete saved startup data or notifications.

Service providers and third parties

Launxe relies on Supabase for authentication, database, and startup-image storage; OpenAI for optional AI analysis, chat, content generation, and outreach research; Vercel for web hosting and server functions; and Google for sign-in and Analytics. The Google user data shared with these providers is specifically described above. External social networks, directories, CapCut, and Read Aloud are separate services you may choose to open; Launxe’s integrations do not send them your connected Google Analytics reports or credentials. Each provider has its own terms and privacy policy.

Public information

A startup you explicitly publish may appear in the public Launxe directory and on a public launch page with its name, description, category, logo or initials, website link, rating, and launch date. Public comments include the commenter’s display name, text, and date. Founders receive private notifications about new ratings and comments on their listings. Public share pages may route visitors to your startup and count visits and outbound clicks. Do not submit information you do not have permission to make public.

Retention, deletion, and choices

You can delete a startup from the dashboard. This permanently deletes its analysis, tasks, generated assets, social setup, campaigns, analytics connections and snapshots, events, saved journey and outreach records, notifications, public launch record, ratings, comments, and stored startup image through the application’s deletion flow. To request account-level access or deletion, email ellisnelsonwalker@gmail.com. Deleting the last startup using a website releases its domain reservation. Some security logs or provider backups may remain for a limited period where necessary for security, legal compliance, or service recovery.

Security and children

Launxe uses encrypted transport, server-only secrets, database row-level security, encrypted Google tokens, private-network crawl protections, rate limits, and access checks. No internet service can guarantee absolute security. Launxe is not directed to children under 13, and it does not knowingly collect their personal information.

Changes and contact

This policy may change as Launxe’s features or legal obligations change. Material updates will receive a new date on this page. For privacy questions or requests, email ellisnelsonwalker@gmail.com.