LOOKOUT

LOOKOUT mobile privacy notice

Effective November 12, 2026 (version 1.2.60 onward).

Clear View, Inc., doing business as LOOKOUT, provides the LOOKOUT mobile app. Our registered address is 195 Saint Paul St APT 8, Brookline, MA 02446-7162, United States. Contact info@lookout.team about this notice or your data.

This notice covers the mobile app and its connected services. Our website's separate privacy notice covers website, shopping and marketing services.

Browsing without an account

You can use public chart features and recorded examples without signing in. Online charts, AIS vessel information, weather and notices make network requests to LOOKOUT services and data providers. These requests can include the map region you view, your IP address, request time and device/app information needed to serve or secure the connection. Coverage and data availability vary by source.

Location, camera and photos

With your permission, LOOKOUT uses precise or approximate phone location to show your position, course and nearby information, and help position hazard reports. You can deny location access and browse the chart manually. Reported coordinates can differ from your phone's current position because you adjusted the marker, used a recent location or submitted a report while offline.

Camera and photo-library access are optional. You choose whether to take or select an image for a report, or use Developer camera/recording features. Images may be resized, compressed and made available in different delivery sizes. Location and motion data can also accompany enabled recordings.

You can change permissions in your phone's settings. If you explicitly start a GPS journey, supported background recording can continue when you lock the phone or switch apps, until you pause or finish. GPS journey history is stored locally; background capability does not by itself upload your location history.

Accounts and boat access

The app currently supports guest use and sign-in to existing LOOKOUT accounts; it does not offer public self-service account registration. We use Google/Firebase Authentication to process identity and sign-in information. This can include your account identifier, email or Apple private-relay address, display name, sign-in provider, security/device information and a phone number if you use SMS multi-factor authentication. Google and Apple also process sign-in under their own policies.

Your account identity is shared with the existing LOOKOUT/Journey Log service. Signing in does not grant access to someone else's boat, fleet, journeys or private backups. Boat access is assigned separately. Supported account linking associates another sign-in method with your existing account rather than intentionally creating a second set of boat permissions.

Hazard reports and attribution

A hazard report can include its category, reported position, observation and submission times, location quality, a report/installation identifier, your chosen attribution name and an optional photo. These details are used to display reports and operate the reporting service. Reports and selected attribution can be shared with other LOOKOUT users; photo viewing follows the report service's access rules. Avoid submitting sensitive personal information or images of people without appropriate permission.

Reports are also used for internal operational alerts, including in LOOKOUT's Slack workspace. Those alerts can include the position, attribution and a copy of the attached photo. Expiry on the active map does not automatically delete the stored report, original attachment, internal alert or copies already shared.

Supported offline flows keep a pending report on your phone and retry when connectivity returns, with its original observation time and position. Pending report age limits apply. Closing or force-stopping the app can interrupt delivery until it is reopened; a queued report is not a confirmed submission.

Recordings and private cloud backups

Enabled Developer features can save video, location, motion/orientation, heading, timing and detection metadata locally. Imported video can include audio. On-device detection runs locally unless its resulting metadata is included in a backup. GPS journey history and video backups are separate features.

When private cloud backup is enabled, video and accompanying metadata are sent to LOOKOUT cloud storage under your account/workspace permissions and applicable network/data settings. Installation identifiers, transfer checksums, timestamps and quota/connection information help manage enrollment, transfers and restoration. Signing out does not delete local files, exported files or committed cloud backups. Exporting or sharing a file sends it to the destination you choose.

Boat Live

Boat Live uses assigned account permissions or a supported onboard connection to receive video and optional boat position/instrument data from a compatible LOOKOUT system. Boat telemetry and phone GPS are distinct sources. Network, discovery and connection information are used to establish and maintain playback. Online services use secure connections; a local onboard connection may use HTTP/WebSocket on the boat's network. Do not assume that every local network hop is encrypted.

Personal boat models

Your boats in Profile stores your boat details, selected photos and cached 3D models on your phone. Choosing Generate sends your selected reference image and any description you provide to LOOKOUT Model Studio under your signed-in account. Generation is currently available to authorized LOOKOUT team accounts. Model Studio uses OpenAI to process that input and produce a boat model. Images may be resized and combined before upload. Avoid including people or sensitive details in reference images.

Uploaded reference images remain private in Model Studio and expire after seven days. OpenAI processes submitted content under its applicable API data terms, which can include separate provider retention. Generated model files have shareable download links. Account permissions protect access to your jobs and private reference images. Saved models can be selected again under the same account, and downloaded models can be cached for offline preview and chart use. Removing a local boat profile does not automatically delete its server-side job or generated model. Contact us for removal requests.

Purposes and service providers

We process app information to provide the features you use, authenticate users, enforce boat/private-data permissions, deliver reports and backups, prevent abuse, diagnose failures and provide support. The app does not request an advertising identifier or enable advertising tracking. This statement does not describe unrelated activity on third-party websites you open.

We use Google/Firebase/Google Cloud for authentication, hosting and storage, infrastructure services including AWS where applicable, and Slack for operational alerts. Chart, AIS, weather and official-data providers can receive network/region requests when their layers are used. Their own services and policies apply to information they process independently. We do not give a chart or weather provider your private cloud recording merely because you view its layer.

Depending on the activity and applicable law, processing supports providing a requested service, permission/consent-based device features, service security and operation, or compliance with legal obligations. Information may be processed outside your country, including by our US company and international cloud providers. Applicable provider data-processing terms and legal transfer safeguards govern those services.

Optional usage analytics and crash reports

In version 1.2.60 onward, Privacy & diagnostics in Settings offers separate Usage analytics and Crash reports switches. Both are off until you enable them. Neither is required to use the app, sign in, report a hazard or access your boats.

With usage analytics enabled, Google Analytics for Firebase processes app opens, sessions, screens and selected actions such as starting Live, selecting a demo, recording a journey and successfully submitting a hazard. This includes app version/platform, installation identifiers and general device/session information. Google can derive approximate regional information from network requests. If you are signed in, we use your LOOKOUT/Firebase account identifier, not your email, to measure usage across your signed-in devices. These events do not contain your precise GPS coordinates, photos, boat names or hazard-report text. We do not use this feature for advertising or automatically link it to a Shopify customer.

With crash reports enabled, Firebase Crashlytics processes crash/error reports, stack traces, app version, installation identifiers and device/operating-system information to help diagnose failures. We do not explicitly attach your account identifier, photos, routes or report text to crash reports. JavaScript error messages are replaced with fixed diagnostic descriptions. Native crash reports can contain technical error context from the operating system and native SDKs.

You can switch either option off at any time. This stops future sending and clears pending data for that option; it does not remove data already received by Google. Crash reports saved before a new opt-in are discarded rather than sent. Optional measurement is consent-based, and Google processes it as our service provider. To request deletion of previously submitted information, contact us as below.

Retention and your choices

We retain account and service information as needed to operate your account, provide requested services, address support/security issues and comply with applicable obligations. Current committed private backups do not have automatic journey-age deletion. Report visibility/attachment-access limits and temporary upload cleanup are distinct from deletion of retained records or Slack copies. Local files stay under your phone's storage controls; exported/shared copies can remain with their recipients.

For access, correction, export, account deletion or removal of a report/photo, email info@lookout.team, preferably from the address associated with your account. Guest users can also contact us and provide a report identifier where available. Do not send a password or authentication code. We may verify your identity and clarify which data you mean. Shared boat/company data, others' reports, legally required records and copies controlled by recipients may need different treatment from your personal mobile data. This contact process does not claim that an automatic in-app account-deletion feature exists.

You can manage phone permissions and available app settings, change report attribution, stop a GPS journey, turn off supported backups, remove local files using available controls and sign out. Where applicable, you can withdraw consent, object to or restrict processing, and contact your data-protection authority. Withdrawing a permission does not by itself remove information already submitted.

We may update this notice when app features or data handling change and will update its effective date. For support and privacy requests, contact info@lookout.team or visit LOOKOUT contact.