Service-Specific Terms — cloud, hosting, domains and SaaS
These terms supplement our general Terms and Conditions for each hosted service, in line with standard industry practice followed by cloud providers worldwide. Read them before ordering — they allocate responsibilities plainly, especially around data and backups.
Effective date: 8 July 2026 · Entity: Addroit Nexus (Proprietorship — Prabhat), Office No. 12, Second Floor, JD Tower, Kanpur Road, The Piccadilly, LDA Colony, Lucknow, Uttar Pradesh 226012, India · GSTIN 09AOJPP9190B1ZL
1. Provisions common to all hosted services
- Provisioning & accuracy: services are provisioned per the written order form. You must provide accurate KYC, billing and technical contacts and keep them current.
- Credentials: you are responsible for the confidentiality of all credentials issued to you and for all actions taken under them until you notify us of compromise in writing.
- Maintenance: scheduled maintenance is announced at least 48 hours in advance (emergency security maintenance excepted) and excluded from availability calculations.
- Fair use: "unlimited" or unmetered features are subject to fair use consistent with the plan's class; sustained abuse may be shaped, or the plan right-sized after notice.
- Suspension: we may suspend for non-payment, AUP breach, security emergencies, or lawful order — immediately where third parties or the platform are at risk, otherwise after notice.
- Your data: remains yours. We access it only to operate, support and secure the service, or as law requires — per the Privacy Policy.
2. Backups and data responsibility — read this twice
Consistent with industry practice across cloud providers: you are solely responsible for maintaining independent backups of your data, on media or services separate from the service in question, unless you have purchased a managed backup plan in writing. Snapshots, RAID, replication and similar platform features improve resilience but are not backups and are not warranted to survive every failure mode. Where a managed backup plan is purchased, our obligation is limited to operating the agreed schedule and retention with reasonable skill — restore points, not guarantees of zero loss, are the deliverable. We strongly recommend the 3-2-1 pattern and periodic restore testing, and we will help you set it up.
3. Cloud servers (VPS, bare metal, edge cloud)
- With root/administrator access, you are responsible for OS hardening, patching, application security, firewall configuration and what your instance sends to the internet.
- Compute, RAM and disk are dedicated or fairly shared per plan class; sustained extraction workloads (e.g., crypto-mining) require a written arrangement.
- IP addresses remain allocated to us; abusive traffic that damages IP reputation may lead to filtering, re-assignment or suspension under the AUP.
- On termination, instance data is irretrievably deleted after the 15-day export window in the general Terms.
4. Cloud storage (object, archive, backup targets)
- Durability figures are engineering design targets (multi-copy replication with integrity checks), not insurance. For irreplaceable data, keep an additional independent copy.
- Ransomware defence features — versioning, object lock/immutability, separate credentials — must be enabled by you on the buckets that matter; we can configure them on request.
- Deletion (including lifecycle rules you configure) is permanent once processed; we cannot recover objects you delete.
- Egress allowances and rates are per the published schedule; archive-tier retrievals may take longer by design.
5. Web and application hosting
- You are responsible for keeping your CMS, plugins, themes and application dependencies updated; compromises originating in outdated or pirated software are outside our responsibility, and cleanup is a chargeable service.
- Shared-platform limits (processes, inodes, mail rate) protect all tenants and are enforced automatically.
- Outbound email from hosting follows the AUP strictly; transactional volumes belong on the Transactional Mail service.
6. Domain registration and management
- Domains are registered through accredited registrars and are governed by the registry's and ICANN's/NIXI's policies (including UDRP/INDRP dispute rules), which bind you as registrant.
- You must keep registrant contact details accurate; failure can result in suspension by the registry — outside our control.
- Renewals: reminders are sent to your registered email, but the obligation to renew on time is yours. Expired domains enter registry-defined grace/redemption phases with escalating third-party fees, and can be permanently lost — we accept no liability for non-renewal, mistyped names, or registry/registrar actions.
- Registration, renewal and redemption fees are non-refundable once submitted to the registry. Transfers-out are supported per policy (auth codes provided promptly when dues are clear).
7. SaaS suites (shop apps, gig platforms, field service, retail, travel)
- Billing: flat monthly subscription per plan, plus a flat ₹3 per-order/booking service fee covering order notifications (1 email, up to 2 SMS, up to 2 WhatsApp utility messages, in-app push) and per-transaction infrastructure. Each plan includes 33% of the month's orders free of this fee; the balance is deducted from your prepaid wallet.
- Wallet: top-ups are prepaid, carry GST invoices, never lapse while the subscription is active, and any unused balance is refundable on termination (less payment-gateway costs) within 30 days of written request.
- Third-party dependencies: SMS (telecom DLT), WhatsApp (Meta), email and payment gateways are third-party platforms; their outages, policy changes, template rejections or price revisions are outside our control — material pass-through price changes are notified at least 15 days ahead.
- Taxes: GST at 18% applies on subscriptions, setup, per-order fees and top-ups. Business customers may deduct TDS as applicable against a valid certificate.
- Your customers' data in the suite belongs to you; we process it on your instructions (DPDP processor role) and export it to you in standard formats on exit.
8. Disclaimers and limitation of liability
To the maximum extent permitted by applicable law, services are provided "as is" and "as available". Without limiting the general Terms, and in line with standard positions taken across the cloud industry, Addroit Nexus accepts no liability for: loss, corruption or unavailability of data from any cause (including hardware failure, software defects, or failed restores where independent backups were not maintained); the consequences of ransomware, malware, hacking, phishing of your credentials, or other unauthorised access occurring despite commercially reasonable safeguards; natural disasters, fire, flood, earthquake, epidemic, war, riot, sabotage or other force majeure; failures of electricity grids, telecom carriers, upstream data centers, registries, payment gateways, Meta/WhatsApp, SMS carriers or other third-party providers; or losses caused by your configuration, your software, or your users. Our total aggregate liability for any service is capped at the fees you paid for that service in the three (3) months preceding the claim; SLA service credits are the sole and exclusive remedy for availability shortfalls. Nothing on this page excludes liability that cannot be excluded under Indian law.
9. Your indemnity
You agree to indemnify and hold harmless Addroit Nexus, its proprietor and personnel against claims, penalties and costs arising from your content, your use of the services in breach of these terms or law, claims by your end-customers, or your failure to maintain backups — as detailed in the Master Service Agreement, which includes a signable Indemnity-cum-Undertaking annexure for execution on stamp paper or digitally.
10. Governing law, jurisdiction and disputes
These terms and every service order are governed by the laws of India. Disputes are first escalated for good-faith resolution; failing that, they are referred to arbitration by a sole arbitrator under the Arbitration and Conciliation Act, 1996, with seat and venue at Lucknow, Uttar Pradesh, proceedings in English. Subject to the above, the courts at Lucknow, Uttar Pradesh, India, have exclusive jurisdiction. Electronic acceptance of these terms (click-through, email or mobile OTP verification with audit trail) constitutes a valid, binding contract under the Information Technology Act, 2000 and the Indian Contract Act, 1872.
Have a project in mind? Let's talk.
Tell us what you are building or what is slowing you down — we reply with a clear, honest plan.
- Response within one business day — usually much faster
- You talk to engineers, not a sales script
- Your details stay with us — see our Privacy Policy