Refund & Cancellation Policy

PREAMBLE & CORPORATE SCOPE

This Master Refund, Cancellation, and Subscription Termination Policy (hereinafter referred to as the "Policy") establishes the legally binding financial, operational, and structural parameters between SAURISH VENTURES PRIVATE LIMITED (hereinafter referred to as the "Company"), operating its proprietary multi-tenant campus orchestration software ecosystem, IdentiCamp, and any legally registered educational institution, school board, university trust, or academic entity utilizing the platform (hereinafter referred to as the "Institutional Client").

By registering an account, initializing an infrastructure setup sprint, executing a milestone payment, or deploying the universal codebase, the Institutional Client explicitly acknowledges, understands, and agrees to be bound by the exhaustive clauses defined herein.

ARTICLE I: GENERAL SERVICE ARCHITECTURE & CONTRACT INTENT

1.1 Nature of Enterprise SaaS Framework: The Institutional Client explicitly recognizes that IdentiCamp is an elite, multi-tenant Software-as-a-Service (SaaS) operational infrastructure. Deployment requires dedicated allocation of cloud multi-tenant spaces on Amazon Web Services (AWS) or Azure, custom schema configuration setups, structural cryptographic key mapping, and systematic localized API parameterizations.

1.2 Mobilization and Resource Overhead: Upon formal execution of the project proposal or the sign-off of the requirement freeze milestone, the Company immediately mobilizes internal technical engineering teams, database architects, and security deployment specialists. Consequently, initial monetization allocations represent immediate physical and logistical infrastructure setup costs, not generic retrievable software credits.

ARTICLE II: SUBSCRIPTION PACKAGES AND MILESTONE BILLING CONTRACTS

2.1 Phased Financial Milestones: For institutional enterprise contracts, billing is structured around operational milestone achievements rather than flexible recurring consumer terms. The standard billing allocation follows a strict phase logic:

Phase 1 (Mobilization & Freeze): Thirty-Five Percent (35%) of the total contractual value upon official project initialization and database schema layout freeze.

Phase 2 (Core Module Readiness): Thirty-Five Percent (35%) upon the successful configuration of the AI Timetable Engine, Face Recognition arrays, and the deployment of User Acceptance Testing (UAT).

Phase 3 (Production Sign-off): Thirty-Percent (30%) upon final production server sync, live deployment on designated domains, and full operational handover.

2.2 Usage Volume and Per-Seat Metering: For usage-based subscription tiers (Per-Student billing matrix), fees are calculated based on the maximum student profiles registered within the Institutional Client's localized data framework during an academic cycle. Once a record or biometric profile is created, mapped, or registered via the universal app engine, it represents active service utilization and cannot be retroactively modified or claimed for a refund.

ARTICLE III: STRICT REFUND NEGATION MATRIX (NON-REFUNDABLE CLAUSES)

3.1 Immediate Non-Refundability Parameters: The Institutional Client explicitly agrees that all milestone fees, annual platform activation tokens, setup configurations, and transactional subscription deposits are one hundred percent (100%) non-refundable, non-creditable, and non-reversible.

3.2 Operational Allocations and Server Sunk Costs: Once a designated multi-tenant database space is initialized or an active integration handshake is executed with third-party networks (such as API Setu, UDISE+, or DigiLocker registries), the absolute infrastructure costs are sunk. Under no scenario shall the Institutional Client demand financial restitution for technical hours already spent or cloud space allocations already reserved.

3.3 Exclusion of Hardware and Network Disruption: IdentiCamp operates exclusively as a software layer via exposed programmatic APIs. If an Institutional Client experiences local operational friction, including but not limited to:

The breakdown, misconfiguration, or localized malfunction of physical BIS-certified face scanners, barcode readers, or gate endpoints;

Local internet blackout spikes causing lag in the localized check-in console;

Delays by third-party telecom infrastructure networks during BSNL DLT SMS delivery loops or WhatsApp business API connection dips;

Such instances shall NOT constitute valid grounds for refund requests, financial chargebacks, or software termination claims against the Company.

ARTICLE IV: SUBSCRIPTION CANCELLATION WORKFLOWS & PROTOCOLS

4.1 Formal Termination Intent Notice: If an Institutional Client intends to terminate their access matrix or cancel their upcoming academic deployment phase, a formal Notice of Subscription Cancellation must be digitally documented and transmitted to the Company’s executive oversight desk at identicamp@saurishpvtltd.com.

4.2 Notice Period Thresholds: To prevent structural script errors and execute graceful multi-tenant deletion pipelines without risking global database synchronization, the cancellation notice must be filed at least thirty (30) operational business days prior to the scheduled automatic renewal date or the commencement of the next academic roster integration sprint.

4.3 Administrative Pipeline Cleanout Fee: Cancellations executed during an active deployment phase or after core AI module setups have been configured will attract a standard administrative pipeline cleanup overhead. The Institutional Client shall remain contractually liable to settle all pending engineering milestones achieved by the Company up to the exact operational minute of the formal cancellation notice.

ARTICLE V: DOUBLE BILLING RESOLUTION AND TRANSACTION OVERHEADS

5.1 Payment Gateway Transaction Discrepancies: In instances where network communication latency within the payment gateway infrastructure (Razorpay/Cashfree integrated webhooks) causes duplicate transactional entries or accidental over-billing on the fee ledger dashboard, the following resolution protocol applies:

5.2 Verification Window: The Institutional Client must flag the exact duplicate transaction timestamp, reference settlement tracking keys, and merchant invoice numbers to our centralized billing registry at identicamp@saurishpvtltd.com or via the enterprise helpline +91 8446355542.

5.3 Automated Restoration Terms: Once the internal accounting framework verifies the duplicate or anomalous gateway chargeback status, the Company will process a system-level override. The excess duplicate transaction amount will be automatically reversed back to the Institutional Client’s original merchant bank account registry or source card within seven (7) operational banking days. Compliance with transaction framework security parameters, including PCI-DSS, is strictly maintained by the payment gateway partner.

ARTICLE VI: DATA RETENTION, DELETION, AND EXTRACTS POST-CANCELLATION

6.1 Data Security Shield Upon Dissolution: The exact second a cancellation or termination contract is finalized, the multi-tenant routing engine will systematically lock access permissions to the principal dashboards, HOD consoles, and parent mobile application routing panels.

6.2 Purging Roster Records: To prevent localized server drag and protect minor data privacy parameters under Indian Cyber Laws, all student and staff master rosters, face registration metrics, barcode indices, and historical timetable records stored inside the cloud instance will be permanently purged after sixty (60) days from the active termination date.

6.3 Data Portability Extracts: Within this 60-day buffer zone, the Institutional Client may request a standardized CSV/Excel data portability extract of their core attendance logs and administrative database fee records. The Company will charge a dedicated data-recovery processing fee for generating these compiled asset bundles.

ARTICLE VII: DISPUTE MITIGATION AND ANTI-CHARGEBACK COVENANTS

7.1 Absolute Ban on Arbitrary Chargebacks: The Institutional Client explicitly agrees that they shall not initiate arbitrary financial chargebacks, transaction blockages, or payment reversals through their banking institutions or corporate credit network lines without exhausting the formal evaluation and internal mediation pipelines provided by the Company.

7.2 Legal Consequences of Unauthorized Chargebacks: If an Institutional Client executes an unauthorized chargeback or clawback maneuver for milestone deployments already configured by our engineering grid, the Company reserves the absolute right to instantly terminate all live production server layers, lock down database instances, and file direct commercial legal litigation for financial damage and breach of contract.