Privacy

Privacy Policy

This policy explains how LaunchBOS handles information across the public website and authenticated cloud Workspace, including account data, business records, legacy browser data, downloads, and visitor choices.

Last updated: 3 October 2026

On this page

Overview

This policy explains the current information practices of the LaunchBOS website and authenticated cloud Workspace. It applies to public resources, downloadable tools, and business records a user chooses to save in Workspace.

The public website can be browsed without creating an account. Access to Workspace requires an account.

Information collected

Workspace account email, authentication session, business ownership membership, and supported cloud business-profile fields are processed through Supabase. Authentication emails may be sent for confirmation and password recovery. The site does not currently provide a newsletter signup or contact-submission form.

Current business profiles, customers, catalogue items, inventory movements, quotations, invoices, payments, and receipts are stored in the authenticated cloud workspace. When enabled, returns and refunds, follow-ups, expenses, and income are also cloud records, while reports and activity are derived from cloud records. A module marked Soon is not currently available through the interface.

Separate Version 1 records may remain in that browser until the user clears them through browser controls. The legacy-data preview reads summary counts locally and cannot upload, import, modify, or delete those records.

The service used to deliver the website may process standard technical request information needed to load and protect the site, such as an IP address, browser type, requested page, and request time. The exact handling of infrastructure logs depends on the hosting service in use.

Analytics, cookies, and browser storage

When site analytics is enabled, LaunchBOS uses Google Analytics to understand page visits and navigation and Microsoft Clarity to understand website interaction and user-experience patterns. These services may use cookies or similar browser technologies and receive technical information such as the page viewed, browser or device information, and interaction data according to their own privacy practices.

Microsoft Clarity may provide aggregated heatmaps and session-replay style information. LaunchBOS should not intentionally place passwords, payment credentials, government identifiers, or customer business records into analytics events, and visitors should avoid entering sensitive information into unverified fields or channels.

Workspace authentication uses secure session cookies, while separate Version 1 business records may remain in browser local storage for local summary review. Enabled Workspace modules use the authenticated cloud business; Version 1 browser records are not synchronized automatically.

Visitors can use browser privacy controls, blocking tools, and applicable third-party opt-out controls to limit analytics technologies. Blocking analytics should not be required to use the core public website or authenticated Workspace.

Workspace data controls and legacy browser data

The current cloud Settings interface does not provide export, backup and restore, bulk clearing, or full account-deletion controls. It should not be treated as a backup service, and users should keep appropriate copies of important business documents outside LaunchBOS.

The legacy-data page can preview summary counts from separate Version 1 browser records only. It cannot export, restore, import, clear, or change those records. Clearing browser storage affects local browser data and does not delete active cloud Workspace records.

Template downloads

When a visitor chooses a template format, the requested file is downloaded directly to their device. The website does not currently require an email address or account before a download.

The visitor’s browser, operating system, network, or download manager may keep its own record of the download.

External links and third-party services

LaunchBOS may use third-party services including Supabase for authenticated Workspace services, Google Analytics for website analytics, Microsoft Clarity for experience analytics, and Vercel or another hosting provider to deliver the application. Those services operate under their own terms and privacy practices.

Guides may also direct visitors to official authorities, software providers, or other external websites for current information. Those services operate under their own terms and privacy policies.

A link does not mean that LaunchBOS controls the external service or its data practices.

Retention and security

Workspace account identity, business ownership membership, and supported cloud profile fields remain stored because the current interface has no full account-deletion control. Version 1 business records remain in browser storage until the user clears them or browser/device behavior removes them.

No online service can be guaranteed completely secure. Visitors should use trusted devices and networks and should avoid sharing sensitive information through an unverified channel.

Visitor choices

Visitors can use browser controls to manage cache, history, downloads, site permissions, and local site data. The current legacy-data page is preview-only and does not export, import, restore, clear, or change records. Browser controls for local site data do not delete active cloud Workspace records. External services should be reviewed separately before information is submitted to them.

  • Do not submit passwords, payment credentials, government identifiers, or customer records through an unverified channel.
  • Check the address of an external website before relying on it.
  • Use browser and device settings to manage local download history and stored files.
  • Protect documents and template files downloaded to your device, and delete copies you no longer need.

Children and policy changes

The website is designed as a business resource for entrepreneurs and is not directed at children.

This policy may be updated when the website’s information practices change. Material changes should be reflected in the published policy and accompanied by a maintained update date.