Lens x Mirantis

Limited and Fair Use Policy

August 17, 2026

Lens Desktop, developed by Mirantis, Inc., connects to third-party services, including Google APIs, to provide certain user-facing features. This policy sets out two things: the limits Mirantis places on its own use of data obtained through those services, and the expectations Mirantis places on users when using the integrations that rely on them.

1. Limited Use Commitment

1.1 General Principle

Lens connects to a third-party service only where a user chooses to enable that connection. Whatever the service, Mirantis applies the same principle to the data it receives: that data is used solely to deliver and improve the feature the user enabled, it is not repurposed for unrelated ends, it is not sold or transferred to unrelated parties, and it is not retained for longer than the feature requires.

Where the provider of a connected service sets its own conditions on how data from that service may be used, Mirantis observes those conditions in addition to the commitments in this policy. Where the two differ, the stricter requirement applies.

1.2 Google API Data

Lens' use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Sections 2 and 3 describe how this commitment applies in practice: what data Lens accesses from Google and why, how that data is stored and protected, and the specific limits Mirantis places on its use, transfer, and human access.

2. Data Accessed

2.1 Categories of Data

Where a user chooses to sign in to Lens with a Google account, Lens accesses a limited set of Google account information:

  • Account identifier and email address — used to create and authenticate the user's Lens ID account, to recognize the user across sessions and devices, and to associate the account with the correct organization or subscription.
  • Basic profile information, such as display name and profile image — used to show the signed-in user within the Lens Desktop interface and, where a shared workspace is in use, to identify team members to one another.

Where a user separately chooses to enable an optional integration connecting Lens to another Google service, the data accessed is limited to what that integration requires to function. Examples of the kind of data such an integration may involve include calendar entries used to schedule maintenance windows, or directory information used to provision access for members of a team. Any such integration is optional, requires its own authorization through Google's consent screen, and is described to the user at the point of activation.

Lens requests the narrowest permissions that support the features described below. No data is requested for analytics, marketing, or functionality unrelated to those features.

2.2 Features Supported

The data described above is used for authentication and account management: verifying the user's identity when signing in with Google, maintaining the authenticated session, associating usage with the correct subscription and organization, and displaying the signed-in account within the product. Where a user has enabled an optional integration, the data supports only the specific feature that user activated.

Google user data is not used for any purpose other than providing and improving these user-facing features. It is not used for advertising, profiling, or resale, is not used to build datasets unrelated to features visible to the user, and is not combined with data from other sources for unrelated purposes.

2.3 Storage and Protection

Google user data is stored only to the extent necessary to operate the features described above. Authentication and account information is held within Lens Cloud Services, hosted on Amazon Web Services (AWS) infrastructure in the European Union and the United States.

Data is encrypted in transit using TLS 1.2 or higher, and encrypted at rest using AES-256. Access is restricted through role-based access controls and least-privilege provisioning, and administrative access is logged.

Mirantis maintains an information security program certified to ISO/IEC 27001 and audited under SOC 2. AWS, as the infrastructure provider underlying Lens Cloud Services, maintains ISO/IEC 27001 certification and SOC 2 attestation for the services used. Reports and certificates are available on request through the channels in section 9.

3. Limits on Use of Data

3.1 Use

Data obtained through Google APIs is used only to provide and improve user-facing features that are prominent in the Lens Desktop interface.

3.2 Transfer

Mirantis does not transfer or sell Google user data to third parties, including advertising platforms, data brokers, or information resellers. Data is transferred only where necessary to provide or improve user-facing features with user consent, for security purposes, to comply with applicable law, or as part of a merger, acquisition, or sale of assets following explicit user consent.

3.3 Advertising and Lending

Google user data is not used to serve advertisements of any kind, and is not used to determine credit-worthiness or for lending purposes.

3.4 Human Access

No Mirantis personnel read Google user data by default. There is no standing or routine access to this data, and no access takes place unless one of the circumstances below applies:

  • Support. Where a user requests assistance and gives affirmative agreement, on a case-by-case basis, for Mirantis personnel to access the specific messages or files needed to resolve that request. Consent is obtained for each individual case and is not granted in advance, implied by the use of Lens, or carried over between support cases. Access is limited to the data the user identifies, ends when the case is closed, is revocable by the user at any time, and is recorded in an access log.
  • Security. Where access is necessary to detect, prevent, or investigate abuse, fraud, or a security incident affecting Lens or its users.
  • Legal. Where required to comply with applicable law or valid legal process.
  • Internal operations. Where the data has been aggregated and de-identified, so that no individual user or record can be identified.

The security and legal circumstances above are exceptional, are not used as a substitute for user consent, and do not extend to routine operation of the service.

Mirantis administers the infrastructure on which Lens Cloud Services run. Personnel performing system administration and maintenance operate under role-based access controls, least-privilege provisioning, and audit logging consistent with the Mirantis SOC 2 and ISO/IEC 27001 programs. Administrative privileges over the systems that store Google user data do not authorize personnel to read the content of that data outside the circumstances listed above.

3.5 Artificial Intelligence and Machine Learning

Data obtained through Google Workspace APIs is not used to develop, improve, or train generalized or non-personalized artificial intelligence or machine learning models. This restriction applies in addition to the commitments described in the Lens AI Transparency Policy.

4. Fair Use of Integrations

The integrations described in this policy are provided to support the normal operation of Lens. Fair use means using them for their intended purpose and at a scale consistent with that purpose.

When using an integration, users must not:

  • extract, mirror, or retain data in bulk beyond what the relevant Lens feature requires;
  • use an integration to build a separate product, dataset, or service, or to resell data obtained through it;
  • circumvent, or attempt to circumvent, rate limits, quotas, or access controls applied by Mirantis or by the third-party provider;
  • use an integration in a manner that breaches the terms of the third-party provider whose data is being accessed;
  • authorize access to data the user is not entitled to share, or connect an account without the necessary permission from its owner or their organization.

Where use of an integration places disproportionate load on Lens or on a third-party service, or where use is inconsistent with this policy, Mirantis may apply rate limits or suspend the integration for the account concerned. Where practical, Mirantis will contact the account holder before doing so.

5. User Control

The Google integration is optional and requires the user to explicitly authorize access through Google's consent screen. Users may review and revoke Lens' access at any time from the Google Account permissions page. Revoking access ends further data retrieval by Lens.

6. Retention and Deletion

Google user data is retained only as long as necessary to provide the features described in this policy, and is not kept for unrelated purposes once it is no longer needed.

Specific retention periods and deletion timelines are governed by the agreement in place between Mirantis and the customer. For users of Lens Cloud Services this is set out in the Lens Terms of Service, the Lens Cloud Services Additional Terms, and the Lens Data Processing Agreement; where a customer has entered into a separate written agreement with Mirantis, the terms of that agreement apply. Current operational detail is maintained in the Lens documentation at docs.k8slens.dev.

Where a user disconnects their Google account or their Lens ID account is closed, the associated Google user data is deleted or returned in accordance with those terms. Residual copies held in routine backups are removed on the normal backup rotation cycle. Retention beyond these periods occurs only where required by applicable law or valid legal process.

7. Related Policies

This policy supplements, and should be read together with, the Mirantis Privacy Policy, the Lens Terms of Service, and the Lens AI Transparency Policy.

8. Changes to This Policy

Mirantis may update this policy as the integrations described in it evolve. Material changes will be reflected in the date at the top of this page, with notice provided through Lens Desktop or the Lens website where appropriate.

9. Contact