Back to Directory
Agnamo

Privacy Policy

Effective date: April 15, 2026  |  Last updated: May 9, 2026

This Privacy Policy describes how Agnamo ("we," "us," or "our") handles information in connection with Agnamo and the Agnamo application surfaces it links to (including Supadash, Control Tower, Lux Chat, Agnamo, Comet Clip, and youBuilder). These tools are operated for internal business use by authorized Agnamo personnel and approved contractors.

1. Scope

This policy applies to Agnamo (luxdeploy.com) and the Agnamo application surfaces accessible from it. These are not consumer-facing products. Access is restricted to authorized Agnamo personnel and approved contractors. Each application surface may have additional, app-specific data practices noted in-product.

2. Information We Access

The Agnamo applications may access the following categories of data:

Internal operational data read from Agnamo's internal systems, which may include:

The specific systems and pipelines used to manage this data are proprietary to Agnamo and are not disclosed in this policy.

Google account data collected at sign-in via Google OAuth 2.0:

No other Google account data, including profile photo, contacts, calendar, Drive, or any other Google service data, is accessed or stored by Agnamo applications.

3. Google Sign-In and Authentication

Agnamo applications use Google Sign-In (OAuth 2.0) solely to authenticate authorized users. When you sign in with Google, we receive your email address, display name, and Google account ID from Google's OAuth service.

This Google user data is used exclusively to:

Your Google account data is not sold, rented, shared with third parties, or used for advertising, profiling, or any purpose beyond authentication. It is not used to train machine learning models. It is not transferred to any other party except as necessary to perform authentication via Google's own OAuth infrastructure.

Agnamo's use of Google user data complies with the Google API Services User Data Policy, including the Limited Use requirements.

4. How Data Is Used

Data accessed by Agnamo applications is used solely to:

We do not sell, license, or share this data with any third party for commercial purposes.

5. Data Storage and Security

Agnamo applications operate primarily as read-only front ends (with limited write access where required) backed by Agnamo's internal infrastructure. Data access is governed by access control policies. Data is transmitted over HTTPS. Operational data is not persisted in the browser beyond the current session except where explicitly noted in-app. Google authentication tokens are managed by Google's OAuth infrastructure and are not stored on Agnamo servers. Specific technologies and configurations underlying Agnamo's infrastructure are proprietary and not disclosed here.

6. Cookies and Local Storage

Agnamo applications may use browser localStorage to save user preferences such as filter presets. This data stays on your device and is not transmitted to any server. No cookies are set by Agnamo for tracking or advertising purposes. Google Sign-In may set cookies managed by Google's authentication infrastructure; these are governed by Google's Privacy Policy.

7. Access Control

Access to Agnamo applications is controlled at the network and application level. Only authorized Agnamo personnel and approved contractors may use these tools. If you believe you have received access in error, contact us at the address below.

8. Third-Party Services

Agnamo applications rely on the following third-party infrastructure providers. These providers host or deliver the applications and supporting services; they do not receive or process Google user data on our behalf:

Each provider maintains its own privacy and data processing policies. We do not control their data handling practices.

9. Data Retention

Agnamo applications do not independently retain Google authentication data beyond the authenticated session. Retention schedules for Agnamo's internal operational data are governed by Agnamo's internal policies and are not disclosed in this document.

10. Changes to This Policy

We may update this policy as the applications evolve. The "Last updated" date at the top of this page reflects the most recent revision. Continued use after changes constitutes acceptance of the revised policy.

11. Contact

Questions or concerns about this policy can be directed to:

Brick - Agnamo Support
brick