Skip to content

Privacy Policy

Last updated: November 9, 2026

This Privacy Policy describes what information we collect from and about you when you use the Lumo portal and its products, including Lumo Vector, Lumo Waypoint, Lumo Navigator, and Lumo Ops Manager, our messaging service (Lumo Concierge), our API and MCP access, or our website at thinklumo.com (collectively, the "Services"), how we use and protect that information, who we share it with, and your choices regarding your data.

When we refer to "Lumo," "we," "our," or "us," we mean Resilient Ops, Inc. This Privacy Policy is incorporated into and subject to our Terms of Service.

Information We Collect

Information You Provide to Us

Account, Organization, and Profile Information. When you create an account, join an organization, or activate a product, we collect information such as your name, email address, phone number where provided, organization details, invitations, memberships, roles, permissions, seat assignments, and account preferences. For Concierge, we also collect travel preferences you share, such as your home airport, preferred airlines, seat preferences, and communication preferences.

Billing and Agreement Records. We collect billing contact and address information, payment processor identifiers and payment method summaries, invoices, product activation details, purchased-seat history, usage and charges, and records of terms acceptance, including the accepting user, agreement version, time, IP address, and browser information where recorded. Stripe processes full payment card details; Lumo does not store your full card number.

Traveler and Trip Information. You or your organization may enter, import, or connect traveler names and email addresses, booking references, flight details, itineraries, organization and team assignments, traveler labels, meeting and group identifiers and names, trip names, and booking notes. We also store note revision history and editor identifiers. Vector can extract trip information from pasted text, including text from spreadsheets, emails, or itineraries. Source material may contain information beyond the fields needed for tracking; review and remove unnecessary information before submitting it.

Insider Tips and Contributions. When you contribute Waypoint insider tips or votes, we collect the contribution, contributor identity, timestamps, AI-organized versions, and voting information. Tips may be surfaced to other authorized users in your organization, including in AI answers, with contributor email attribution and vote counts. Booking notes are shared according to booking and traveler access permissions; they are not private messages to Lumo.

Notification Destinations and Integrations. When you configure alerts or connect an integration, we collect the destination address, phone number, channel, or webhook URL, relevant credentials or authorization tokens, selected settings, and related delivery or connection records.

Messages and AI Interactions. When you send messages through Lumo Concierge, Vector, or Waypoint AI features, we receive and store your messages and responses, conversation history, relevant travel or dashboard context, and supported action results. We use this information to respond to requests, maintain conversation continuity, and provide the features you use.

Content You Provide by Forwarding Emails. When you forward trip confirmation emails to trips@thinklumo.com or to your personal Lumo inbox address, we parse those emails to extract flight information. While we use only flight-related information to provide the Service, forwarded emails may contain other personal or financial data. If you prefer not to share the contents of full emails, you can register flights directly through Lumo Concierge instead.

Content from Connected Calendars. If you connect your calendar to Lumo Concierge, we receive calendar data to the extent needed to support flight tracking and travel planning.

Information You Provide Through Support

If you contact us for support or submit feedback through the Services, we collect the information you provide, including issue descriptions, supporting material, and feedback.

Information We Collect Automatically

Usage Information. We collect information about how you use the Services, including features used, message frequency, notification preferences, and usage patterns.

Device and Connection Information. We collect device type, device identifiers, IP addresses, and error or crash information to diagnose issues and maintain the Services.

Tracking Technologies. We use cookies, log files, and tracking scripts on our website to support session management, analytics, and product improvement. You can disable cookies in your browser settings, though this may affect site functionality.

Information We Receive from Third Parties

We work with businesses (such as employers, travel management companies, and airlines) that may provide us with information about you — including your name, email, phone number, and flight details — to enable flight tracking on your behalf. Third parties may only share your data with us if you have given them consent to do so.

How We Use Information We Collect

To Provide the Services. We use information to authenticate users, manage organizations and access permissions, register and track travel, display dashboards and reports, support shared booking notes and tips, analyze disruptions, provide travel planning assistance, and send alerts through the destinations and channels you or your authorized organization configure, including email, SMS, WhatsApp, Slack, and supported webhooks.

To Provide AI-Assisted Features. We process messages, relevant conversation and travel context, trip-import text, and insider tips using AI services to answer questions, analyze authorized dashboard information, extract trip records, organize tips, and carry out supported actions requested through the Services. See "Sharing with Service Providers" for the information sent to OpenAI.

To Administer Accounts, Billing, and Security. We use account, seat, usage, payment, and agreement records to administer subscriptions and invoices, manage invitations and sponsored access, enforce permissions, prevent fraud or abuse, troubleshoot errors, and meet legal obligations.

To Send Service Updates. We may contact you to inform you of changes to our Terms, Privacy Policy, or security practices.

For Research and Development. We use aggregated and anonymized information about how users interact with the Services to identify opportunities to improve our products.

For Customer Support. We use information you provide to resolve technical issues and respond to account or service questions.

With Your Consent. For any use not listed above, we will ask for your explicit consent before proceeding.

Legal Bases for Processing (EEA Users)

For users in the European Economic Area, we process personal data under the following bases:

  1. Legitimate interests — to operate and improve our Services, ensure security, and communicate with users, where those interests are not overridden by your rights.
  2. Contract performance — where processing is necessary to provide the Services you have signed up for.
  3. Consent — where we have specifically asked for and received your consent.
  4. Legal obligation — where we are required to process data to comply with applicable law.

How We Share Information We Collect

We do not sell or lease your personal information to any third party. However, we do share your information with third parties to provide our Services. We work with third-party service providers to provide website and application development, hosting, maintenance, backup, storage, infrastructure, payment processing, authentication, survey hosting, analysis and other services for us, which may require them to access or use information about you. Examples of service providers are listed below. No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

Sharing with Service Providers

We share information with third-party service providers who help us operate the Services. Our current key service providers include:

Amazon Web Services (AWS). We use AWS to host our Services, store data, and manage infrastructure. Other service providers also process information as described below.

OpenAI. We use OpenAI’s API to process messages and relevant context for Concierge and portal AI features, including Vector and Waypoint, AI-assisted trip extraction, and insider-tip organization. We use the API rather than the consumer ChatGPT service. Under OpenAI’s API data policies, API inputs and outputs are not used to train its models by default, unless the API customer explicitly opts in to data sharing. OpenAI processes the information sent in these requests and may retain it. By default, abuse-monitoring logs may contain request and response content and may be retained for up to 30 days, subject to applicable exceptions. Some API features store application data for longer, depending on the feature and configuration. See OpenAI’s API data controls.

What is sent to OpenAI. Depending on the feature, requests may include your prompt, relevant conversation history, travel preferences, traveler names and email addresses, flight and booking details, booking notes, organization or team context, meeting and group information, selected dashboard records, contributed tips, and text submitted for AI-assisted trip extraction. The information included depends on the request and the information available to that feature under its access permissions. Avoid placing payment card details, passwords, or unrelated sensitive information in messages, notes, tips, or import text. Our AI integrations do not intentionally include stored payment card information in model requests.

Stripe. We use Stripe to process payments and administer billing for individual subscriptions, organization seats, and API usage. Resilient Ops does not store your full payment card details. Stripe's privacy policy is available at stripe.com/privacy.

Google Mail. Our @thinklumo.com email addresses are hosted by Google.

Google Analytics. We use Google Analytics to track interactions with our website.

HubSpot. We use HubSpot to manage web pages, capture website usage data, and log communications.

Messaging and Connected Destinations. Delivering alerts requires sharing the message and relevant travel information with the recipient and the providers operating the selected channel or integration. For example, this may include email and SMS delivery providers, WhatsApp, Slack, or a webhook endpoint you configure. Those destinations may be controlled by your organization or another third party and have their own access, retention, and privacy practices. Connecting a destination can disclose travel information to everyone authorized to access that destination.

External Assistants and MCP Connections. If you authorize an external assistant or application to access Lumo through MCP or API credentials, the application receives the information returned by the calls made under that authorization. Its handling of that information is governed by its own terms and privacy policy. You can revoke Lumo-side credentials or authorization using the available account controls; revocation does not recall information already received by the external application.

International Data Transfers

We are based in the United States. Information handled by Lumo and its service providers may be transferred to, stored in, or processed in the United States and other countries where the relevant providers operate. Storage and processing locations depend on the service and its configuration. We do not promise that all information remains exclusively in the United States. For information about the transfer arrangements and safeguards applicable to your use of the Services, contact privacy@thinklumo.com.

Compliance with Law and Enforcement of Rights

We may disclose your information as required by law or regulation, or where we believe in good faith that disclosure is necessary to: (1) comply with any applicable law, regulation, or legal process; (2) protect and defend our rights or property, or the rights of our users or third parties; (3) detect, prevent, or address fraud, security, or technical issues; or (4) enforce our Terms of Service.

Sharing with Partners or Corporate Customers

When Services are provided through an organization, authorized organization users may access traveler and booking information, shared notes, labels, reports, and contributions according to their roles and assigned access. Organization owners and authorized managers can manage memberships, permissions, and seats. Relevant travel information and alerts may also be delivered to the destinations configured for that use. A person may have access through more than one organization, and removing access from one organization does not remove records or access held independently by another.

Merger or Acquisition

In the event of a merger, acquisition, or sale of all or part of Resilient Ops, your information may be transferred to the successor entity, subject to this Privacy Policy unless and until it is amended.

Conversation History and Data Retention

Conversation history. We store messages exchanged through Concierge and portal AI features to support responses and conversation continuity. We do not specify a fixed automatic archiving or deletion period for these records in this Policy.

Portal records. We retain trip and traveler records, shared notes and revision history, tips, organization memberships, and portal AI conversations as needed to provide the Services and support the organization’s use, subject to applicable agreements and legal obligations. Removing a user, deactivating a product, disconnecting a destination, or marking a record deleted does not necessarily erase all associated records, archived conversations, backups, or information already delivered to recipients. To request erasure, contact us as described below.

Billing and agreement records. We may retain invoices, payment and seat history, agreement acceptance records, and records needed to resolve disputes, prevent fraud, or comply with accounting, tax, and other legal obligations after access ends.

Account information. Account closure or removal of access does not necessarily erase associated records. Retention depends on the type of record, the purposes described in this Policy, applicable agreements, and legal obligations. You can request deletion as described below.

Usage information. We use activity and error logs to operate, secure, and troubleshoot the Services. This Policy does not promise that logs are anonymized or deleted on a fixed schedule.

Managed accounts. Retention of information processed on an organization’s behalf is subject to the applicable agreement and legal obligations. Contact your organization or Lumo about records associated with an organization-provided account.

How We Store and Secure Your Information

We use AWS infrastructure for hosting and data storage. Portal AI conversation files are stored with server-side encryption. Security measures and data handling differ across systems and service providers. No system is completely secure, and we cannot guarantee absolute security of your information.

Your Choices and Rights

You may decline to provide personal information, in which case we may be unable to provide some or all of the Services. You have the right to request that we:

  1. Delete your personal information
  2. Provide you with a copy of your personal information
  3. Correct or update inaccurate information
  4. Restrict or object to certain uses of your information

To make a request, contact us at privacy@thinklumo.com. We may be unable to fulfill requests in certain cases where our legal obligations or the privacy rights of others take precedence, and we will explain why if that is the case.

Other Important Privacy Information

Individuals Under 16

Our Services are not intended for individuals under 16. We do not knowingly collect personal information from anyone under 16. If we become aware that we have done so, we will delete that information promptly.

California Users

California Civil Code Section 1798.83 permits California residents who have provided personal information to request certain information about our disclosure of that information to third parties for direct marketing purposes. To make such a request, contact us at privacy@thinklumo.com.

Canadian Users

Canadian residents are entitled to access their personal information collected by Lumo, subject to certain legal exceptions. To request access, correction, or additional information about our data practices, contact us at privacy@thinklumo.com.

Notice to Users of Employer or Organization-Provided Services

When Services are made available through an organization, that organization determines how it uses traveler information, assigns access, and configures sharing and notifications. Its privacy notices and any applicable agreement with Lumo also govern that use. Where Lumo processes personal information on the organization’s behalf, we act under the applicable agreement and instructions; Lumo remains responsible for processing it performs for its own account administration, billing, security, and other purposes described in this Policy. Contact the organization for questions about its use of your information. You may also contact privacy@thinklumo.com, and we will coordinate where appropriate to address your request.

Managing Your Settings. Use available product controls to update profile information, manage notification destinations, or disconnect authorized integrations. You may stop SMS messages by replying STOP where supported. Declining or withdrawing messaging consent does not itself deactivate an organization’s purchased seats. Revoking access or deleting a destination does not delete copies already held by recipients.

Updates to This Policy

We may update this Privacy Policy from time to time. If there are significant changes, we will notify you by posting a notice on the Site and, where appropriate, via the email address associated with your account. Where a change requires consent or another step under applicable law or our existing privacy commitments, we will take that step before applying the change. Publishing an updated policy does not by itself authorize materially different uses of information collected under an earlier policy.

Contact Us

If you have any questions about this Privacy Policy, please contact us:

Email: privacy@thinklumo.com
Postal address: Resilient Ops, Inc., 1 Broadway Fl 14, Cambridge MA 02142, USA
Phone: +1 (866) 452-1961