Privacy notice

Better Launcher is a venture-development service operated as a sole proprietorship under the Better Launcher name. “We,” “us” and “our” refer to that operator. Contact support@betterlauncher.com for privacy questions and requests. This notice covers our website, accounts, startup workspaces, support and exports.

We decide how account, security and operational information is used. Workspace users also decide what information about interviewees, customers, team members and other people they upload and who can access it. Their responsibilities and any separate notices they provide continue to apply. Accepting our Terms does not give a user permission to disclose someone else’s information.

Account information: your email address, account identifiers, authentication and session records, and any profile name, photo, bio or links you provide. Supabase handles password authentication. Sign-up also records the accepted Terms version, document hash and server-recorded acceptance time.

Workspace information: startup descriptions, branding and contact details; membership roles and invitation email addresses; team and advisor profiles; customer segments and personas; interviewee names, demographics, protocol answers, quotes and attribution permissions; validation records and attachments; business models, market information, financial assumptions, actuals and pitch content. We receive this from you or other authorized workspace members. Uploaded files may contain personal information and embedded metadata.

Collaboration information: the workspace and section you have open, session identifiers, recent presence, editing reservations and timestamps used to coordinate access and changes.

Cohort program information: enrollment and staff roles, designated contact names, roles and email addresses, choices about peer visibility, announcements, and activity descriptions, times, locations and links. These are supplied by cohort staff or startup administrators. Designated contact addresses are entered separately from login emails.

Cohort engagement: activity sharing starts automatically for team members with editing access while their startup belongs to an active cohort. We record coarse daily active-time totals and the most recent activity time for your account in that workspace. We do not record keystroke contents, pointer locations or screen recordings. Hidden tabs and idle time are excluded from the estimate. Authorized cohort staff see team-level totals for the reported UTC date range, not individual activity histories. You can turn off your own sharing in cohort Settings; this removes your recorded engagement totals for that startup and keeps a disabled preference so rejoining does not turn it back on. Totals otherwise remain until sharing is disabled or the workspace or account is removed. This measure does not capture work outside Better Launcher, and past activity is not reconstructed.

Technical information: hosting and authentication services may record IP addresses, browser or device information, request URLs, timestamps, authentication events and errors. Our application also records some diagnostic errors. These records support operation, security and troubleshooting and can be personal information even without a name.

Support information: the messages and attachments you send us. Do not send passwords, authentication tokens or unnecessary sensitive information.

We use information to create and authenticate accounts, recover access, save and display your work, manage invitations and permissions, coordinate editing, generate requested exports and pitches, respond to support, diagnose failures, prevent abuse and meet legal obligations. Account and authentication information is necessary to provide an account. Optional profile and workspace fields can be left blank where the interface permits.

Where a law requires a legal basis, account and requested service processing relies on performing our agreement with you; necessary security, troubleshooting and service administration rely on our legitimate interests, subject to your rights and a balancing assessment; legally required processing relies on the relevant obligation. When consent is required for an optional use, we will request it separately and explain withdrawal. Accepting the Terms is not blanket consent to every use of personal information.

The current service has no third-party marketing analytics, advertising pixels or session-replay tools. We do not sell personal information or share it for cross-context behavioral advertising. We do not use the service to make automated decisions that produce legal or similarly significant effects about individuals.

Workspace members can see information permitted by their role, including collaborators’ names or initials and current sections. Access-management views can show profile photos, roles and membership or invitation information. Administrators can manage access. Removing access does not retrieve exports, screenshots or copies already made.

Cohort enrollment shares the startup name and enrollment status with cohort staff. The join form initially selects viewer access for the named current staff, startup directory visibility, and visibility of the joining account’s display name. Administrators can review and turn off those choices before confirming enrollment, and change them later in cohort Settings. Staff viewer access includes private workspace content, interviews, financial projections and report downloads; it does not allow editing. New staff require a separate approval. Peer directory visibility shares only the startup name, logo, saved directory description and links, and names whose visibility is enabled; it does not grant peers access to the workspace. Each team member controls their own name visibility. Existing enrollment choices are not changed automatically.

Cohort staff and enrolled startup members can read program announcements and activities without granting access to private startup workspaces. Designated cohort contacts are available to cohort staff for program communications; peers see contact details only when peer sharing and any applicable startup directory listing are enabled. Your own startup team can see its designated contacts. Managers can prepare email drafts using selected contact addresses in BCC. Opening a draft passes those addresses and the draft text to the email application you choose; you decide whether to send it. Announcements and activity entries do not send email automatically. We store private per-account read markers to identify new or revised announcements and activities; cohort staff do not receive individual read reports. Choosing a calendar provider passes the selected activity’s title, times, description, location and meeting link to that provider for you to review and save. Calendar file downloads stay on your device until you import or share them.

Service providers: Supabase provides authentication, database and file storage. Vercel hosts the deployed application and processes requests and operational logs. Providers and their infrastructure subprocessors handle information needed to deliver these services. Authentication emails use the delivery infrastructure configured for Supabase Auth. Authorized operator access may also be necessary for support, security and administration.

At your direction: exports are downloaded to your device. Including content in a pitch prepares it for your use; it does not by itself publish it to everyone. You control subsequent distribution. Attribution permission in an interview record is a workspace setting, not a substitute for obtaining appropriate permission from the interviewee.

Legal and safety needs: information may be disclosed where required by law or reasonably necessary to address fraud, abuse, threats to safety or legal claims. If the service transfers to another operator through a business transaction, relevant information may transfer subject to applicable law, confidentiality protections and notice of material changes.

To retrieve alternative logos, the server may request an image from the website or image address entered in the workspace. A fallback request to Google’s favicon service includes the website domain. Those destinations receive the requested address and server connection information. Retrieved alternative logos may be cached in Supabase storage.

Remote images and demo content can cause requests to external websites or media providers. YouTube demo links use its privacy-enhanced embed address; Vimeo links use its player. Loading or playing external content may disclose your IP address and browser information and allow the provider to use its own cookies or similar technologies. Privacy-enhanced embedding does not make a video anonymous. External sites opened from links apply their own privacy practices.

Authentication cookies maintain and refresh your signed-in session. Browser session storage remembers workspace views and navigation choices. A browser session identifier helps coordinate editing. These features support the service rather than advertising. Blocking cookies may prevent sign-in; clearing browser storage may sign you out or reset preferences. External content providers may use additional technologies as described above.

Before introducing optional tracking that requires consent, we will explain its purpose and provide the choices required by applicable law. A browser Do Not Track signal does not disable essential authentication or security processing.

Optional device recovery: when you turn it on, supported editors keep an unsaved text/settings copy in this browser’s local storage, scoped to your signed-in account, startup and editor. It is not a backup of uploaded files. A copy is offered for up to seven days; expired copies are removed on your next authenticated visit. Successful saves or cancellations in an open supported editor remove its copy. Signing out or turning off recovery clears device recovery copies. Use this option only on a private device. Clearing browser data also removes these copies.

As of this notice’s date, we are not using user data for academic research. Section 8 of the Terms describes possible future research into entrepreneurial processes, decisions and outcomes. It does not establish that a study has begun, that ethics approval has been obtained, or that accepting the Terms replaces required research consent.

Before research use begins, we will provide a study-specific explanation of its purpose, information involved, responsible researchers or institutions, applicable legal basis, recipients, retention and participant choices. Required ethics review and additional consent must be completed before the relevant use. Possible data include usage and activity histories, timestamps, venture-development content, customer discovery and validation records, revisions and decisions. We will not silently expand permissions for previously collected information.

Information linked to an account or internal research identifier remains personal information when a person can reasonably be identified. Removing names alone is not enough: distinctive venture details, quotes and combinations of facts can identify a person or reveal confidential business information. Safeguards must address those risks through appropriate access limits, removal or generalization of identifiers, suppression and, where appropriate, paraphrasing.

Section 8 permits appropriately de-identified research derivatives and academic sharing only subject to applicable law, this notice and study requirements. Collaborators must have appropriate confidentiality, security and restrictions on re-identification. Publications must not identify users or disclose recognizable confidential venture information without appropriate authorization or another lawful basis.

Truly anonymous derivatives may remain after account closure when permitted, because they cannot reasonably be linked back to an individual. Pseudonymous or otherwise identifiable records remain subject to applicable rights and retention limits. Study-specific notices will explain any limits on withdrawal after anonymization or publication.

The current service does not send user content to AI providers, and we are not using it to train AI models. Section 9 of the Terms anticipates possible future AI features; accepting the Terms does not activate those features or authorize undisclosed model training.

Before enabling an AI feature, we will explain what data is sent, to which provider, for what purpose, any human review, retention and processing locations, whether the provider can use it to train models, and how you can choose whether to use the feature. We will obtain consent or other authorization where required. Sending content to a model to generate an answer and using it to train a model are different uses and will be disclosed separately. We will not introduce training on private workspace content through a silent policy change.

Workspace content is retained to make your saved work available until it is removed or the service is closed, subject to applicable requirements. Permanent deletion removes selected records and the dependent information described in the confirmation. File cleanup can require retries; deletion is not a promise that every storage copy disappears instantly.

Operational logs, support records, authentication records and Terms acceptance records may be retained for the time necessary for security, troubleshooting, legal obligations or disputes. Backups follow the relevant provider’s retention cycle and may outlast removal from the live service. Duration depends on the record’s purpose, provider configuration and applicable obligations; we do not promise one deletion deadline for every copy. Retained information should be limited to the purpose that requires it.

Contact support to request account deletion or deletion beyond the available in-app controls. Deleting an account is not necessarily the same as deleting an entire shared startup: other authorized members’ work and legitimate records may need to remain. We will explain applicable limits. Copies held by export recipients are outside our direct control.

We use authentication, startup membership checks, database access policies and private storage buckets to restrict access. Some files use temporary signed links; treat those links as confidential while valid. These measures reduce risk but do not guarantee absolute security. Avoid unnecessary sensitive personal information, passwords, payment-card details or regulated data the service is not designed to handle. If a breach requires notification, we will provide it as required by applicable law.

Providers may process information in countries other than your own. Supabase hosts core project data in the selected project region, while support, operational services and subprocessors can involve other countries. Vercel also uses distributed infrastructure. We do not promise all processing stays in one country. Where a transfer requires safeguards, the relevant provider agreements and an appropriate lawful transfer mechanism must apply. Contact support for information about the hosting configuration and safeguards relevant to your data.

You can edit your profile and workspace content, manage access where your role permits, remove supported items and download available exports. Email support@betterlauncher.com to request access, correction, deletion or a copy of personal information. You can also contact us if another workspace user uploaded information about you. We may need proportionate identity verification and information identifying the workspace; do not send identity documents unless requested.

Depending on where you live and the law that applies, you may have rights to restriction, portability, objection to certain processing, withdrawal of consent, and an appeal or complaint to a privacy regulator. We will respond within the applicable legal period and explain refusals or limitations. Withdrawing consent does not undo lawful processing already completed. We will not discriminate against you for exercising applicable privacy rights. An authorized agent may need to provide evidence of their authority.

Right to object: where applicable, you can object to processing based on legitimate interests by emailing support@betterlauncher.com. You can use the same address to withdraw consent to an optional use. We will explain any lawful grounds for continuing processing and how to challenge our response.

Workspace administrators may also need to respond to requests concerning personal information they collected. Access controls and our Terms do not remove an interviewee’s or another individual’s applicable privacy rights.

The service is intended for adults aged 18 and older, consistent with the Terms. We do not knowingly offer accounts to children. Contact support if a child created an account or personal information about a child was uploaded so we can assess and address it.

We will update this notice when practices change and display the revision date. For material changes we will provide appropriate notice, such as an in-app message or email, and obtain required additional consent before a new use begins. Continued use does not replace legally required consent or authorize retroactive expansion of data uses.