Terms of Service

These terms govern your use of the NexoPlus lane access and FASTag platform — the website, the installable PWA, the mobile application, and the reader, camera and relay hardware they drive. Using any part of it means you accept them.

The platform is a product of NexoPlus Automations. These terms bind whoever uses it: an owner-operator running their own site, a resident welfare association, a company, a facility-management contractor, an integrator, a reseller, and every person holding an account on a deployment. Where any of those parties acts through another — a contractor wiring the gate, an agency running the desk — the party engaging them passes these terms on with the access and remains answerable for that person's compliance.

If you are accepting on behalf of an organisation, you warrant that you may bind that organisation. Where a separate signed agreement covers the deployment, that agreement prevails over anything here.

NexoPlus Automations grants the operator a non-exclusive, non-transferable and revocable licence to install and run the software at the sites covered by the commercial agreement, for the term of that agreement.

• A licence, never a sale. Nothing in these terms, in an invoice, or in payment of any fee conveys title. The software, and everything listed in section 3, stay the property of NexoPlus Automations.
• The operator's data is the other way round: it belongs to the operator throughout, and this licence says nothing that transfers it.
• Copying the software to sites outside the agreement, sub-licensing, lending, renting or otherwise re-supplying it to anyone else, removing or obscuring the product credit where it is enabled, or reverse engineering, decompiling or disassembling it is outside the licence.
• Every right not expressly granted in this section is reserved to NexoPlus Automations.

This section exists because a lane-control system is built beside its customer, and proximity is mistaken for authorship more often than it should be. Read it as the whole of the position.

Who owns what

The platform in its entirety — the source code and the compiled form of it, the database schema and data model, the reader, camera, barrier and relay services, the website, the PWA and the mobile applications, the templates, styling and screens, the documentation and help content, the interface design and architecture, and the names, logos, marks and trade dress used with any of them — is the exclusive property of NexoPlus Automations. It is protected by the copyright, trade-mark and other intellectual-property laws of India and by international treaties.

NexoPlus Automations is the sole author and owner of the product. It is not a work jointly authored with an operator, not a work commissioned or funded by an operator, and not work made for hire arising from an engagement. No payment, no fee, no purchase of hardware, no hosting arrangement, no data supplied, no requirement stated, no feedback given, no funding, and no commercial relationship of any kind creates or transfers an ownership interest in the software or in any part of it.

NexoPlus may supply anyone

The software is supplied to whomever NexoPlus Automations chooses. NexoPlus may license, sell, demonstrate, host, sublicense and distribute it, in any number of copies, at any price, to any person or organisation, and to more than one operator at the same address or in the same market — including organisations that compete with you. Nothing in a deployment, an exclusivity conversation, a volume of business, or a length of relationship grants you or any other operator an exclusive right, a territory, a field of use, a right of first refusal, or a right to be the only party supplied.

No ownership may be claimed

No operator, licensee, customer, reseller, distributor, integrator, installer, contractor, employee, agent or user shall claim, assert, publish, register or imply that they own, authored, developed, source, or have rights in the software or any part of it. Without limiting that sentence, and whether or not in good faith, you shall not:

• file, procure, support or allow the filing of an application to register a copyright, trade mark, patent, design, geometry or domain name that reproduces, incorporates, derives from or is confusingly similar to the software, its interface or any NexoPlus mark;
• rebrand, re-skin, rename or re-publish the software, or any screen, report, model or service of it, as your own product or as a product of another author;
• remove, obscure, overrule or alter a proprietary notice, credit, watermark, licence header or mark, or substitute another name for it;
• hold yourself out as the owner, maker, publisher or source of the software, in marketing, to a customer, to an investor, to an acquirer, to a court, or to a tax, subsidy, grant or procurement authority;
• distribute, disclose or publish the source code, internal architecture, credentials, protocols or security behaviour of the software, whether obtained from a deployment, from a device, or from a support engagement;
• use, copy or adapt anything reached under a support, trial, demonstration or evaluation engagement for a purpose beyond that engagement.

An operator's own records, images, reports and exports — the data generated at the operator's site — are not affected by this section. They are the operator's, and this section claims nothing over them.

Modifications and derived works

No modification, customisation, translation, adaptation, enhancement, integration or other derived work of the software may be made or exploited except under a written agreement that permits that specific work. Where such an agreement exists, ownership of everything NexoPlus Automations authored stays with NexoPlus Automations unless that agreement assigns something else in writing, signed on its behalf; and a licence to run a modification does not make it yours to supply to others.

Feedback

Ideas, bug reports, feature requests and other feedback about the software may be used in the product, without obligation, credit or payment to whoever gave them. Feedback gives no right in the software.

Names of other companies

These documents describe outside services by the kind of service they are rather than by name, because which provider an operator uses depends on that operator's own credentials. Any product, company or service name belonging to someone else is the property of its owner, and a reference of any kind here is descriptive only: it is not a licence from that owner, not an endorsement by it, and not a statement that NexoPlus Automations is authorised to use its mark.

There is no public sign-up. Every account is created by somebody who already holds the permission to create accounts, and access to a feature follows the account's category and its granted permissions.

• The operator is responsible for who is given an account and what that account can reach.
• Actions taken under an account are attributed to it through the audit log; sharing credentials defeats that and is prohibited.
• Five failed sign-ins lock the account for fifteen minutes, and only one session per account is live at a time — a new sign-in disconnects the older one.
• Vehicle owners may sign in to the phone app with their ten-digit contact number as both username and password. This is a convenience the operator enables, and the operator owns the risk of it.
• Changing an account's category or permissions signs that person out so the new access takes effect.

This software energises relays that move barriers and traffic signals. That is the whole point of it, and it is where the operator's responsibility is heaviest.

Hardware operations are logged for audit, but no real-time monitoring, intervention or safety assurance is provided or implied. Liability for injury, death or property damage arising from physical equipment operation rests with the operator.

Where NexoPlus Automations supplies hardware for a site — readers, controllers, relay boards, cameras, single-board computers, power supplies and the accessories named on the invoice — that hardware carries a warranty. Where the operator sources hardware itself, this section does not apply to it and the operator holds the manufacturer's own cover.

The first year

Supplied hardware is warranted against defects in materials and workmanship for one year from the date of delivery to the site, or from the date of the invoice if that is earlier. Within that period NexoPlus Automations will, at its option, repair the item, replace it, or refund its invoice price. A repaired or replaced item carries the balance of the original year or ninety days from the date it goes back, whichever is longer.

An item that fails outright within the first fifteen days is replaced rather than repaired, and the carriage both ways is on NexoPlus Automations.

What the warranty does not reach

This is a warranty against manufacturing defects, not against the environment a gate lives in. It does not cover, and NexoPlus Automations is not obliged to fix free of charge:

• Impact, dropping, crushing, water or dust ingress, corrosion, condensation, insect or rodent damage, or fire.
• Mains surges, lightning, an unstable, unregulated or wrongly rated supply, or reverse polarity.
• Operation outside the rated temperature, humidity or voltage envelope of the item.
• An unapproved power supply, an electrical load on a relay output above its rating, or wiring that does not follow the supplied map.
• Opening a sealed unit, removing labels or serials, or any repair, modification or re-flashing attempted by anyone other than NexoPlus Automations where that caused or worsened the fault.
• Wear and consumables: barrier arms, gaskets, lamps, batteries, cables, mounting brackets, casings, and any part with its own shorter manufacturer's cover.
• Theft, vandalism, tampering, or damage while in transit arranged by the operator or a third party.
• A fault that a remote check shows to be configuration, network, or the operator's own server rather than the item supplied.

The warranty also assumes the duties in section 5 were met: installation to a recognised standard, fail-safes fitted, and the relay map confirmed against the physical board before the lane carried traffic. Keep the invoice; a claim without a serial and a purchase record is a chargeable job, not a warranty one.

How to claim

Raise it through the support channel named in the commercial agreement, with the site identifier, the serial or asset tag, the symptom, when it started, and the logs from the period. NexoPlus Automations will try to diagnose remotely first, because most faults reported as hardware are not. Where the item has to come in, it is sent freight-prepaid to the address given at the time of the claim; where the claim is valid and inside the year, the return leg is on NexoPlus Automations.

After the year: the AMC

When the warranty period ends, hardware support continues only under an annual maintenance contract. An AMC is optional, is taken for a twelve-month term, is payable in advance, and renews on its anniversary unless either party gives written notice before it does.

If an AMC lapses and is later taken again, cover restarts at the new start date and nothing is back-dated across the gap; NexoPlus Automations may inspect the installation before resuming cover, and an inspection that finds a fault starts a chargeable repair, quoted before any work begins.

A hardware model may be discontinued. NexoPlus Automations will say so in writing, will keep supporting the versions under contract for the balance of that term, and will supply spares for a discontinued model while stock lasts. Nothing here limits a right that cannot be excluded by law.

The platform is supplied as it is built, and parts of it are not what their screens suggest. We would rather say so here than have it discovered at a gate.

• Demonstration screens. The visual workflow builder reached from the Automation menu is a design tool: what it produces is kept in the browser and is never written to the site's rules, and it drives no hardware. It is not a way to configure this site.
• Automation rules. On this build, the per-door reader services do not invoke the automation engine, so a tag read at a door does not fire a rule. Rules are evaluated only on a plate reading that has already been granted access, and what a fired rule can do is limited to logging, notifying, calling a webhook, updating a record or alerting an administrator — it does not drive a relay. Do not design a safety or security dependency on it.
• Reader-level switches. A reader's own enable and schedule settings are not read by the per-door services; control is per door.
• Camera recognition. Recognition done on the server rather than in the camera depends on a licensed third-party container the operator enables and supplies a licence key for. Where it is not running, or its licence lapses, plates come only from what a camera reports itself, and a lane that looked automatic stops reading.
• Motion capture. Where a camera's stream is analysed, the software saves a still because something moved. Sensitivity that suits a shaded lane over-triggers in open sun; tuning it is site work, and captures made from the camera test screen are records like any other.
• Documentation. The in-app help describes the screens as designed for. Where it and these terms disagree about what this build does, these terms govern what is supplied.

Features may be added, changed or withdrawn between releases. Continued use of an updated site accepts the software as updated.

The operator is the data controller for everything the site holds. NexoPlus Automations does not host, receive, copy or inspect that data in the ordinary running of the software.

• Obtain any consent or notice the law requires before reading tags, recognising plates, photographing people or logging a guard's position.
• Decide deliberately whether a lane's video stream is analysed for movement. That option is what turns a plate reader into a general camera, and everything it saves is your record to justify.
• Set retention periods that are no longer than needed — the defaults in the software are a starting point, not advice.
• Keep the server, its database file and its image folder protected; they contain the personal data described in the Privacy Policy.
• Honour requests from individuals about their own records. The software gives you the screens to do it; the duty is yours.
• Where a support engagement gives NexoPlus staff temporary access to a site, that access is governed by the support agreement and is logged.
• The split runs both ways: nothing here gives NexoPlus Automations a right in your data, and nothing gives you a right in the software. Section 3 says which way each of them falls.

The platform records what the people using it do. That record protects the operator as much as it protects NexoPlus Automations: it is how a dispute about who opened a barrier, who deleted a record or who changed a rule gets settled instead of argued.

What is recorded

• Every change to a record — creates, updates and deletes of accounts, permissions, categories, owner and KYC records, visitors, staff, readers, doors, rules, schedules and settings, with the account, the time and what changed.
• Every sign-in and sign-out, including failures and the source address.
• Every manual barrier and relay command, every keep-open, every forced state, and every test fired from a control screen.
• Every access decision — the tag, the lane, the outcome and the reason it was granted or refused.
• Exports, uploads, bulk deletions, whole-database clears and backups, and the update actions run through the in-product updater.

Not every keystroke is written down; the trail covers the actions that can later be disputed. The operator sets how long each class is kept, and the default for audit logs is ninety days — a shorter period is the operator's choice and deletes the evidence with it.

What that means in law

The parties agree that this record is the account of what happened at the site. An action carried by an account is treated as the operator's act, whether or not a person with authority pressed the button: an account holder is answerable for anything done under their credentials, and credential sharing is prohibited by section 4 for exactly this reason.

Rectification is chargeable

Where NexoPlus Automations is asked to put right something an operator caused, that is billable work, not warranty work and not a service-level event. It includes, and is not limited to:

• Recovering, rebuilding or re-keying data the operator deleted, overwrote or expired — and note that the software deletes rather than anonymises, so some of it may be unrecoverable at any price.
• Restoring configuration, permissions, reader or door mappings, schedules or rules that were changed on the operator's side.
• Re-issuing credentials, re-establishing access to a site, or re-doing an update the operator attempted themselves.
• A site visit, remote session or diagnostic whose cause turns out to be operator error, a change made by a third party, or a fault in equipment the operator supplied.

Such work is quoted at the rates current when it is done, before it starts, and NexoPlus Automations may make payment a condition of doing it. A finding that the fault is a genuine defect in the software, or in warranted hardware, moves it back inside sections 6 and 13 and off the invoice.

Leave the trail alone

Deleting or truncating audit rows, overwriting the log files, moving the server clock to make a timestamp lie, or disabling the recording of an action before taking it is a breach of these terms and of section 15, and the operator must preserve the trail wherever a dispute or a claim is reasonably in prospect.

Stated honestly: the trail is written on the operator's server, and a person with root on that machine can alter it. These terms do not pretend otherwise. What they do is make doing so a breach, and make NexoPlus Automations answerable only for what its own record can show.

The software provides backup tools. It does not carry the backup duty for you.

• A backup is a complete copy of the database, including every account, owner record, detection and log. Protect it as much as the live server.
• Cloud drive backup authorises an account with the drive provider the operator chooses, at the broadest file scope rather than a folder-scoped one; see the Privacy Policy for what that means and how to withdraw it.
• The retention scheduler deletes data on the schedule the operator sets. Deletion under a schedule is not a fault and is not recoverable from us.
• We are not liable for loss of data, or for the cost of reconstructing it, whatever the cause.
• A backup restores data, not rights. Neither a database copy nor anything reached through a deployment gives any claim over the software; section 3 continues to apply to every copy of it.

Balance, vehicle detail, challan and price features ask other companies over the operator's own credentials and connections. Which companies, and whether they will answer at all, is outside our hands, so these terms name none of them.

• Those services are independent. Their accuracy, limits, pricing and availability are outside our control, and we do not warrant them.
• They throttle. Expect rate limits and daily caps, and design around a lookup that simply fails for a while.
• A cached answer may be stale. Nothing here promises a real-time balance.
• A feature may stop working when a provider changes its interface, and may be withdrawn in a release.
• No relationship with any of those providers is claimed or implied. Nothing here is a representation that NexoPlus Automations is authorised to use any provider's name or mark, is a partner of it, or can obtain anything from it on your behalf.
• Using a lookup means using that service under its own terms, which you are responsible for holding. Automating, scraping or otherwise reaching a provider outside what it permits is your breach, not ours.
• The external database and URL-posting tools send data to endpoints the operator configures. What leaves the site through them is the operator's decision and the operator's compliance burden.

No uptime is guaranteed. A lane depends on the server, its power, its network, the reader attached to it and the barrier it drives. Any of those can fail, and the software cannot promise otherwise.

Maintenance, updates and configuration changes may take a site down temporarily. Where a site must keep working through a failure, continuous operation is achieved by physical means — a manual release, an attendant, or a gate that defaults open — and providing those means is the operator's task.

What this does not mean is that a fault goes unanswered. Section 13 sets out what support commits to when a site raises one.

Section 12 says no uptime is guaranteed. This section says what NexoPlus Automations does commit to when something is raised with it.

The two numbers

Both clocks run on the Indian Standard Time meridian, which is the time the Coimbatore courts keep, and both are stated as the standard engagement: a signed agreement may set tighter ones for a specific site, and where it does, that agreement governs.

What the clocks do not run on

• A third-party service that is down, throttling, or has changed its interface. Section 11 puts that outside our control, and the 48 hours does not start until the dependency is resolved.
• The operator's own server, storage, network, power, air conditioning, internet link, private network or VPN, and hardware the operator bought elsewhere.
• A fault introduced by a change the operator or another party made, or by a modified build. Reproduce it on the current supported build first.
• A request for something the software does not do. That is a change request, scoped and quoted, not a defect.
• Anything awaiting parts, a site visit window, or access the operator has not yet granted.

A missed response is escalated to the person named in the commercial agreement; the service levels are a commitment about how support is run and are not, by themselves, a source of refunds, credits or damages beyond what an agreement provides.

What the operator has to give a support engagement

• A way in: logs, and remote access where the fix needs it, granted for the duration and revocable — access taken under a support engagement is used for that engagement and is logged.
• A working backup before any intervention, per section 10.
• Somebody on site who can reach the lane, the board and the server.

Work that is not a defect in the software or in warranted hardware — recovery of operator-deleted data, reconfiguration, training, migration, or a visit that finds operator error — is chargeable under section 9. All amounts are exclusive of applicable taxes, including GST, which the operator bears.

The platform ships an update tool that pulls a release onto the machine it is running on and restarts that machine's services. It is a genuine remote-administration capability and is treated as one.

• It is gated behind a specific permission, and the operator decides who holds it.
• Using it applies code to that server immediately. There is no staged rollout, no canary and no rollback button in the product.
• An update that fails partway can leave a site in an inconsistent state. A tested backup before updating is the operator's responsibility.
• Where NexoPlus performs the update on the operator's behalf under a support agreement, both parties accept that the risk described here is inherent to the task.

You agree not to:

• Use the platform to break any law, including data-protection, surveillance or road-transport rules applying to the site.
• Attempt to bypass authentication, permission checks or the audit log, or to reach another tenant's data.
• Deny service to the platform, or interfere with another site's deployment.
• Upload or transmit malicious code through its integrations.
• Use a site's credentials or API keys for anything the operator did not authorise.
• Hold a barrier open as a way of avoiding a charge, or add a tag to a watchlist to harass a person.
• Do anything section 3 rules out: claim ownership of the software or authorship of it, rebrand or white-label it, register or apply to register anything in it, strip a proprietary notice, copy its source outside the licence, or supply it onward as your own.
• Build, buy or commission anything that reproduces the platform from its source, its screens or its documentation.

Each party keeps the other's non-public technical and commercial information — architecture, source, pricing, terms, customer lists, security findings — confidential, uses it only for the deployment, and discloses it only to people who need it and are bound to the same terms, or where the law compels disclosure after notice to the other party.

• Site data is the operator's to protect, and section 8 says so; nothing in this section moves that duty onto NexoPlus Automations.
• What NexoPlus learns at a site — records, plates, images, credentials, the shape of the installation — is used for the engagement in hand and for nothing else, and is not published, sold or shown to another customer.
• Names and marks. The operator may not use the NexoPlus name, logo or marks, or name NexoPlus Automations as a supplier, in marketing, brochures, case studies, tenders, investor decks or client lists without written permission — and may not present the software as its own, which section 3 already rules out.
• The reverse holds too. NexoPlus Automations may say generally that it supplies lane-control and FASTag software; it will not name a site, show its images or publish its details without permission.

This obligation continues for twelve months after the licence ends, longer for anything that is a trade secret, and indefinitely for the ownership position in section 3.

The software is provided "as is" and "as available", without warranty of any kind, express or implied, including fitness for a purpose, title and non-infringement. We do not warrant that a tag will be read, a plate recognised, a barrier actuated correctly, or that any third-party lookup will return a correct answer.

To the maximum extent the law allows, NexoPlus Automations is not liable for indirect, incidental, special, consequential or punitive losses, lost data, lost revenue, business interruption, or the cost of substitute goods or services — even if told they were possible.

Where a commercial agreement sets a liability cap, that cap governs. Nothing here excludes liability that cannot lawfully be excluded. The limits in this section do not work in favour of a party in breach of section 3: a cap written for the ordinary running of a gate is not a price list for the software itself, and no money term in any agreement is taken to license what that section reserves.

These terms may be revised; the date at the top of this page is the version in force. Using the software after a change accepts it.

The licence ends when the commercial agreement does, when NexoPlus Automations withdraws it, or when either party stops using the software. On the end of a licence the operator should stop running the build and delete or return supplied materials, including every copy of the source, the documentation and any screen or export that carries a NexoPlus mark; the operator's own data remains theirs and should be exported before the site is decommissioned. Termination ends the permission to run the software. It transfers nothing, and it leaves ownership exactly where section 3 puts it.

NexoPlus Automations may supply the software to others during and after your term, and no part of your deployment gives you a say in that.

Sections 3, 8, 9, 10, 11, 13, 15, 16, 17, 19 and 20 continue after termination, and section 3 continues without any time limit.

• Force majeure. Neither party is liable for a delay caused by something beyond its reasonable control — internet or telecom failure, an outage of the grid, a third-party service going down, fire, flood, strike, civil disruption, government action. The operator's duty to keep a lane safe and passable does not pause while this clause runs.
• Order of precedence. A signed commercial agreement covering the deployment comes first, these terms come second, and anything in the in-app help is a statement of what the build does rather than a term of supply.
• Entire agreement. These terms, with that agreement, are the whole of the arrangement about the software. No statement in a proposal, a demonstration, an email or a chat window binds NexoPlus Automations unless it is written into the agreement.
• Amendment and waiver. Changes are in writing. A failure to enforce something is not a waiver of it, and one waiver does not become a standing permission.
• Severability. If a court reads one clause as unenforceable, it is trimmed to what is enforceable and the rest of these terms stand.
• Assignment. The operator may not assign or transfer the licence, or hand a deployment to another party, without written consent. NexoPlus Automations may assign it to an affiliate or to a successor of the business.
• Indemnity. The operator holds NexoPlus Automations harmless against claims, losses and costs — including legal fees — arising from the operator's use of the software, the way its site is wired and operated, the data and content at the site, its breach of these terms, and anything section 3 or section 15 rules out.
• Third-party and open-source components. The platform is built on components licensed by their own owners. Those licences are unaffected by these terms: this document grants nothing in them, and they grant nothing that overrides section 3.
• Notices. A notice under these terms goes in writing to the address or mailbox named in the commercial agreement, and is treated as received on delivery or on the next working day after it is sent.
• No third-party beneficiaries. These terms are between NexoPlus Automations and the operator. A resident, visitor, guard or driver who benefits from a working gate acquires no right under them.
• Disputes. Before either party files, they will put the dispute in writing to the other's named contact and spend thirty days trying to settle it at the level of the people who run the engagement. Failing that, section 20 governs.

These terms are governed by the laws of India. The parties submit to the exclusive jurisdiction of the competent courts in Coimbatore, Tamil Nadu, and these terms are construed and enforced there.

That choice holds whatever the site. A deployment in another city, a reseller elsewhere, a foreign-hosted lookup or a dispute about data at a gate several states away does not move the forum; nor does it move the ownership position in section 3.

Questions about these terms, or about a deployment, go to the administrator of the site concerned, or to NexoPlus Automations through the commercial channel that supplied it. This page deliberately prints no address, phone number or mailbox: which one is correct depends on the agreement covering the site.