Skip to content

Acceptable use policy

Responsible use for AI, edge, and research systems

Clear operating boundaries for agentic workflows, model-driven automation, quantum research tools, embedded Linux, drones, robotics, and public collaboration.

This policy is operational, not theoretical. If a use case can affect people, safety, critical infrastructure, public systems, or regulated decisions, it needs written authorization and documented controls.

AI agents

Agents must not impersonate, manipulate, bypass controls, automate abuse, or make high-impact decisions without oversight.

Edge systems

Drones, robotics, vehicles, industrial, medical, defence, or public infrastructure deployments require validation and authorization.

Research integrity

Benchmarks, simulations, hardware results, papers, provenance, and reproducibility artifacts must not be fabricated or misrepresented.

01

Policy scope

The AUP covers the website, NowFlow, QFlow Studio, NeuralOS, QANTIS, qmesh, QMANN, managed services, research environments, APIs, integrations, and open-source community channels.

This policy is part of the Terms of Service. A customer agreement, order form, security schedule, or open-source licence may add stricter rules for a specific deployment.

If you use the services through an organization, you are responsible for following both this policy and that organization's acceptable-use, security, compliance, and procurement rules.

02

Prohibited

  • Do not violate laws, regulations, sanctions, export controls, court orders, third-party rights, or contractual obligations.
  • Do not use the services for fraud, money laundering, scams, phishing, identity theft, extortion, harassment, stalking, doxxing, hate, violence, or exploitation.
  • Do not upload, generate, distribute, or facilitate child sexual abuse material, terrorist content, illegal extremist content, or instructions for violent wrongdoing.
  • Do not use the services to impersonate people, misrepresent authority, manipulate users, or hide the origin of harmful content or actions.

03

AI safety

AI systems that can act need controls. Users must not configure agents or workflows to deceive, manipulate, harm, or bypass oversight.

  • Do not build agents that secretly manipulate users, exploit vulnerabilities, or produce materially deceptive content without appropriate disclosure.
  • Do not use AI to generate deepfakes, voice clones, forged credentials, synthetic evidence, or impersonation materials for fraud, harassment, or deception.
  • Do not automate election interference, voter suppression, spam, influence operations, or targeted disinformation campaigns.
  • Do not bypass model, tool, rate, security, or content restrictions; do not prompt systems to reveal secrets, credentials, personal data, or hidden instructions.
  • Do not use the services for social scoring, unlawful discrimination, unauthorized biometric identification, or prohibited profiling.

Any workflow that affects rights, safety, access, eligibility, employment, credit, health, education, housing, public services, or legal position needs clear authority, human review, logging, testing, and appeal paths.

04

Cyber abuse

  • Do not create, deploy, distribute, or improve malware, ransomware, credential theft, botnets, exploit kits, persistence tools, or evasion techniques.
  • Do not conduct unauthorized scanning, scraping, penetration testing, credential stuffing, denial-of-service attacks, or data exfiltration.
  • Do not use generated code, agents, workflows, or integrations to compromise systems or bypass authentication, authorization, rate limits, or security controls.
  • Security research must be authorized, scoped, rate-limited, non-destructive, and reported responsibly to security@neuraparse.com.

05

Privacy

  • Do not collect, process, scrape, infer, or enrich personal data without a lawful basis, required notices, consent where needed, and appropriate safeguards.
  • Do not use the services for unauthorized surveillance, location tracking, biometric tracking, workplace monitoring, or profiling.
  • Do not upload sensitive, regulated, child, biometric, health, financial, defence, export-controlled, or special-category data unless a written agreement authorizes it.
  • Do not attempt to re-identify anonymized data or combine datasets in a way that violates privacy law, customer agreements, or user expectations.

06

Edge and autonomy

NeuralOS, NowFlow, QANTIS, and related tools can support drones, robotics, edge systems, and operational workflows. That does not make every deployment acceptable.

  • Do not use the services for autonomous weapons, lethal targeting, target selection, or offensive military autonomy.
  • Do not deploy to aircraft, drones, vehicles, robots, medical devices, industrial controls, public infrastructure, or defence systems without independent safety validation and written authorization.
  • Do not remove required human supervision, failsafes, emergency stop, fallback, rollback, audit, or operator override controls.
  • Do not use the services to violate aviation, road, workplace safety, medical device, defence procurement, spectrum, export, or local operational rules.
  • Do not connect agents to physical actuators, payment rails, identity systems, or external production systems without scoped permissions, monitoring, and rollback.

07

Research use

  • Do not fabricate benchmark results, hardware access, citations, provenance, reproducibility artifacts, safety claims, or regulatory evidence.
  • Do not use research tooling to misrepresent scientific priority, falsify logs, hide failed runs, or tamper with audit trails.
  • Do not submit third-party confidential data, controlled technical information, or restricted datasets to research tools without permission.
  • Do not use generated papers, diagrams, datasets, or summaries without checking sources, rights, and attribution.

08

Platform integrity

  • Do not overload, probe, disrupt, reverse engineer, or circumvent service limits, billing limits, usage quotas, or technical protections.
  • Do not resell, sublicense, multiplex, share accounts, or provide service-bureau access unless a written agreement allows it.
  • Do not mine cryptocurrency, run unauthorized crawlers, host unrelated workloads, or use the platform as a command-and-control layer.
  • Do not interfere with logs, metering, billing, attribution, telemetry, security monitoring, or abuse-detection systems.

09

Expected controls

Human review

Use approvals, escalation, exception handling, and rollback for actions that can affect people, assets, money, safety, or production systems.

Evidence

Maintain records of prompts, tool calls, data sources, approvals, model versions, deployment packages, and incident handling.

Evaluation

Evaluate outputs, failure modes, bias, latency, safety envelopes, fallback behavior, and model drift before release.

Least privilege

Give agents and users only the credentials, integrations, data scopes, and actions needed for the task.

10

Reporting

Send enough detail for us to identify the issue, affected account, service, timestamp, URL, workflow, repository, device, or integration.

abuse@neuraparse.com

Report policy violations, spam, fraud, impersonation, or misuse.

security@neuraparse.com

Report vulnerabilities, credential exposure, suspicious access, or security incidents.

legal@neuraparse.com

Legal notices, rights requests, or procurement policy questions.

11

Enforcement

  • Warn, rate-limit, suspend, restrict, or terminate accounts, workspaces, keys, integrations, repositories, deployments, or access.
  • Remove, quarantine, disable, or preserve content, logs, workflows, files, outputs, or integrations.
  • Notify workspace administrators, affected customers, providers, regulators, law enforcement, or rights holders where appropriate.
  • Refuse support, onboarding, renewal, or professional services for deployments that create unacceptable risk.
  • Preserve evidence and cooperate with investigations where required by law or necessary to protect systems, people, or property.

13

Updates

We may update this policy as products, AI capabilities, edge deployments, regulatory expectations, or abuse patterns change.

Material updates will be reflected through the last-updated date and, where appropriate, additional customer or workspace notice.

Contact

Include timestamps, workspace IDs, URLs, repository links, workflow names, logs, and screenshots where available.

abuse@neuraparse.com

Policy abuse, impersonation, spam, fraud, or harmful content.

security@neuraparse.com

Security vulnerabilities, suspicious access, or incident reports.

legal@neuraparse.com

Legal notices and formal policy inquiries.