Launch handles the information needed for your workspace. We do not sell your data, use it for advertising, or operate a server that collects your extension data.
1. About this policy
Supporting Launch is an internal Chrome extension provided for our team’s daily work. It replaces the new-tab page with a customizable workspace. This policy covers the extension and this informational website.
Launch handles information to provide the features you choose, including Google-connected widgets, weather, notes, team photos, and a user-requested QuickBooks session reset. It has no advertising, analytics, or telemetry service and does not send extension data to a backend operated by the Launch team.
2. Google connection and team photos
Connecting Google is optional. When you connect, Launch uses Chrome’s identity service to obtain authorization tokens and make authenticated requests directly to Google. Tokens are not saved in extension settings or repair logs.
- Profile: your basic Google profile, including your name and account identifier, is used for the greeting and to separate cached data between accounts.
- Drive folders: starred folder names, identifiers, links, and modification information are used to display shortcuts.
- Calendar: upcoming event information is retrieved from your primary calendar. Launch displays and caches titles, times, locations, and meeting/event links.
- Tasks: task titles, identifiers, due dates, status, and notes are retrieved to show your task list.
- Team photos: selecting Enable photos requests additional Drive read-only access. Although Google describes this as access to view and download Drive files, Launch uses it to list and display images from the configured team photo folder. Image data is held in the open tab; Google and Chrome may apply normal HTTP caching.
- Photo uploads: selecting Upload requests additional full Drive authorization. The selected photo, caption, and uploader information are sent to the configured shared Drive folder. They are available to people who have access to that folder under its Google Drive sharing permissions.
These features depend on your Google account and folder permissions. Launch does not read Gmail messages. Notes, work links, and focus tools can be used without connecting Google.
3. Storage on your device and Chrome sync
Device storage: Launch saves Google connection status, basic account identity, cached folder/calendar/task information, optional photo metadata, weather data and coordinates, timer state, sound volume, and recent repair progress/results in local browser storage.
Notes: notes are saved on this device in the extension’s local storage, with a local backup. They are not intentionally uploaded or synced by this version. Download saves a text file through Chrome’s normal download handling. Older synced notes are migrated to local storage and removed from the old synced settings after the local copy is written; another device may retain an older copy until it updates.
Synced preferences: widget choices, layout, theme, custom work-link titles and URLs, and weather settings use Chrome extension sync storage. Whether those preferences sync to other devices depends on your Chrome account and sync settings.
Ambient sounds are generated in the tab. They do not use your microphone, stream audio from a service, or send listening activity to a server. Audio starts only when you choose to play it.
4. Weather and location
Weather uses Open-Meteo and its geocoding service. New installations start with Boston, Massachusetts as a default city, sending Boston’s fixed coordinates to the weather API. This default does not identify your current location.
Searching for a city sends the search text to Open-Meteo’s geocoding service. Choosing browser-location mode asks the browser for your location and uses those coordinates for weather requests. Launch does not request device location unless you choose that mode. You can select another city or turn off weather.
Google and the weather providers receive the network information needed to respond, such as your IP address and request timing. See Google’s privacy policy and Open-Meteo’s terms and privacy information.
5. QuickBooks session repair
Fix QuickBooks runs only when you request it and confirm the displayed impact. It requests optional browser permissions for browsing-data removal, cookies, and Intuit/QuickBooks websites.
During repair, Launch examines open Intuit/QuickBooks tab addresses and target cookie information to identify the session data to clear. It closes affected tabs, removes Intuit/QuickBooks cookies, clears specified site storage and cache for known or discovered Intuit/QuickBooks origins and selected Intuit asset origins, and opens a sign-in page.
This can sign you out of multiple Intuit products or companies because cookie domains may be shared. If you allow the extension in incognito, cookie removal may also reach that cookie store; a complete incognito reset is not guaranteed.
A separate option, unchecked by default, clears HTTP cache for all ordinary websites for that run. It does not expand cookie or site-storage deletion to unrelated websites. Repair does not clear browsing history, saved passwords, or downloads, and it does not read QuickBooks financial records.
Launch does not maintain a browsing-history log or monitor browsing in the background. Repair logs contain step descriptions, counts, and diagnostic information, not cookie values or full browsing URLs. Cookie values are not sent to a server. You can clear the saved repair log in the repair Details section.
7. Your choices and data retention
- Disconnect Google: clears saved Google account caches and visible meeting information and attempts to revoke the Google token. If revocation fails, Launch directs you to remove its access in your Google Account settings.
- Hide a widget: stops its normal refresh/display; it is not a data-deletion command. Account caches otherwise remain until refreshed, disconnected, or the extension is removed.
- Notes and preferences: remain after disconnecting Google so you can continue using the workspace. Export notes before removing the extension or clearing its data. Chrome-synced preferences remain subject to Chrome’s sync and retention behavior.
- Shared photos: remain in Google Drive until a person with the necessary folder permissions deletes them. Removing the extension does not delete uploaded photos or files you downloaded.
- Permissions: you can manage extension permissions in Chrome and remove Google authorization through your Google Account’s third-party connections settings.
For help removing data or managing shared-folder access, contact the internal administrator who provided Launch.
8. This website
This website provides product information and this privacy policy. Its page code does not set cookies, collect form submissions, or include analytics, advertising, tracking pixels, embedded media, or external font services. Screenshots use fictional sample workspace data.
The website is prepared for hosting on Cloudflare Pages. When served through Cloudflare, Cloudflare processes connection information, such as IP addresses and request details, to deliver and secure the site. This is separate from the extension’s data handling. See Cloudflare’s privacy policy for its practices.
9. Contact and updates
For support, privacy questions, or data requests, contact your internal IT team or the administrator who provided Supporting Launch. Authorized users can also use the support contact on the private Chrome Web Store listing.
We will update this page when the product’s data handling changes and revise the date above. Material changes will also be described through the product or our internal communication channels as appropriate.
Supporting Launch is an internal team tool. It is not affiliated with or endorsed by Google, Intuit, or the other services linked from the workspace. Product names and trademarks belong to their respective owners.