Legal

Acceptable Use Policy

Rules, restrictions, operational-security requirements, lawful-use obligations, and infrastructure-protection standards governing the use of Raksham Labs products, firmware, software, APIs, telemetry systems, communication systems, embedded electronics, technical infrastructure, and related services.

Last updated: 2026-05-11

1. Purpose

This Acceptable Use Policy ("AUP") defines permitted and prohibited uses of Raksham Labs:

  • products;
  • firmware;
  • software;
  • APIs;
  • telemetry systems;
  • communication systems;
  • GNSS-related systems;
  • embedded electronics;
  • dashboards;
  • operational services;
  • technical documentation;
  • infrastructure systems.

Raksham Labs products and services are intended solely for lawful, authorised, compliant, responsible, and ethical use.

This Policy operates together with:

2. Scope

This Policy applies to:

  • customers;
  • distributors;
  • resellers;
  • integrators;
  • commercial users;
  • institutional users;
  • research organisations;
  • any person or entity accessing or using Raksham Labs products or services.

The term "Products" includes:

  • hardware;
  • firmware;
  • software;
  • APIs;
  • telemetry systems;
  • communication modules;
  • embedded electronics;
  • technical systems;
  • operational information;
  • dashboards;
  • infrastructure systems;
  • documentation.

3. Lawful use requirement

Products may only be used in compliance with applicable:

  • laws;
  • export regulations;
  • telecom regulations;
  • aviation rules;
  • cybersecurity obligations;
  • privacy laws;
  • operational-security requirements;
  • radio-frequency regulations.

Customers are solely responsible for ensuring that:

  • deployment;
  • testing;
  • integration;
  • operation;
  • resale;
  • redistribution;
  • technical usage

remain lawful within their jurisdiction.

Customers assume responsibility for:

  • operational deployment decisions;
  • infrastructure integration decisions;
  • operational-risk assessment;
  • deployment validation.

Products may require independent operational-risk assessment, verification, testing, or regulatory review before deployment.

4. Prohibited activities

Customers may not use Products for:

  • unlawful surveillance;
  • unlawful interception of communications;
  • cybercrime;
  • hacking activity;
  • malware deployment;
  • credential theft;
  • denial-of-service activity;
  • privacy violations;
  • unlawful remote monitoring;
  • unlawful tracking;
  • sanctions evasion;
  • export-control violations;
  • unlawful intelligence gathering;
  • prohibited telecommunications activity;
  • unauthorised access to systems or networks;
  • harassment;
  • fraudulent activity;
  • unlawful weapons development;
  • prohibited military activity;
  • unlawful operational disruption;
  • unlawful data harvesting;
  • prohibited RF operation;
  • unlawful signal interference;
  • unlawful automation activity.

Products may not be used to violate:

  • intellectual-property rights;
  • privacy rights;
  • telecom regulations;
  • aviation laws;
  • cybersecurity laws;
  • export-control restrictions;
  • radio-frequency regulations.

Products and services may not be used for:

  • unlawful competitive misuse;
  • abusive infrastructure interaction;
  • unauthorised stress testing;
  • unauthorised load testing;
  • abusive automated interaction.

5. Surveillance, privacy, and data-use restrictions

Products may not be used for:

  • unlawful surveillance;
  • unlawful recording;
  • unauthorised monitoring;
  • covert interception;
  • privacy-invasive activity;
  • unlawful data collection;
  • unlawful data harvesting.

Customers remain solely responsible for compliance with applicable:

  • privacy laws;
  • surveillance restrictions;
  • telecom regulations;
  • lawful-consent requirements;
  • data-protection obligations.

Raksham Labs does not authorise or endorse unlawful monitoring, unlawful interception, unlawful data collection, privacy violations, or prohibited surveillance activity.

Customers remain responsible for operational data generated during deployment or integration activity.

6. Cybersecurity and operational-security restrictions

Customers may not:

  • attempt to bypass security controls;
  • compromise operational-security protections;
  • interfere with firmware-integrity mechanisms;
  • misuse firmware-update systems;
  • distribute malicious code;
  • exploit vulnerabilities for unlawful purposes;
  • interfere with network operations;
  • conduct unauthorised penetration testing;
  • conduct unauthorised vulnerability testing;
  • interfere with infrastructure availability;
  • abuse APIs or telemetry systems;
  • engage in cyber attacks or intrusion activity.

Products may not be used in ways that:

  • threaten operational security;
  • compromise infrastructure;
  • disrupt networks;
  • interfere with service availability;
  • violate cybersecurity obligations.

Excessive automated requests, abusive technical activity, excessive resource consumption, abusive API usage, or operational misuse of:

  • APIs;
  • telemetry systems;
  • dashboards;
  • infrastructure systems

is prohibited.

Users are responsible for safeguarding:

  • credentials;
  • authentication tokens;
  • API keys;
  • access systems;
  • operational access credentials.

Users remain responsible for securing their:

  • operational environments;
  • integration systems;
  • deployment infrastructure;
  • local networks.

Security controls, infrastructure protections, APIs, operational safeguards, or technical restrictions may evolve without notice.

No system can guarantee absolute operational security.

Certain services, APIs, dashboards, or telemetry systems may depend on third-party infrastructure providers or communication systems.

Vulnerability reports and responsible disclosure should be submitted in accordance with our Security & Responsible Disclosure Policy.

7. Export-control and sanctions compliance

Products may not be:

  • exported;
  • re-exported;
  • transferred;
  • redistributed;
  • supplied

in violation of:

  • export-control laws;
  • sanctions regulations;
  • customs restrictions;
  • operational-security requirements.

Customers may not:

  • circumvent export restrictions;
  • evade sanctions controls;
  • conceal end users;
  • obscure end-use activity;
  • engage in unlawful export diversion.

Additional obligations are described in the Export Compliance Policy.

8. High-risk and regulated deployment

Unless expressly stated otherwise in writing, Products are not represented as:

  • military-certified;
  • aviation-certified;
  • safety-critical certified;
  • medical-device certified;
  • life-support certified;
  • approved for regulated-security deployment.

Products may not be deployed in:

  • safety-critical systems;
  • life-support environments;
  • aviation-certified systems;
  • regulated infrastructure

without independent:

  • validation;
  • testing;
  • verification;
  • regulatory approval.

Autonomous deployment, remote operation, telemetry deployment, RF operation, or operational automation remains subject to applicable law and regulatory restrictions.

Certain operational capabilities, APIs, telemetry systems, communication features, dashboards, or firmware functionality may not be available in all jurisdictions.

9. Compatibility and integration responsibility

Customers are responsible for:

  • integration;
  • calibration;
  • configuration;
  • compatibility verification;
  • operational testing;
  • deployment validation.

Unless expressly stated otherwise, compatibility with:

  • third-party hardware;
  • firmware stacks;
  • APIs;
  • software environments;
  • flight controllers;
  • ESCs;
  • communication systems;
  • telemetry systems

is not guaranteed.

Third-party platforms, APIs, communication providers, infrastructure systems, software ecosystems, or operational services may impose additional:

  • requirements;
  • restrictions;
  • operational limitations;
  • compliance obligations.

10. Experimental and beta functionality

Certain:

  • firmware;
  • software;
  • APIs;
  • telemetry systems;
  • dashboards;
  • operational systems;
  • technical features

may be released in:

  • beta;
  • experimental;
  • pre-release;
  • evaluation

form.

Such functionality may contain:

  • instability;
  • errors;
  • incomplete features;
  • compatibility limitations;
  • operational inconsistencies.

Customers assume associated:

  • operational risks;
  • deployment risks;
  • integration risks;
  • compatibility risks.

Features, APIs, dashboards, firmware functionality, telemetry systems, or operational capabilities may be:

  • modified;
  • deprecated;
  • restricted;
  • discontinued

over time.

11. Technical restrictions and prohibited modifications

Customers may not:

  • tamper with protected systems unlawfully;
  • remove security mechanisms unlawfully;
  • bypass operational restrictions;
  • misuse APIs or technical systems;
  • interfere with firmware protections;
  • misuse communication systems;
  • engage in prohibited modification activity.

Unauthorised modification, improper installation, prohibited integration activity, operational misuse, or unauthorised reverse engineering may:

  • void replacement eligibility;
  • void warranty eligibility;
  • restrict technical support;
  • result in account restrictions;
  • result in service suspension.

12. AI-assisted systems and operational analytics

Certain:

  • compliance systems;
  • fraud-prevention systems;
  • operational analytics;
  • telemetry systems;
  • infrastructure monitoring systems;
  • security-review systems

may involve:

  • automated systems;
  • algorithmic review;
  • AI-assisted analysis.

Such systems are intended to support lawful operational decision-making and are not intended for:

  • unlawful automated profiling;
  • prohibited surveillance activity;
  • unlawful monitoring.

AI-assisted operational systems may operate with human oversight where operationally appropriate.

13. Operational monitoring and enforcement

Raksham Labs reserves the right to:

  • investigate suspected misuse;
  • review operational activity;
  • log operational activity;
  • restrict technical access;
  • suspend accounts;
  • suspend operational access;
  • suspend APIs;
  • suspend telemetry services;
  • suspend dashboards;
  • suspend services;
  • deny support;
  • terminate access;
  • refuse future transactions

where:

  • compliance concerns;
  • cybersecurity risks;
  • operational-security concerns;
  • export-control concerns;
  • abusive operational behaviour;
  • unlawful activity

are identified.

Operational access, dashboards, APIs, telemetry systems, firmware services, infrastructure systems, or technical services may be restricted without prior notice where:

  • cybersecurity concerns;
  • security risks;
  • operational concerns;
  • compliance concerns

arise.

Enforcement actions may be taken at Raksham Labs' reasonable discretion.

Raksham Labs may cooperate with lawful:

  • governmental requests;
  • cybersecurity investigations;
  • export-control enforcement actions;
  • regulatory inquiries;
  • judicial processes

where legally required.

Users may be required to cooperate with lawful:

  • compliance inquiries;
  • operational investigations;
  • cybersecurity investigations;
  • regulatory review;
  • export-control review.

14. No guarantee of uninterrupted operation

Raksham Labs does not guarantee:

  • uninterrupted availability;
  • continuous firmware support;
  • continuous API availability;
  • uninterrupted telemetry access;
  • permanent technical compatibility;
  • uninterrupted operational functionality.

Operational characteristics, firmware behaviour, APIs, dashboards, telemetry systems, infrastructure systems, compatibility behaviour, operational functionality, or integration characteristics may evolve over time.

Raksham Labs does not guarantee continuous availability of:

  • products;
  • firmware versions;
  • APIs;
  • dashboards;
  • technical systems;
  • operational services;
  • telemetry services;
  • technical support.

Access rights, operational availability, or technical capabilities may vary by:

  • region;
  • product type;
  • compliance status;
  • operational constraints.

15. Limitation of liability

Raksham Labs shall not be liable for:

  • unlawful deployment;
  • operational misuse;
  • cybersecurity incidents caused by customer activity;
  • export-control violations;
  • operational interruption;
  • mission loss;
  • regulatory action;
  • third-party misuse;
  • unlawful integration activity;
  • privacy-law violations;
  • prohibited RF operation;
  • infrastructure misuse.

16. No waiver, severability, and survival

Failure by Raksham Labs to enforce any provision of this Policy shall not constitute waiver of any rights or provisions.

If any provision of this Policy is determined unenforceable, remaining provisions remain in full force and effect.

Obligations relating to:

  • lawful use;
  • export compliance;
  • operational-security requirements;
  • confidentiality;
  • liability limitations;
  • cybersecurity obligations

shall survive termination where applicable.

17. Relationship with other policies

This Policy operates together with:

Nothing in this Policy creates any:

  • partnership;
  • agency relationship;
  • representative relationship;
  • joint venture

between Raksham Labs and any user or third party.

18. Changes to this Policy

Raksham Labs may update this Acceptable Use Policy periodically to reflect:

  • operational changes;
  • infrastructure developments;
  • cybersecurity requirements;
  • export obligations;
  • legal developments;
  • product evolution.

Updated versions become effective upon publication.

English-language versions of this Policy shall control in case of interpretation inconsistency or translation conflict.

19. Governing law and jurisdiction

This Policy is governed by the laws of India.

Subject to applicable law, disputes relating to this Policy shall fall under the jurisdiction of courts located in Prayagraj, Uttar Pradesh, India.

20. Contact

General enquiries: hello@rakshamlabs.com or through the contact page.

For security-related concerns and responsible disclosure, see our Security & Responsible Disclosure Policy. For export-compliance enquiries, see our Export Compliance Policy.