Acceptable Use Policy

Last updated: June 28, 2026  ·  Effective immediately

1. The core rule

Use GridShare lawfully, and do not use it — or let anyone use it through your account — to harm others, break the law, or abuse the platform, our Providers, or other users. GridShare runs on hardware owned by independent Providers; treating that hardware and the network with care is a condition of using the service.

2. Prohibited content and activities

You must not use GridShare to create, store, train on, transmit, or distribute anything that:

• Is illegal under Indian law or the law applicable to you
• Involves child sexual abuse material (CSAM) or the sexual exploitation of minors — this is reported to law enforcement without exception
• Constitutes malware, ransomware, spyware, exploits, botnets, or tools whose primary purpose is to gain unauthorised access to systems
• Is used to attack, disrupt, overload, or gain unauthorised access to any network, system, or account (including DoS/DDoS, port scanning, credential stuffing, or brute-forcing) — whether the target is GridShare, a Provider, or a third party
• Infringes the intellectual property, privacy, or other rights of others, or misappropriates trade secrets
• Is fraudulent, deceptive, or facilitates fraud, phishing, scams, or financial crime (including money laundering)
• Generates or distributes spam, bulk unsolicited messaging, or content designed to manipulate or deceive at scale (including non-consensual deepfakes and disinformation campaigns)
• Harasses, threatens, defames, or incites violence or hatred against any person or group
• Unlawfully processes personal data, or processes sensitive personal data without a lawful basis and appropriate safeguards

3. Platform and resource abuse

• Do not attempt to circumvent billing, metering, quotas, the IP-masking proxy, or any security or access control
• Do not run workloads designed to damage, destabilise, or excessively wear Provider hardware, or to evade GridShare's monitoring
• Do not create multiple accounts to abuse trial credits, referral bonuses, or rate limits, or to evade a suspension
• Do not resell, sublicense, or expose GridShare compute to third parties in a way that masks the actual user from us, where doing so defeats abuse controls
• Do not probe, scan, or test the vulnerability of the Platform without our prior written consent (responsible disclosure to security@gridshare.in is welcome)

4. Responsibilities for Providers

• Only share hardware you own or are authorised to operate, and ensure your electricity and internet use complies with your agreements
• Do not attempt to access, copy, tamper with, or interfere with Buyer workloads or data running on your machine
• Do not misrepresent your hardware's specifications or manipulate benchmarks or reliability metrics

5. Sensitive workloads

6. Enforcement

If we reasonably believe you have violated this AUP, we may — with or without notice, depending on severity — suspend or terminate your account or any workload, remove or disable access to content, withhold or reverse credits or payouts associated with the violation, and retain or disclose information as required to comply with law or protect GridShare, our users, or the public. Serious violations (such as CSAM, attacks on third parties, or fraud) are reported to the appropriate authorities, including CERT-In where applicable.

We aim to act proportionately and, where practical and lawful, to give you a chance to remedy a violation. Nothing here limits any other rights or remedies available to us under the Terms of Service or applicable law.

7. Reporting abuse

If you encounter content or activity on GridShare that violates this AUP, or you believe content infringes your rights, report it to abuse@gridshare.in (or support@gridshare.in). Include enough detail for us to locate and assess the issue. We review reports promptly and act on verified violations.

8. Changes to this Policy

We may update this AUP as the Platform and the legal landscape evolve. For material changes, we will provide notice as described in our Terms of Service. The “last updated” date above always reflects the current version; continued use after the effective date constitutes acceptance.