Terms & Conditions

LEGAL NOTICE & JURIDICAL BINDING

This Master Terms and Conditions of Service Agreement (hereinafter referred to as the "Agreement" or "Terms") constitutes a legally binding, enforceable corporate contract between SAURISH VENTURES PRIVATE LIMITED (hereinafter referred to as the "Company"), including all its architectural modifications, structural designs, and software subdivisions under the brand name IdentiCamp, and any authorized educational board, university trust, school system, management collective, or academic enterprise (hereinafter referred to as the "Institutional Client" or "User").

By executing a digital onboarding setup, registering an active multi-tenant workspace configuration, allowing structural API integration handshakes, or accessing any sub-dashboards or mobile portal layers, the Institutional Client acknowledges that they have read, understood, and agreed to be unconditionally bound by these terms. If you are executing this contract on behalf of an institution, you declare under legal penalty that you possess absolute corporate signing authority to bind the respective entity to this sovereign software covenant.

ARTICLE I: DEFINITIONS & SOFTWARE SYSTEM SPECIFICATIONS

1.1 Multi-Tenant SaaS Infrastructure: Refers to the unified, cloud-native enterprise operating environment engineered by the Company. Multiple distinct institutions (Tenants) access a centralized cloud server architecture running an identical core application database layer while maintaining absolute logical data separation, structural cryptographic parameterization, and isolated schema parameters.

1.2 Universal App Codebase: Refers to the single, comprehensive mobile and web application architecture deployed across all customer brackets. It utilizes an automated, real-time Role-Based Routing Engine during user authentication to dynamically modify system states, view matrices, and security clearances based on the stored Student_Type or database permission tiers (e.g., School vs. College configuration).

1.3 Automated Design Rendering Engine: Refers to the automated backend software components designed to instantly receive unstructured database streams and automatically render dynamic, high-resolution digital profile formats and identity blueprints based on pre-set institutional layout templates without manual formatting cycles.

ARTICLE II: SCOPE OF SERVICES & PROGRAMMATIC BOUNDARIES

2.1 Baseline Phase 1 Functional Modules: The Company agrees to provide access to the operational service suites as structured in the active project definition matrix, including:

Super Admin Controls: High-level cross-institute health metrics, licensing caps, tenant status mapping, and device heartbeat log metrics.

Principal & Director Dashboards: Executive operational summary widgets, automatic exceptions logging, approval centers for leave matrix parameters, and timetable overrides.

AI Timetable & Resource Allocation Grid: Structural processing engines designed to auto-calculate lecture parameters, laboratory sub-batch splitting boundaries, and conflict-free hall utilization.

Security & Attendance Console: Check-In arrays supporting barcode mapping, universal USB/OTG QR scanners, and specialized camera face-recognition logging tools.

2.2 Explicit Hardware & Integration Decoupling: The Institutional Client explicitly notes, understands, and agrees that the Company's operational scope is strictly confined to the software engineering layer.

The Company exposes structural, fully documented programmatic Application Programming Interfaces (APIs) for attendance, security logging, and device heartbeat monitoring workflows.

The acquisition, physical delivery, network structural setups, power configurations, and on-site hardware maintenance of Bureau of Indian Standards (BIS) certified facial recognition scanners, eSSL nodes, Hikvision terminals, or automated gate equipment remain the exclusive, one hundred percent (100%) liability and operational cost of the designated third-party hardware vendor or institutional technical team.

The Company assumes zero legal, monetary, or operational liability for physical device malfunctions, hardware configuration errors, or failure of local vendors to successfully map hardware endpoints against the exposed software APIs.

ARTICLE III: DATA POLICY, SOVEREIGN APIS & GOVERNMENT PRIVACY SHIELD

3.1 Institutional Data Ownership & Roster Compliance: The Institutional Client remains the absolute data controller concerning all personal identifiable information (PII), student records, faculty profiles, and financial transaction indices injected into the multi-tenant instance. The User guarantees that all student and staff master rosters, guardian communication logs, and identity parameters are legally acquired and fully compliant with national data privacy regulations.

3.2 Government API Framework Handshakes (UDISE+ / DigiLocker / APAAR):

The system is structurally engineered to interact with official verification registries, including the Government APAAR ID Verification Engine.

The Institutional Client is strictly obligated to supply their officially authorized, verified API credentials, developer access keys, or authorized endpoint mappings via API Setu, UDISE+, or DigiLocker portals.

The Company’s background synchronization scripts will run execution calls to match student parameter streams against the government server response matrices. Under no scenario shall the Company be held liable for latency spikes, credential blocks, or database lookup failures stemming directly from server downtimes on the sovereign government registry networks.

3.3 Bank-Grade Cloud Encryption Protocols: The Company deploys institutional-grade security mechanisms to maintain absolute structural isolation of tenant parameters. All databases are securely isolated on premium cloud configurations (AWS/Azure) utilizing end-to-end industry-standard encryption protocols during transit and storage stages.

ARTICLE IV: ACCOUNT BILLING, LICENSING CAPS & PAYMENT PROCESSING

4.1 Subscription Compliance & Capacity Limits: Access to the multi-tenant SaaS grid is governed by explicit operational thresholds (e.g., student enrollment numbers, active staff quotas, and connected device caps) established in the verified project proposal. Exceeding these baseline computational quotas will automatically trigger system rate-limiting blocks until an enterprise upgrade invoice is settled.

4.2 Payment Gateway Integration Standard (Razorpay / Cashfree):

For integrated fee ledger modules, the Institutional Client is strictly required to provide valid, verified Razorpay or Cashfree Merchant Live Keys directly into the configuration panel.

The Company's software architecture will integrate standard programmatic webhooks and encrypted API endpoints to record successful transaction events and systematically update the instance's fee books.

Absolute legal and structural transaction compliance parameters, including the Payment Card Industry Data Security Standard (PCI-DSS), tokenization protocols, and transaction security rules, are managed exclusively by the merchant gateway processor. The Company acts purely as a data-logging layer and assumes zero monetary liability for settlement delays or payment system faults.

ARTICLE V: INTELLECTUAL PROPERTY & PROHIBITED UTILIZATION CODE

5.1 Proprietary Ecosystem Perimeter: The Institutional Client explicitly acknowledges that all source codes, database schemas, structural software layout models, architectural framework variations, AI algorithmic libraries, and user interface designs (UI/UX) engineered under the IdentiCamp brand are the exclusive property of SAURISH VENTURES PRIVATE LIMITED.

5.2 Strict Prohibited Operational Commands: Users, administrative staff, or institutional IT engineering networks are strictly prohibited from executing, attempting, or facilitating any of the following parameters:

Reverse-engineering, decompiling, scraping, or systematically extracting structural modules from the universal application codebase or web portals.

Bypassing, overriding, or tampering with the Role-Based Routing Engine to acquire unauthorized access permissions to the Super Admin or executive director dashboards.

Utilizing exposed software APIs for any unauthorized third-party development, database harvesting, or unaligned external hardware tracking pipelines.

Multiplexing logins, creating secondary unsanctioned system instances, or bypassing preset multi-tenant operational limits.

Violation of any clause listed within this Article will result in immediate, permanent account suspension, complete structural cloud instance lockdown, and immediate escalation to federal law enforcement networks under the Information Technology Act of India.

ARTICLE VI: LIMITATION OF LIABILITY & SYSTEM WARRANTIES

6.1 System Warranty Disclaimer: The multi-tenant enterprise SaaS infrastructure is delivered to the Institutional Client "As Is" and "As Available" without any express or implied operational warranties. The Company does not guarantee that the software's functional parameters will be completely uninterrupted, zero-latency, or entirely free from minor algorithmic anomalies during intense compute loads.

6.2 Indemnity Caps: To the maximum extent permitted under applicable corporate and cyber laws, SAURISH VENTURES PRIVATE LIMITED shall never be held liable for any direct, indirect, incidental, punitive, or consequential business damages, including but not limited to:

Institutional revenue leakages, data tracking failures, or administrative operational disruptions resulting from network downtime;

Delays by telecom service lines during automated parental push notification loops or BSNL DLT SMS delivery schedules;

Local data corruption incidents caused by hardware breakdown, network interruptions, or localized failures to manage the Offline Sync Queue correctly before system resets.

Under all commercial scenarios, the absolute financial liability limit of the Company for any claim generated out of this software framework shall never exceed the total monetary subscription amount actually settled by the Institutional Client to the Company within the preceding three (3) calendar months.

ARTICLE VII: LEGAL AMENDMENTS, TERM & JURISDICTION

7.1 Periodic Structural Adjustments: The Company reserves the right to periodically alter, update, or append structural parameters within these Terms to maintain compliance with changing national education laws, internet governance frameworks, and data protection protocols.

7.2 Term and Graceful Server Offloading: These Terms remain active as long as the Institutional Client maintains an active data allocation block on our cloud servers. Upon termination or expiration of the baseline contract, the system will lock all principal and administrative access consoles. Roster databases will be held securely within the cloud framework for a maximum buffer zone of sixty (60) calendar days to facilitate standard portability extracts, after which all student parameters will be permanently purged from the cloud servers.

7.3 Sovereign Indian Jurisdiction: This contract shall be exclusively governed, managed, and evaluated under the statutory parameters of the Republic of India. Any legal conflicts, compliance disputes, or breach-of-contract litigations shall be presented strictly within the competent courts located in Palghar / Thane, Maharashtra, India.