Terms & Conditions
1. Acceptance of Terms: By accessing and using Lubhata QC Suite, you accept and
agree to be bound by the terms and provisions of this agreement.
2. User Conduct: You agree not to use the service for any unlawful purpose or any
purpose prohibited under this clause. You agree not to use the service in any way that could damage
the site or general business of Lubhata.
3. Account Setup: To use features of the Service, you must register for an account.
You are responsible for safeguarding your password and any activities under your account.
4. Supplementary Tool Classification: Lubhata QC Suite operates strictly as a
supplementary quality control tool interfacing with officially supported API endpoints (e.g.,
Autodesk Revit API). It is designed to enhance user workflows and does not intend to replicate,
circumvent, or maliciously compete with native proprietary services (e.g., Navisworks) in violation
of publisher guidelines.
5. Third-Party Acceptable Use (AUP): By utilizing this software in conjunction with
third-party platforms (including but not limited to Autodesk Construction Cloud or Revit), you agree
to abide by the respective publisher's Acceptable Use Policy. Lubhata is not liable for data misuse
or ToS violations committed by the end-user.
6. Modification of Terms: We may amend these Terms at any time by posting a revised
version. By continuing to use the service, you accept the changes.
7. Reverse Engineering Audit: If any attempt to reverse engineer the Lubhata plugin
is detected, Lubhata reserves the right to perform a complete system audit and suspend connectivity
immediately to protect intellectual property.
Software License & Violation Act
1. Grant of License: Lubhata grants you a revocable, non-exclusive,
non-transferable, limited license to download, install and use the application strictly in
accordance with these terms.
2. Restrictions: You agree not to, and you will not permit others to license, sell,
rent, lease, assign, distribute, transmit, host, outsource, disclose or otherwise commercially
exploit the Application or make the Application available to any third party.
3. Reverse Engineering: You agree NOT to reverse-engineer, decompile, trace, or
extract the core collision-detection methodologies or algorithms housed within the Lubhata QC Suite
server. All cloud-based AI and geometric analysis processes are the exclusive intellectual property
of Lubhata.
4. API Interfacing: This software extracts metadata solely through sanctioned,
documented API endpoints provided by the host platform (e.g., Autodesk). It does not employ
unauthorized scraping or extraction techniques that compromise the host's cloud infrastructure.
5. Violation Act: Any unauthorized circumvention, scraping, or automated extraction
of backend AI intelligence may result in immediate termination of the license, legal injunctions,
and claims for damages arising from intellectual property theft.
Privacy Policy (Web & Plugin)
1. Data Collection: We showcase that we don't use your data in any means. We only
store and record your name, company name, mobile no, and email for future updates on the portal,
notifications, and analytics counts to provide you with the best services. Registration requires
compulsory acceptance of this strictly minimal data collection.
2. Data Usage (Strictly No AI): Model metadata and clash data are strictly siloed.
We do not look into, share, or use your data for AI training. It is not our data;
it belongs solely to you.
3. Security & Telemetry: We implement advanced encryption (DPAPI for local
credentials) and secure data storage practices. We track unique Hardware IDs and session data to
detect tampering or account sharing.
4. Feedback & Iteration: We improvise and continuously work based on feedback posted
on LinkedIn and our helpdesk feedback page.
5. Deletion & Revocation: End-users may request full deletion of their data by
contacting business@lubhata.com. You may revoke consent at any time, which will
result in the immediate termination of plugin and web access.
Technical Data Usage & API Documentation
Autodesk Compliance Alignment
While not officially endorsed by Autodesk, we respect Autodesk's
intellectual property and have engineered Lubhata QC Suite to completely align with the Autodesk App
Store Developer Guidelines. We ensure that all BIM metadata extraction is performed securely via
official APIs.
1. Local Data Storage
The plugin stores minimal data locally on the user's machine, primarily for authentication caching,
license states, export reports, and security tracking.
Authentication & Project Cache (auth_v2.bin):
Stored at %AppData%\LubhataQCSuite\auth_v2.bin. This file persists session tokens, user
roles, and active plan configurations. Passwords are never stored in plaintext and are instead secured
via Windows DPAPI.
Security Audit Tracker (sec_audit.dat):
Stored at %AppData%\LubhataQCSuite\sec_audit.dat. This log tracks detected attempts at
tampering or the presence of unauthorized debuggers to protect the integrity of the Lubhata IP.
2. API Data Transmission
All communication targets api/data.php via authenticated Bearer Tokens.
- Telemetry: Sends hardware_id (SHA256 hash), device_name, and plugin version for
session locking.
- Sync & Audit: Transmits
audit_json containing Revit Health Metrics
(Unused Views, Imported CAD, Warnings, Duplicate elements) and ClashResults.
- Model Upload: Multipart payload of FBX geometry files used for 3D visualization.
Embedded Securities & Regulations
BIM Standard Compliance: Lubhata QC Suite incorporates principles for the strict
organization and digitization of information about buildings and civil engineering works securely.
Autodesk App Store Compliance: This application adheres to Autodesk's publisher
guidelines. We do not obtain user passwords for third-party services, nor do we misuse customer
metadata. Our privacy policy is embedded within the app and accessible via this portal.
Embedded Security & Data Storage: Lubhata is engineered with powerful embedded
securities and validation protocols. User data is protected with enterprise-grade security, and
users may request data isolation in specific jurisdictions to satisfy local data sovereignty laws.