LAZweaver

Terms of Service

The legal suite below is published in draft. It has not been reviewed by counsel and no customer has been asked to accept it.

LAZweaver Master Terms of Service & Subscription Agreement

Last Updated & Effective Date: 17 September 2026
Document Version: 1.0.0-draft
Status: DRAFT — NOT YET PUBLISHED. This document has not been reviewed by counsel and no customer has been asked to accept it. Every clause marked [REVIEW: …] needs the owner's or a lawyer's confirmation before publication; the list is at the top of `README.md`.
Operating Entity: Alons Advanced Technologies Private Limited ("Alonstech", "Company", "we", "us", or "our")
Product: LAZweaver [REVIEW: the hostnames this product will be served on. GISweaver's equivalent line names three; LAZweaver's cell is not bootstrapped and no hostname is settled.]
Applicable Cell / Region: India Data Plane (in-mumbai-1), serving customers in every country

1. Introduction, Legal Capacity & Formation of Agreement

1.1. Contractual Relationship. This Master Terms of Service and Subscription Agreement ("Terms", "Agreement") constitutes a legally binding contract between Alons Advanced Technologies Private Limited (a private limited company incorporated under the Companies Act, 2013, with its registered office in Kerala, India, hereinafter referred to as "Alonstech") and the entity, organisation, sole proprietorship, partnership, or professional individual accessing or using the LAZweaver service ("Customer", "Organisation", "You", or "Your").

1.2. Product Description. LAZweaver is a hosted LiDAR and point-cloud processing service (collectively, the "Service" or "Platform"). The Customer supplies point clouds it has acquired or been given; LAZweaver's engine reads them, runs the processing the Customer asked for — thinning, denoising, ground and class extraction, terrain and surface models, corridor and powerline work, tiling and packaging — and writes the results back as files the Customer downloads. It is a processing service and not a workspace: it does not acquire survey, does not host a collaborative editing environment, and does not stand between the Customer and its own clients.

  • The Customer's inputs and the Service's outputs are stored under a prefix in object storage that belongs to that Organisation. No Organisation's prefix is readable by another, by any route.
  • The people who use the Service are the firms that produce point clouds and the firms that consume them: drone and aerial LiDAR operators, terrestrial and mobile scanning firms, survey and civil engineering consultancies, mining and quarrying operations, transmission and corridor contractors, and the project offices that commission such work.

1.3. Authority to Bind. If you are accepting these Terms on behalf of a company, corporate enterprise, partnership, government body, or other legal entity, you represent and warrant that you possess full legal power and authority to bind that entity. If you do not, or if you do not agree with each provision set out here, you must not create an account, submit a point cloud, or otherwise access the Service.

1.4. Electronic Contract Formation. In accordance with the Information Technology Act, 2000 (as amended) and the Indian Contract Act, 1872, this Agreement is an electronic record generated by a computer system and does not require a physical or digital signature. By checking the registration consent box, signing in with verified credentials, or submitting a job, you signify your assent to these Terms.

1.5. Age & Professional Requirement. The Platform is strictly a business-to-business (B2B) and professional commercial service. You affirm that every individual user operating under your Organisation is at least eighteen (18) years of age and legally competent to contract under Indian law.

2. Account Structure, Identity & Tenant Isolation

2.1. Structure. LAZweaver's structure is deliberately shallow, and these Terms describe only what exists:

  • Organisation: the legal entity, the billing tenant, and the unit of isolation.
  • Members: the people in that Organisation.
  • Runs (Jobs): one submission of one point cloud for processing, with the parameters it was submitted under.
  • Artifacts: the files a run produced — the classified cloud, the derived models, the tiles, the report — together with the run's own ledger of status, events and logs.

There are no branches, no projects and no shared workspaces. A clause describing them would describe software that does not exist.

2.2. Roles. Access within the Customer's Organisation is governed by exactly four roles, and the Platform recognises no others:

  • owner: ultimate administrative and commercial authority, including billing, plan changes and transfer of ownership. Exactly one Owner is maintained per Organisation, enforced by the database.
  • admin: every capability of the Owner except the transfer of ownership itself.
  • billing: the plan, the invoices and the billing profile. It confers no ability to read or submit survey data.
  • member: the base membership row — belongs to the Organisation, and does the work.

Alonstech staff access. [REVIEW: whether staff assumption of a customer Organisation is offered at launch, and which capabilities are withheld when it is. GISweaver's §2.2 names ten withheld capabilities; LAZweaver's staff surface is not built to that shape and this Agreement must not describe a control it does not have.]

2.3. Session & Credential Security.

  • Every sign-in is identified by a random, opaque token held in a browser cookie that page scripts cannot read and that the browser does not send on requests made from other sites. Alonstech keeps only a one-way hash of each token, so a copy of our records does not yield a usable session. Every change made through the browser is additionally protected against cross-site request forgery. The cookies LAZweaver sets, and their attributes, are listed in full in Section 14 of the Privacy Policy.
  • Password credentials are salted and hashed — never encrypted, never recoverable — using the memory-hard Argon2id key derivation function with a cryptographically random per-password salt. Multi-factor authentication (TOTP) with replay guards is available and is strongly recommended for every administrative account.
  • Programmatic access is by API key, where the Organisation's plan includes it. A key is shown once, is stored only as a hash, and is scoped to the Organisation that minted it. The Customer is responsible for the confidentiality of its credentials and for everything done under them, and must notify Alonstech immediately on discovering a compromise.

2.4. Tenant Isolation in the Database. Every record that belongs to an Organisation is isolated inside the database itself, by rules the database engine applies to every query regardless of which part of the application issued it. No account the running Platform uses can switch those rules off. A request for a record belonging to another Organisation is answered exactly as a request for a record that does not exist, so that neither the record nor its existence is disclosed. Object storage is separated the same way: each Organisation's inputs and outputs live under a prefix reachable only by credentials scoped to that prefix.

3. Scope of the Service

3.1. Intake.

  • Accepted inputs. The engine reads LAS and LAZ point clouds, including cloud-optimised point clouds (COPC). A file is identified by its content, never by its filename or extension, and a file whose content is not one of these is refused at intake.
  • Verification. Every upload is verified against the SHA-256 checksum declared before transfer, and a mismatch is refused. The file's header, bounds, point format and georeferencing are then read and reported back, and its integrity is checked; each check reports pass, warn or fail, and the Customer sees all of them before a run is submitted.
  • Malware scanning. No antivirus scanner is installed on any LAZweaver host, and uploaded files are not scanned for malware. We state this rather than implying otherwise. The exposure is narrower than a file-sharing product's — a point cloud submitted by an Organisation is readable only by that Organisation's own members, there is no sharing route by which a file reaches anyone outside it, and the engine parses point-cloud structure rather than executing anything — but it is not nothing, and the Customer should not upload a file it received from a third party and has not itself checked. [REVIEW: whether to commit to a scanning date the way GISweaver's §3.1 does. A condition with a date is a commitment; one without is a disclosure. The owner should choose deliberately.]
  • Refused at intake. Formats other than LAS, LAZ and COPC — E57, PLY, PTS, proprietary scanner formats, raster imagery, CAD — are not accepted. Alonstech makes no commitment as to when, or whether, any further format will be accepted.

3.2. Processing.

  • A run is one point cloud, one set of parameters, one result. The Customer either chooses a named preset — terrain, powerline, survey or full — or, where the plan includes the preset library, composes the run from the stages the engine publishes (thin, denoise, classify, terrain, powerline, corridor) with their own parameters. Every plan includes the standard run; choosing how the cloud is processed is a plan capability.
  • Before submitting, the Customer may ask the engine what a submission would cost in work and time. That answer is an estimate derived from the file and the parameters. It is not a quotation and not a guarantee.
  • Outputs. Depending on the run and on the Organisation's plan, a run produces the classified point cloud, a cloud-optimised point cloud (COPC), a streamable tile pyramid (LAZ LOD or OGC 3D Tiles 1.1), derived surfaces and rasters, contours where the run produced them, a report, and an assembled deliverable package. Producing a format is a plan capability; downloading what has already been produced is not, and is refused to nobody.
  • The run ledger. Every run writes its own status, its events, its logs, its report and its artifact list into the Organisation's prefix. That ledger is what the Customer reads to know what happened, and it is retained with the run.

3.3. What the Service Does Not Do, Stated Rather Than Implied.

  • LAZweaver does not acquire survey data, does not fly, scan or measure anything, and does not certify any result.
  • Every derived product is a mathematical transformation of the Customer's own input. A ground classification, a terrain model, a contour, a volume, a corridor clearance or a powerline catenary computed by the engine is constrained by the density, accuracy, completeness, no-data extent and declared reference frame of the cloud supplied. It is planning-grade output for a qualified professional to check, and it is not a certified survey, a certified quantity, or a safety determination.
  • The Customer, as the qualified surveying or engineering professional, remains solely responsible for ground-truthing, datum and CRS verification, and the professional certification of anything it delivers to its own clients on the strength of a LAZweaver output.
  • There is no sharing of a run with another Organisation, no public link, no guest link, and no recipient account. A run is readable by the members of the Organisation that submitted it and by nobody else.

3.4. The Console, the API and the MCP Server. The Service is reached through the LAZweaver console in a browser, through its HTTP API where the plan includes API keys, and — where a deployment enables it — through a Model Context Protocol server exposing the same operations. All three are the same Service under these Terms, and a capability the plan does not include is refused identically on all three.

4. Subscriptions, Metering, Pricing & Invoicing

4.1. Plans, the Meter and the Ceilings. LAZweaver is sold as tiered subscription plans. Every published plan version states, as numbers a customer can read before buying:

What it governs Meaning
Points each month The purchased allowance: how many points the Organisation may process in a calendar month. This is the meter.
Points in one run The largest cloud the plan will take in a single run. A ceiling on each run, not a total; nothing accumulates towards it.
Members How many people the Organisation may have in it.
Storage How many gigabytes of clouds and deliverables the Organisation may hold.
Retention How long a finished run's outputs are kept. See Section 5.
Concurrent runs How many runs may be in flight at once.

Plan capabilities — the preset library, each export format, programmatic access, recording a review decision, and publishing a finished run into a GISweaver workspace — are stated against each plan in the same way.

  • Published plan versions are immutable. Alonstech does not alter the price, the quotas or the capabilities of a published plan version. A change takes effect through a newly published version, on renewal or on an explicit plan change.
  • Quotas govern additions only. An Organisation that exceeds a quota after a downgrade or an expired promotion keeps everything it already holds, and is prevented from adding until it is within the limit or upgrades.
  • Exhausting the monthly points allowance is a commercial answer and never an operational one. A run refused because the allowance is spent is answered with a payment status and the remedy is to buy more or wait for the month. A run refused because our queue is full is answered with a rate-limit status, is never a charge, and is never sold. Keeping the two apart is what stops an outage of ours reading to a customer as a bill.

4.2. Starting Plan and Trials. [REVIEW: the starting plan, whether a trial is offered, and on what terms. No plan version is published in this repository — the plan catalogue is created and deliberately empty — so this Agreement cannot state a price, an allowance or a trial length without inventing one.] A free tier requires no payment and therefore involves no tax decision.

4.3. Fees, Currency and Indian GST.

  • Indian customers. Fees are denominated and billed in Indian Rupees (INR, ₹) and are subject to Goods and Services Tax under the Central Goods and Services Tax Act, 2017, the State Goods and Services Tax Acts, 2017, and the Integrated Goods and Services Tax Act, 2017. The Service is classified under Services Accounting Code (SAC) 998313 (Information technology consulting and support services) and 998314 (Information technology design and development services), both within Group 99831 of Heading 9983. Treatment follows the Customer's verified GSTIN and Place of Supply: intra-state supply attracts CGST and SGST; inter-state supply attracts IGST; an unregistered buyer is charged according to the state code of its billing address.
  • Tax invoices bear a consecutive serial number, unique for the financial year, in accordance with Rule 46(b) of the Central Goods and Services Tax Rules, 2017, and are immutably archived. As an internal control exceeding what the Rule requires, serials are issued so that the series contains no gaps: a number is never consumed by an invoice that was not in fact issued. [REVIEW: the invoice series prefix. The deployment design records "LW" pending the chartered accountant's sign-off, which has not been given.]

4.4. Customers Outside India.

  • LAZweaver accepts business customers in every country. Outside India the Service is offered to businesses only. A buyer who cannot confirm business use, and who holds no tax identifier where one is required, is declined politely at checkout rather than sold to.
  • A supply to a business customer outside India is an export of services, invoiced in the sale currency with the INR equivalent and the applicable reference rate stated, and is zero-rated under a Letter of Undertaking without payment of IGST. Each such invoice carries the statutory endorsement to that effect.
  • Where the customer is a business in the European Union or the United Kingdom, its VAT number is required, is validated, and is printed on the invoice together with the reverse-charge statement.
  • [REVIEW: the Letter of Undertaking must be on file, and the export invoice format and endorsement wording signed off by the chartered accountant, before the first export invoice is raised. Neither has happened.]
  • Alonstech monitors the registration thresholds that apply to a non-resident supplier in the jurisdictions it sells into, and registers where it becomes liable. Nothing in this Agreement is tax advice to the Customer.

4.5. Payment, Renewal and Grace.

  • Indian payments are processed through an RBI-authorised payment aggregator (presently Razorpay); payments from outside India are processed through Stripe. Alonstech does not receive or store card numbers or banking credentials.
  • There is no automatic renewal and no stored payment mandate. Alonstech holds no standing instruction, e-mandate, card token or recurring authorisation against any Customer, and never charges an Organisation without that Organisation initiating the payment. At the end of a paid period the Organisation renews by completing a checkout it starts itself.
  • Where a period ends without a renewal, the subscription enters a seven (7) day grace period during which the plan and its full entitlements continue uninterrupted. If it is not renewed by the end of that period, the subscription expires and the Organisation reverts to the free tier, subject to Section 4.1's rule that quotas govern additions only.
  • Non-payment never deletes an artifact and never hides a run.

4.6. Refunds and Cancellation, Under a Meter.

  • The Customer may cancel at any time from the billing screen. Cancellation takes effect at the end of the currently paid period.
  • Because the Service allocates compute on submission and consumes it irreversibly, points already processed are not refundable: the work was done and cannot be undone. An unused allowance is likewise not refundable and does not carry into the following month, and these Terms say so rather than leaving it to be discovered.
  • Alonstech does refund, on request and without argument, in each of these cases: a double charge arising from a gateway error; a charge for a subscription period in which the Service was unavailable for a material part of the period; and points consumed by a run that failed for a fault of ours — where a run fails because of a defect in the engine or the platform rather than because of the data or the parameters it was given, the points it consumed are credited back.
  • Nothing in this Section limits any right the Customer has under applicable consumer-protection law.

4.7. Dormancy and Reinstatement. Where a subscription has lapsed and no payment has been made, the Organisation may, after notice stated to it in advance, be placed in a frozen state in which no new run may be submitted. Freezing never affects what is already held: throughout dormancy the Organisation retains sign-in, complete read access, and unrestricted download of every artifact it holds, subject only to the plan retention period that was in force when each run finished (Section 5.2). No dormant period of any length results in deletion beyond that retention period.

5. Retention: What Is Kept, and What Is Never a Consequence of Payment

5.1. The Principle. Payment state governs additions; it never governs retention. No dunning workflow, payment lapse, downgrade or commercial dispute causes a Customer's point clouds, artifacts, run records or audit records to be deleted, degraded, watermarked or withheld.

5.2. The Plan Retention Period — the one thing that does remove data, and how it is done. Unlike a document workspace, a processing service stores gigabytes per run, and a plan states how long a finished run's outputs are kept. That period is a number on the plan, it is stated before purchase, and its floor on every published plan version is at least one day.

  • Retention runs from the completion of a run, and is the period in force at that time. A later downgrade does not shorten the retention of a run that has already finished.
  • Removal at the end of a retention period is a scheduled act with notice, never a consequence of payment state. The Organisation is told in advance, told what is due to be removed and on what day, and can download it or move to a plan that keeps it for longer at any point before that day.
  • What is removed is the bytes, never the record. The run itself — its identity, its parameters, its status, its events, its report, the manifest of what it produced and the SHA-256 checksum of each artifact — is kept, and survives the removal of the artifacts it names. A checksum of geometry identifies no person and proves what was delivered.
  • An Organisation's own uploaded source clouds count against its storage quota and are subject to the same period and the same notice.

5.3. Customer-Initiated Erasure and Account Closure. An Organisation's data is permanently purged from the active data plane only on an explicit, verified, multi-step erasure request made by the authenticated Organisation Owner. Erasure is deliberately built so that no request the Platform can receive — from a browser, from an API client, or through a defect — destroys customer data: the Owner records and confirms an intent, and the destruction itself is carried out by an Alonstech operator using an authority the running Platform does not hold. [REVIEW: the erasure flow described here is GISweaver's design and is not yet implemented in this repository. Either build it before publication or state plainly that erasure is presently a support request handled manually.]

  • Confirmation requires the Owner to restate the mode of erasure, to acknowledge by name each category of record that will survive it, and to re-authenticate.
  • Whichever mode is chosen, the following survive and the Owner is told so before confirming: tax invoices and payment records, retained under Section 9.2 of the Privacy Policy; the audit trail, which is append-only and becomes pseudonymous once the accounts it names are gone; and existing backups, which age out on their own schedule and which nothing here reaches.

5.4. Discontinuation. Should Alonstech discontinue the Service or a cell, it will give the Organisation not fewer than one hundred and eighty (180) days' written notice and will maintain complete, unrestricted and free download of everything the Organisation holds throughout that period.

6. Indian Geospatial Regulation

6.1. The Framework. The acquisition, processing, handling and distribution of geospatial data in India is governed by the Guidelines for Acquiring and Producing Geospatial Data and Geospatial Data Services Including Maps (Department of Science and Technology, 15 February 2021) and the National Geospatial Policy, 2022 (S.O. 6095(E), notified 28 December 2022, which does not supersede the 2021 Guidelines).

6.2. Threshold Value of Spatial Accuracy. The DST Guidelines set threshold values of spatial accuracy, of which the two relevant to terrestrial survey work are one (1) metre horizontal and three (3) metres vertical, at one RMSE in accordance with the Department's Office Memorandum of 28 November 2022. Airborne, terrestrial and mobile LiDAR of the kind LAZweaver processes is ordinarily finer than those values, and the Customer should assume that its clouds are.

6.3. Localisation. All processing of Indian point-cloud data on LAZweaver takes place, and all such data is stored, exclusively within the India data plane (in-mumbai-1, AWS Mumbai). Point coordinates, classified clouds and derived surfaces do not transit foreign edge proxies, international CDN workers, overseas key-value stores or international log aggregators. Edge services are confined to authoritative DNS and the sign-in challenge.

6.4. The Customer's Own Obligations. The Customer is solely responsible for:

  • verifying that its data does not attribute, label or depict any entry on the negative list of sensitive attributes notified by the Department of Science and Technology. Explanation 1 to paragraph 8(iii) of the Guidelines states expressly that there will not be any negative list of prohibited areas; the restriction is on labelling and depiction of specified attributes, not a prohibition on collecting data within any area;
  • observing the categories the Guidelines reserve to Indian entities irrespective of accuracy, including terrestrial mobile mapping, street-view surveys, and surveying within Indian territorial waters;
  • holding every statutory permission its acquisition required, including DGCA / DigitalSky authorisations for drone flight, local administration clearances, and landholder authorisations where the law requires them.

6.5. Customers Outside India. A Customer acquiring or processing data in another jurisdiction is responsible for that jurisdiction's own rules on survey, aerial acquisition, mapping and data export. Alonstech gives no advice on them and makes no representation that processing on the India cell satisfies them. [REVIEW: whether any foreign jurisdiction LAZweaver expects to sell into prohibits the processing of its high-accuracy spatial data outside its borders. This affects who may be sold to before a second cell exists.]

7. Intellectual Property & Ownership

7.1. Customer Ownership. As between the parties, the Customer retains full, exclusive and unencumbered ownership of every point cloud, trajectory, control file, classification override, parameter set and note it supplies, and of every artifact the Service derives from them ("Customer Data"). A derived product of the Customer's data is the Customer's.

7.2. Limited Operational Licence. The Customer grants Alonstech a non-exclusive, worldwide, royalty-free, limited licence to store, read, parse, transform, classify, tile, render and serve Customer Data solely and strictly to the extent necessary to provide, maintain, secure and support the Service for that Customer. Alonstech will not sell, commercialise, aggregate for resale, publicly disclose or claim ownership of any Customer Data.

7.3. No Training. Alonstech does not use Customer Data to train, fine-tune or evaluate any machine-learning model, whether its own or a third party's, and does not permit any sub-processor to do so.

7.4. Alonstech's Rights. Alonstech retains all right, title and interest in the LAZweaver engine, the control plane, the console, the algorithms, the presets, the design, the documentation, the APIs, and the "LAZweaver" and "Alonstech" names and marks. The Customer will not reverse engineer, decompile, disassemble or create derivative works of the Platform. [REVIEW: the trade-mark position on the LAZweaver name, and whether a mark has been applied for.]

7.5. Publishing into GISweaver. Where an Organisation's plan includes it and the Organisation asks for it, a finished run may be published into that same company's GISweaver workspace. The two products are separate — separate accounts, separate billing, separate customer records — and this capability changes none of that: it moves the Customer's own files from one service it holds to another service it holds, on its instruction, and Alonstech acquires no further right in them by doing so.

8. Acceptable Use

8.1. Prohibited. You and your users shall not:

  • Submit any point cloud or derived dataset that you do not have the right to process, or whose processing would breach an obligation you owe to a third party.
  • Submit data in violation of the National Geospatial Policy, 2022, the 2021 DST Guidelines, or the sovereignty, integrity or national security of India.
  • Submit files containing malicious code, or files crafted to exploit a parser rather than to be processed.
  • Probe, scan or test the vulnerability of, or attempt to circumvent, any authentication, quota, metering or tenant-isolation control.
  • Use an automated agent to consume the Service other than through the API that exists for that purpose, or to evade a quota or a rate limit.
  • Resell, sublicense, lease or operate a service bureau on top of the Service without a written agreement with Alonstech that permits it.
  • Impersonate any person, entity or surveying authority, or misrepresent an affiliation with any government revenue or survey department.

8.2. Enforcement. Alonstech refuses at intake any file that fails checksum verification or format identification, and may suspend an Organisation in accordance with Section 12 where an egregious breach of this Section or of statutory law occurs.

9. Operational Telemetry

9.1. Collection and Use. By using the Platform you accept that operational telemetry — system metrics, error reports and performance measurements about the Platform itself — is collected and used to keep the Service reliable, to diagnose and fix faults, and to improve performance.

9.2. What It Does Not Contain. This telemetry is designed and checked so that it contains no personal data and no customer data: no coordinates, no point geometry, no file names, no tokens, no tax identifiers. If we ever find telemetry carrying such data we treat it as an incident, remove it and close the cause.

10. Service Levels and Maintenance

10.1. What Is Targeted, and What Is Not Promised. LAZweaver is a batch processing service and its service levels are stated as such.

  • Alonstech targets an operational availability of 99.9% for the API, the console and the artifact download endpoints in each calendar month, excluding scheduled maintenance and force majeure.
  • Alonstech targets admitting a submitted run to the queue within the same measure.
  • Alonstech does not promise a completion time for any run, and no completion time is a term of this Agreement. How long a run takes depends on the size and density of the cloud, the stages requested and the load on the queue. The engine will tell the Customer what a submission is expected to cost in work and time before it is submitted; that estimate is not a commitment.
  • [REVIEW: whether any service credit is offered against the availability target. None is offered above, which means the target is a statement of intent rather than a remedy. That is a commercial decision the owner should make deliberately.]

10.2. Scheduled Maintenance. Maintenance — migrations, security patching, engine upgrades — is performed in designated low-traffic windows (ordinarily 00:00 to 04:00 IST). Advance notice of significant scheduled downtime is given by in-app notice or email.

10.3. Portability. Alonstech builds on open, portable technologies — Go, Rust, PostgreSQL, OCI containers, S3-compatible object storage, and open output formats (LAS, LAZ, COPC, OGC 3D Tiles) — so that a Customer's data and a deployment of the Platform can be moved without a proprietary dependency. Every artifact this Service produces is in a published open format that another tool can read, which is the part of portability that matters most to a customer. Alonstech commits to conducting a documented restore-and-exit drill at least once in every twelve (12) month period and to recording its date and outcome. As at the effective date of these Terms no such drill has been performed, and Alonstech makes no representation that a restore or exit has been rehearsed.

11. Intermediary Status under Indian Law

11.1. Status. In respect of the point clouds and derived files stored on behalf of Customers, Alonstech receives, stores and transmits records on behalf of another person and accordingly considers itself an "intermediary" within the meaning of Section 2(1)(w) of the Information Technology Act, 2000. Whether Alonstech is an intermediary in respect of any particular record, and whether the exemption under Section 79 is available, are matters for a competent authority to determine on the facts. Alonstech does not by this Section declare itself to hold that status.

11.2. Conditions. The exemption under Section 79 applies only where the conditions in Section 79(2) are met and does not apply in the circumstances set out in Section 79(3). Alonstech conducts itself so as to qualify: it does not initiate transmissions, does not select receivers, and does not select or modify the data the Customer submits beyond performing the processing the Customer asked for; and it observes the due diligence prescribed by the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 (as amended, most recently by G.S.R. 120(E) dated 10 February 2026), including the grievance mechanism at Section 15.

12. Term, Suspension & Termination

12.1. Term. This Agreement commences when you first register an account or access the Platform and continues until terminated in accordance with these Terms.

12.2. Suspension for Cause. Alonstech may temporarily suspend an Organisation where required to do so by a court, a law enforcement agency or a statutory authority; where the Customer is in material breach of Section 8 or of Indian geospatial regulation; or where the Organisation's activity poses an imminent threat to platform security or to other tenants.

  • The default scope of suspension disables submitting runs, adding members and other writes, and retains sign-in, read access, billing management and artifact download. This is enforced by construction: reads and downloads are admitted before any suspension check is applied, so a suspended or frozen Organisation can always open and download everything it holds.
  • Security containment. Where an active security incident is under way, or where a judicial or statutory order so requires, Alonstech may suspend access in full, including read and download, for as long as containment or the order requires and no longer. Alonstech will notify the Organisation of such a suspension and of its basis as soon as it is lawful and safe to do so, will restore read and download at the earliest point consistent with containment, and will not use this paragraph for a commercial purpose. Nothing in it permits deletion or degradation of Customer Data.

12.3. Termination by the Customer. The Customer may terminate at any time by closing its account and cancelling its subscriptions. Before closure the Customer is strongly encouraged to download every artifact and invoice it wishes to keep.

12.4. Survival. Sections 1, 4.3, 4.4, 5, 6, 7, 9, 11, 13, 14, 15, 16 and 17 survive termination or expiry.

13. Warranties & Disclaimers

13.1. Mutual. Each party warrants that it has the legal power and authority to enter into this Agreement.

13.2. As Is. EXCEPT AS EXPRESSLY PROVIDED HERE, THE SERVICE IS PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS. TO THE MAXIMUM EXTENT PERMITTED UNDER APPLICABLE INDIAN LAW, ALONSTECH AND ITS DIRECTORS, EMPLOYEES AND AFFILIATES DISCLAIM ALL WARRANTIES OF ANY KIND, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT.

13.3. No Warranty as to Processing Results. Alonstech does not warrant that any classification, ground extraction, surface model, contour, volume, clearance or other derived product is correct, complete or fit for the Customer's purpose. These are computations over data Alonstech did not acquire and cannot verify, and Section 3.3 states plainly what they are and what they are not.

13.4. Rendering. Alonstech does not warrant that point-cloud or tile rendering in a browser will be error-free or uninterrupted across every hardware configuration, unsupported browser or degraded connection.

14. Limitation of Liability & Indemnification

14.1. Exclusion of Consequential Damages. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL ALONSTECH, ITS AFFILIATES, OFFICERS, DIRECTORS OR AGENTS BE LIABLE TO THE CUSTOMER OR ANY THIRD PARTY FOR ANY INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES, INCLUDING DAMAGES FOR LOSS OF PROFITS, GOODWILL, WORK STOPPAGE, TENDER DISQUALIFICATION, BOUNDARY OR QUANTITY DISPUTES, RE-FLIGHT OR RE-SURVEY COSTS, COMPUTER FAILURE OR LOSS OF BUSINESS REVENUE, ARISING OUT OF OR IN CONNECTION WITH THE USE OR INABILITY TO USE THE SERVICE.

14.2. Aggregate Cap. IN NO EVENT SHALL ALONSTECH'S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THIS AGREEMENT, WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), STATUTE OR OTHERWISE, EXCEED THE TOTAL AMOUNT ACTUALLY PAID BY THE CUSTOMER TO ALONSTECH UNDER THIS AGREEMENT IN THE TWELVE (12) MONTHS IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM, OR INDIAN RUPEES FIVE THOUSAND (INR ₹5,000), WHICHEVER IS GREATER. [REVIEW: GISweaver's cap is copied here unchanged. Confirm it is the right figure for a product whose customers process corridor surveys worth substantially more than the subscription.]

14.3. Customer Indemnification. The Customer agrees to defend, indemnify and hold harmless Alonstech, its officers, directors and employees against any claim, liability, damage, judgment, loss, cost or expense (including reasonable legal fees) arising out of or relating to:

  • the Customer's breach of these Terms or of Section 8;
  • the Customer's lack of right to process any dataset it submitted;
  • the Customer's infringement of a third party's intellectual property or land rights;
  • the Customer's non-compliance with the National Geospatial Policy 2022, the 2021 DST Guidelines, DGCA drone regulations, or the equivalent law of any other jurisdiction in which it acquired the data;
  • any dispute between the Customer and its own clients, tender authorities or landholders as to a deliverable the Customer produced.

15. Grievance Redressal Mechanism

15.1. Designation. In compliance with Rule 3(2) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 (as amended), Alonstech has designated a Grievance Officer and publishes that officer's contact details, together with this mechanism, in this section — reachable through the Terms and Privacy links on the LAZweaver console and in every message the product sends.

15.2. Grievance Contact Details:

  • Grievance Officer: [name published on the website and in the application] [REVIEW: the officer's name must be published before these documents are published. GISweaver leaves the same placeholder; publishing a mechanism with no named officer does not satisfy Rule 3(2).]
  • Entity: Alons Advanced Technologies Private Limited
  • Registered Address: Alons Advanced Technologies Private Limited, No. 4/461, 2nd Floor, Suite No. 1123, Valamkottil Towers, Thrikkakara, Ernakulam, Kochi, Kerala 682021, India (CIN U62099KL2026PTC102744)
  • Official Grievance Email: [email protected]
  • Support Email: [email protected] [REVIEW: whether a product mailbox — [email protected] — should be published instead, once that domain is live. The company address above is used here because it exists today and the product domain's status is unconfirmed.]

15.3. Who May Complain. The mechanism is open to any user of the Platform and to any victim, whether or not that person is a user or a Customer of Alonstech.

15.4. Timelines under the IT Rules.

  • Acknowledgement within twenty-four (24) hours of receipt.
  • Disposal within seven (7) days of receipt. (This period was shortened from fifteen days by G.S.R. 120(E) dated 10 February 2026, in force from 20 February 2026.)
  • Certain categories of removal request carry shorter statutory periods — thirty-six (36) hours for specified requests under Rule 3(1)(b), and two (2) hours for content of the kind described in Rule 3(2)(b). Alonstech observes the shortest period applicable to the complaint before it.

15.5. Data Protection Grievances. The Digital Personal Data Protection Act, 2023 has been brought into force in stages by notification G.S.R. 843(E) dated 13 November 2025. Sections 5 to 17 of that Act — which include the obligations of a Data Fiduciary, the rights of a Data Principal and the right of grievance redressal at Section 13 — are not yet in force, and are expected to commence approximately eighteen months from the publication of that notification. Pending commencement, Alonstech voluntarily receives, acknowledges and disposes of data protection grievances through the same officer and on the same timelines, and will comply with the statutory scheme when it commences. Details are in Section 15 of the Privacy Policy.

16. Governing Law, Dispute Resolution & Jurisdiction

16.1. Governing Law. This Agreement, its construction, validity and performance, and every dispute arising out of or related to it, are governed by and construed in accordance with the substantive laws of the Republic of India, without giving effect to any choice-of-law or conflict-of-law rule.

16.2. Negotiation. The parties shall first endeavour in good faith to resolve any dispute by consultation between authorised officers within thirty (30) calendar days of written notice.

16.3. Arbitration. If the dispute is not settled within thirty (30) days it shall be referred to and finally resolved by binding arbitration under the Arbitration and Conciliation Act, 1996 (as amended).

  • A sole arbitrator appointed by mutual consent or, failing agreement within fifteen (15) days, appointed by the High Court of Kerala under the Act.
  • Seat and legal venue: Ernakulam / Kochi, Kerala, India.
  • Language: English.
  • The award is final, binding and enforceable in any court of competent jurisdiction.

16.4. Jurisdiction. Subject to the arbitration agreement above, the courts of competent jurisdiction at Ernakulam / Kochi, Kerala, India have exclusive jurisdiction over all court proceedings, applications for interim or injunctive relief, and enforcement actions under or in connection with this Agreement. [REVIEW: an Indian seat and Indian jurisdiction are copied from GISweaver. For a product sold to businesses in the EU, the UK and the US from day one, confirm with counsel that this is enforceable and commercially acceptable, or adopt a neutral seat for foreign customers.]

17. Miscellaneous

17.1. Modifications. Alonstech may modify these Terms to reflect changes in the Platform, in statutory regulation, or in business practice. Notice of a material modification is given at least thirty (30) days before its effective date, by email to Organisation Owners or by a prominent in-app notice. Continued use after the effective date constitutes acceptance.

17.2. Severability. If any provision is held invalid, illegal or unenforceable, it is enforced to the maximum extent permissible and the remaining provisions continue in full force.

17.3. No Waiver. No waiver of any breach constitutes a waiver of any prior, concurrent or subsequent breach.

17.4. Entire Agreement. These Terms, together with the Privacy Policy, Part B (Trust Commitments) of the Vision, Mission & Governance statement, and any written enterprise addendum, constitute the entire understanding between the parties and supersede all prior discussions and representations.

  • Part A (Mission & Vision) and Part C (Governance Framework) of that statement are published as statements of intent and of internal practice. They are expressly not incorporated into this Agreement, create no contractual obligation, and are not representations on which the Customer is entitled to rely. Part B alone is contractual, and where Part B and these Terms differ, these Terms prevail.

17.5. Versioning. Each published version of these Terms carries a version identifier, shown with the document. The version in force when an Organisation accepts these Terms is recorded against that acceptance, together with the address at which it was published. A later revision does not rewrite what an earlier Customer accepted. Where these Terms are modified under Section 17.1, the modified version takes effect for all Customers on its stated effective date; Alonstech does not require an existing Customer to re-accept a modified version except where it says that it does.