Skip to content
DecisionNodeDecisionNde
  • Model
  • Inference
  • Benchmarks
  • Examples
  • Docs
  • Pricing
Sign inGet API keyGet API key
  • dnModelTyped answers, calibrated confidence
  • msInferenceOur own stack and GPUs, answers in ms
  • %BenchmarksAccuracy per suite, with intervals
  • exExamplesBuilds you can start from today
  • /v1DocsQuickstart, API reference, recipes
  • $PricingPay per input token, output is free
  • inSign inEmail link or Google, no password
  1. legal
  2. /acceptable use policy
policy

Acceptable Use Policy.

What the Service may never be used for, and the rules for decisions about people.

sections
11
linkable clauses
36
min read
10
version
1.1
last updated
8 October 2026
in effect from
8 October 2026
applies to
Every Customer, Authorised User and End User

Questions: legal@bynn.com

contents0% read

  1. 11. Illegal and harmful activity
  2. 22. Weapons and military use
  3. 33. Decisions about people
  4. 44. Surveillance
  5. 55. Self-harm
  6. 66. Children
  7. 77. Protecting the Service
  8. 88. Customer Products and End Users
  9. 99. The Safety Check
  10. 1010. Enforcement and reporting
  11. 1111. Changes
  1. 11. Illegal and harmful activity
  2. 22. Weapons and military use
  3. 33. Decisions about people
  4. 44. Surveillance
  5. 55. Self-harm
  6. 66. Children
  7. 77. Protecting the Service
  8. 88. Customer Products and End Users
  9. 99. The Safety Check
  10. 1010. Enforcement and reporting
  11. 1111. Changes

This Acceptable Use Policy (the Policy) applies to every person who accesses or uses the Service, including the Customer, its Authorised Users and the End Users of every Customer Product. It forms part of, and is incorporated into, the Terms of Service between Bynn Intelligence, Inc. (Bynn) and the Customer. Capitalised terms not defined in this Policy have the meanings given in the Terms of Service.

The prohibitions in this Policy apply whether or not the Safety Check refuses a request. A request that the Safety Check accepts is not, for that reason, a permitted use.

1Section 1. Illegal and harmful activity

#

The Customer shall not use the Service, and shall not permit any person to use it, to:

1.1

violate Applicable Law, or infringe, misappropriate or violate the intellectual property, privacy, publicity or other rights of any person;

1.2

defraud, deceive or mislead any person, including by phishing, scams, impersonation or other fraudulent schemes;

1.3

present an Output, or a decision made with an Output, as the decision of a natural person where Applicable Law or the circumstances require disclosure that the decision was automated;

1.4

create, distribute or facilitate malware, spam or unsolicited communications;

1.5

threaten, harass or intimidate any person, or promote or incite violence, terrorism, violent extremism or hatred against any person or group; or

1.6

traffic in or exploit persons, or facilitate trade in illegal goods, services or controlled substances.

2Section 2. Weapons and military use

#
2.1

Weapons. The Customer shall not use the Service to design, develop, produce, acquire, stockpile or use weapons intended to injure or kill, including biological, chemical, nuclear and radiological weapons.

Important: Military use prohibited

2.2

Military Use. Military Use is prohibited unless the Customer has signed a Defence Contract Addendum with Bynn, and then only within its terms. Section 4 of the Terms of Service defines what is and is not Military Use.

2.3

Harm to people. The Customer shall not use the Service to choose, rank or target natural persons for physical or lethal harm, except as a signed Defence Contract Addendum expressly permits, and never in a way that Section 4 of the Defence Contract Addendum forbids.

2.4

Vehicles, unmanned aircraft and simulators. The Customer may use the Service, including Sessions, in connection with civilian vehicles, unmanned aircraft, vessels, robots, machines and simulators, such as for survey, inspection, mapping, delivery, agriculture, industrial monitoring, training and games, subject to Section 7.6 of the Terms of Service. The Customer shall not use the Service in connection with any such system:

  1. (a)(a) to aim, arm, trigger, release or deliver any weapon, or any payload intended to injure or kill people or animals or to damage property, or to select or engage any target, except as a signed Defence Contract Addendum expressly permits and never in a way that Section 4 of the Defence Contract Addendum forbids;
  2. (b)(b) to operate the system in breach of aviation, unmanned aircraft, road traffic, maritime or other law, including airspace restrictions, or to evade lawful detection, identification or interception;
  3. (c)(c) to track, follow or monitor any natural person in breach of Section 4; or
  4. (d)(d) as the sole means of controlling a Safety-Critical System.

3Section 3. Decisions about people

#

Important: Qualified review required

3.1

Qualified review of Consequential Decisions. The Customer may use the Service to support Consequential Decisions, including decisions about hiring, credit, housing, insurance, education, benefits, law enforcement and healthcare, only where (a) a Qualified Reviewer reviews each Consequential Decision before it takes effect; and (b) the use complies with Applicable Law, including anti-discrimination, consumer protection, data protection and artificial intelligence law.

3.2

Protected characteristics. The Customer shall not use the Service to treat a person less favourably because of their race, colour, ethnicity, national origin or nationality, religion or belief, sex, gender identity, sexual orientation, disability, pregnancy, caste, immigration status, political opinion, body weight or appearance, or wealth or occupation. The only exception is an attribute on which the decision genuinely depends, where Applicable Law allows it to be considered: for example, income when assessing whether a loan can be repaid, or work experience when hiring.

3.3

Criminal records. The Customer may take a criminal record into account only where Applicable Law allows it for that decision. In a medical decision, a criminal record shall never affect who receives care, what care they receive or in what order; a recent conviction for violence may be considered only for measures that protect the safety of staff.

3.4

Social scoring. The Customer shall not use the Service to evaluate or classify natural persons on the basis of their social behaviour or personal characteristics where the resulting score leads to their detrimental treatment in contexts unrelated to those in which the data was generated, or to treatment that is unjustified or disproportionate.

3.5

Sensitive traits. The Customer shall not use the Service to infer a person's race or ethnic origin, religion, sexual orientation, political opinion, health or a similar sensitive trait, unless the person has given explicit consent or Applicable Law permits it.

4Section 4. Surveillance

#

The Customer shall not use the Service for mass surveillance, or to track, monitor or profile individuals without a lawful basis. This includes (a) recognising the emotions of natural persons in the workplace or in education, except for medical or safety reasons where Applicable Law permits it; and (b) predicting whether a natural person will commit a criminal offence on the basis of profiling or an assessment of their personality traits alone.

5Section 5. Self-harm

#
5.1

Prohibition. The Customer shall not use the Service to help any person harm or kill themselves, including by choosing a method or a dose.

5.2

Detecting risk. Bynn encourages the use of the Service to detect a risk of self-harm and to connect people with help. Requests that ask whether a message indicates such a risk are protective and are not refused on that ground. Where a Customer Product serves people who may be at risk, it shall offer a clear way to reach human help, such as a crisis line or a support team.

6Section 6. Children

#

The Customer shall not use the Service to create, distribute or solicit sexual content involving minors; to groom, exploit, bully or harass minors; or to build products designed to make minors use them compulsively. Bynn reports apparent child sexual abuse material to the competent authorities as the law requires.

7Section 7. Protecting the Service

#

The Customer shall not, and shall not permit any person to:

7.1

reverse engineer, decompile or disassemble the hosted Service, or attempt to extract its model weights, parameters, training data or design;

7.2

scrape or crawl the Service, or access it by automated means other than through the API as the Documentation describes;

7.3

access the Service in any unauthorised way, or access the data of any other customer;

7.4

circumvent, disable or interfere with the Safety Check, rate limits or usage limits, including by splitting, disguising or rephrasing requests;

7.5

disrupt, overload or impair the Service;

7.6

probe, scan or test the vulnerability of the Service without Bynn's prior written permission (security findings may be reported to security@bynn.com); or

7.7

use Outputs to develop, train or improve a model or service that competes with the Service.

Open Models are governed by their own licence.

8Section 8. Customer Products and End Users

#

The Customer is responsible for how its Authorised Users and End Users use the Service through its Account and its Customer Products. The Customer shall maintain reasonable measures, including terms of use and monitoring appropriate to the Customer Product, to prevent them from doing what this Policy forbids, and shall act promptly, including by suspending the person concerned, on becoming aware of a breach.

9Section 9. The Safety Check

#
9.1

Assessment of every request. The Service includes an automated Safety Check. The Safety Check assesses every request to the hosted API, in the same processing as the request's questions, and returns, with each answer, the probability that the request seeks to harm others (including choosing whom to harm by a protected characteristic or targeting people for lethal force) and the probability that it seeks help to harm oneself, as described in the Documentation. Detecting or assessing a risk of harm is never refused on that ground.

9.2

Default flagging. By default, the Safety Check answers and flags every request: it returns its probabilities with the Output, marks a probability above the applicable threshold as flagged, and does not refuse the request. Bynn may at any time apply stricter handling, including refusal, to any API Key or to every API Key where it considers this necessary to prevent harm or to enforce this Policy, and shall describe any change to the default in the Documentation.

9.3

Stricter handling per Customer. Stricter handling, including the refusal of a request, is set per Customer. The Customer may set, for its own API Keys, thresholds and actions stricter than the default, flagging or refusing a request above a threshold it chooses, and Bynn may set them for a Customer under Section 9.2. A refused request returns a documented error instead of Output. The Customer may not switch off the Safety Check or loosen any handling that Bynn applies. Only Bynn may switch off or loosen the assessment of requests that seek to harm others (the Harm and Targeting Component, as defined in the Defence Contract Addendum), and only on the Named Keys of a signed Defence Contract Addendum. The flags and settings do not make any use permitted that this Policy forbids.

9.4

Refusal of a single question. Where the Documentation describes it as available, a refusal may apply to a single question instead of the whole request: the refused question returns a documented refusal answer in place of its Output, and the other questions of the request are answered. On an interface of the API that follows a third party's request format, a refused question is answered in this way; on the other interfaces of the API, it applies where the Customer enables it.

9.5

Circumvention. Repeated attempts to get around the Safety Check are a breach of this Policy.

9.6

No reliance. The Safety Check is a risk-reduction measure. It does not relieve the Customer of any obligation, and Bynn does not warrant that it detects every misuse, that it flags or refuses any particular request, or that it never refuses a legitimate request. Records of refused and flagged requests are kept as described in the Privacy Policy.

9.7

Sessions. In a Session, the Safety Check assesses the request that opens the Session and every Frame, and returns its probabilities with the Output for each Frame. Where a Frame is refused, it returns a documented error instead of Output, and Bynn may end a Session in which Frames are refused. Every rule in this Policy applies to each Frame as it applies to any other request.

9.8

Deployments on the Customer's hardware. The Safety Check runs on the hosted API. A Customer-Hosted Deployment, as defined in Section 3.8 of the Terms of Service, runs without it unless its Order Form or a Defence Contract Addendum requires it. This Policy applies in full to every Customer-Hosted Deployment, and the Customer is solely responsible for preventing every use of it that this Policy forbids.

10Section 10. Enforcement and reporting

#
10.1

Investigation and action. Bynn may investigate any suspected breach of this Policy, including by reviewing Usage Data and, where necessary for the investigation, the relevant Customer Data. Bynn may require information from the Customer, and may suspend or end access, or disable API Keys, with notice where it can reasonably give it.

10.2

Reports to authorities. Bynn reports to the competent authorities where the law requires it, and may do so where it believes in good faith that a report is necessary to prevent imminent harm to any person.

10.3

How to report. Report misuse of the Service to abuse@bynn.com and security issues to security@bynn.com.

10.4

Records of enforcement. Bynn may keep records of requests it refuses or flags, of investigations under this Policy and of the action taken, and may use them to improve the Safety Check and to detect repeated misuse, as the Privacy Policy describes.

11Section 11. Changes

#

Bynn gives at least thirty (30) days' notice of a material change to this Policy, except for a change needed urgently for safety or security, or required by Applicable Law, which applies as soon as Bynn gives notice of it.

← previousTerms of Servicenext →Privacy Policy
DecisionNodeDecisionNde

Add a decision engine with one prompt.

Paste into your coding agent.

start building

Your first decision in minutes.

Make a key, connect your project, branch on a typed answer. Prepaid, no sales call.

  • api all systems normalapi normal
  • output is always freeoutput always free
  • same request, same answersame request, same answer

DecisionNode is built and run by Bynn Intelligence, Inc.

We train the model and serve it on our own GPUs.

hello@bynn.com

product

  • Model
  • Inference
  • Benchmarks
  • Pricing
  • Open models

developers

  • Docs
  • Quickstart
  • Examples
  • Playground
  • Console
  • Status

company

  • Contact
  • Security
  • Report abuse
  • Dedicated
  • Affiliate program

legal

  • Terms
  • Acceptable use
  • Privacy
  • Data processing
  • Defence addendum
  • Cookies
  • Affiliate agreement

compliance

  • SOC 2, SOC 2 report, monitored continuously (opens the trust center in a new tab)
  • ISO 27001:2022, Information security management, certified (opens the trust center in a new tab)
  • ISO/IEC 42001:2023, AI management system, controls mapped to ISO/IEC 42001:2023; compliant, not certified (opens the trust center in a new tab)
  • GDPR, Processor terms under Article 28 in the Data Processing Addendum; a law, not a certification (opens the trust center in a new tab)
  • CCPA, Service-provider terms in the Data Processing Addendum; a law, not a certification (opens the trust center in a new tab)
  • PCI DSS SAQ A, Card data is handled by the payment provider and never stored by us; a self-assessment, not a certification (opens the trust center in a new tab)
  • NIST Cybersecurity Framework, Controls mapped to the NIST CSF; a framework, not a certification (opens the trust center in a new tab)
  • HIPAA (BAA available), Protected health information only under a signed Business Associate Agreement, available on request; HIPAA is not a certification (opens the trust center in a new tab)
  • EU AI Act, Controls mapped to the EU AI Act; a law, not a certification, and no determination that any customer use complies (opens the trust center in a new tab)

© 2026 Bynn Intelligence, Inc.

prices in USD per 1M input tokens