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. /privacy policy
notice

Privacy Policy.

What personal data Bynn collects, why, how long it is kept, and the rights you have.

sections
13
linkable clauses
28
min read
20
version
1.5
last updated
14 October 2026
in effect from
16 October 2026
applies to
Customers, Authorised Users and website visitors

Questions: legal@bynn.com

contents0% read

  1. 11. Who we are and the scope of this Policy
  2. 22. Personal Data we collect
  3. 33. How we use Personal Data and our legal bases
  4. 44. Model improvement
  5. 55. Retention
  6. 66. Security
  7. 77. Disclosure and Sub-processors
  8. 88. International transfers
  9. 99. Your rights
  10. 1010. Children
  11. 1111. Cookies and similar technologies
  12. 1212. Changes to this Policy
  13. 1313. Contact
  1. 11. Who we are and the scope of this Policy
  2. 22. Personal Data we collect
  3. 33. How we use Personal Data and our legal bases
  4. 44. Model improvement
  5. 55. Retention
  6. 66. Security
  7. 77. Disclosure and Sub-processors
  8. 88. International transfers
  9. 99. Your rights
  10. 1010. Children
  11. 1111. Cookies and similar technologies
  12. 1212. Changes to this Policy
  13. 1313. Contact

This Privacy Policy (the Policy) explains how Bynn Intelligence, Inc. (Bynn, we or us) collects, uses, discloses and otherwise processes Personal Data in connection with the DecisionNode Service and the website at decisionnode.com, including the Console, the playground and the Documentation (the Website), and the rights available to the individuals concerned. Capitalised terms not defined in this Policy have the meanings given in the Terms of Service.

The commitments in brief

  • You control model improvement. Input and Output may be used to improve the Models and the Safety Check unless the Customer opts out, and never where zero retention, an Order Form or a Defence Contract Addendum applies.

  • Deleted by default. Input and Output are deleted thirty (30) days after each request, and are not stored at all where zero retention applies, except those of a Batch Job, kept as Section 5.9 describes.

  • Not sold. Bynn does not sell Personal Data or share it for targeted advertising.

  • Your rights. Access, correction, deletion, portability and objection, by email to privacy@bynn.com.

1Section 1. Who we are and the scope of this Policy

#
1.1

Bynn as Controller. Bynn is the Controller of the Personal Data in Account Data, Usage Data, safety records, communications with Bynn, and data collected through the Website. Bynn Intelligence, Inc. is a Delaware corporation with its principal place of business at 2261 Market Street STE 22340, San Francisco, CA 94114, United States.

1.2

Bynn as Processor of Customer Data. When a Customer submits Input containing Personal Data, Bynn processes that Personal Data, and the Output derived from it, as a Processor on behalf of the Customer, which is the Controller, under the Data Processing Addendum. This Policy describes Bynn's practices for that data for transparency, but the Customer's own privacy notice governs it. An individual whose Personal Data a Customer has submitted should contact that Customer; Bynn forwards any request it receives about such data to the Customer concerned.

1.3

Business service. The Service is provided to businesses and is intended for use by persons aged eighteen (18) or older acting on behalf of an organisation.

1.4

Biometric identification and Collections. Where a Customer uses a Biometric Booster under the Terms of Service, Bynn derives a face template from each picture the booster reads and compares it with the Collection the request names, as a Processor for the Customer. Where a Customer enrolls a face in one of its own Collections, Bynn derives and stores its face template, with the reference identifier, label and Item Metadata the Customer gives it, as a Processor for the Customer, and does not keep the picture; a match returns that label and Item Metadata to the Customer and gives them to the Models as evidence for the decision the request asks. Bynn is the Controller of the Public Collections, which it maintains solely so that these comparisons can be made: the Celebrities Collection, which holds for each public figure a face template, a name and a reference identifier, and the Wanted Persons Collection, which holds, for each person whom a public authority has asked by a public notice to be located, a face template, the person's name, the charges and the issuing country as the notice states them, and a reference identifier. A match in the Celebrities Collection returns the public figure's name; a match in the Wanted Persons Collection returns the name, the charges and the issuing country with the reference identifier, and only to a Customer for whose workspace Bynn has enabled that collection under Section 6.9 of the Terms of Service.

2Section 2. Personal Data we collect

#
2.1

Categories. Bynn collects the following categories of Personal Data:

Categories of Personal Data Bynn collects
CategoryWhat it includesSource
Account Data: profileName, business email address, organisation, role, workspace membership and settings, and sign-in records. Where you sign in with Google, Google provides your name, email address and profile picture under its own privacy policy; Bynn stores no password.You, the Customer that invites you, or your sign-in provider
Account Data: billingBilling contact, billing address, tax identifiers and transaction records. Card details are collected by Bynn's payment processor; Bynn receives only limited details such as card brand, last four digits and expiry date.You and Bynn's payment processor
Customer DataInput (state, questions, criteria, instructions, images and the Frames of a Session) and Output. It contains Personal Data only if the Customer chooses to include it, for example where an image or a camera Frame shows a person.The Customer, through the API
Usage DataRequest identifiers, Session identifiers, Frame sequence numbers, timestamps, token counts, latency, model identifiers, error codes, API Key identifiers, and the IP address and user agent of each request.Generated automatically
Safety recordsRecords of requests refused or flagged by the Safety Check and, under a Defence Contract Addendum, of requests served with the Safety Check switched off: the API Key, the time, a cryptographic hash of the request and the check's probability.Generated automatically
Biometric dataWhere a Customer uses a Biometric Booster or Collections: the face templates derived from the pictures it submits, the matches they return, and the Face Items it enrolls in its own Collections (a face template, the Customer's reference identifier and label, and the Item Metadata the Customer sets, up to twenty fields and 4 KB an item). Bynn processes them for the Customer as a Processor, keeps no picture and no template of a search after its request, holds Face Items with their Item Metadata until they are deleted, and never uses any of them to improve the Models. The Customer decides what Item Metadata contains, and may not put special categories of personal data in it beyond what its purpose requires and the law permits.The Customer, through the API or the Console
Celebrities CollectionFor each public figure: a face template, the public figure's name and a reference identifier.Pictures of public figures that are publicly available
Wanted Persons CollectionFor each person whom a public authority has asked to be located: a face template, the person's name, the charges and the issuing country, as the public notice states them, and a reference identifier. These include personal data relating to criminal offences. The Service returns them only to Customers for whose workspace Bynn has enabled the collection.Public notices by which public authorities ask for help in locating a person
CommunicationsSupport requests, feedback, and reports of abuse or security issues, with their contents and contact details.You
Website dataDevice and browser information, pages viewed, referring page, IP address, your cookie choices, the browser storage described in the Cookies Policy, and error reports from the Website and the Console, which hold the page, the browser and the error.Generated automatically
Referral dataIf you open the Website through a referral link: the link's code, when you first opened it and any campaign tags on it, kept in the Referral cookie, and, if you then open an Account, the fact that it was referred and by which code. Clicks on a referral link are counted per day and campaign tag, with a salted hash of the visitor's IP address used only to count each visitor once a day.Generated automatically
Partner dataIf you join the referral program under the Affiliate Program Agreement: your enrollment and the agreement version you accepted, your referral code, the clicks and referrals credited to you, your commission and payouts, and your payout account's identifier, country and status. Bynn's payment processor collects your identity, bank and tax details for that account under its own terms; Bynn does not receive them.You, generated automatically, and Bynn's payment processor
Category
Account Data: profile
What it includes
Name, business email address, organisation, role, workspace membership and settings, and sign-in records. Where you sign in with Google, Google provides your name, email address and profile picture under its own privacy policy; Bynn stores no password.
Source
You, the Customer that invites you, or your sign-in provider
Category
Account Data: billing
What it includes
Billing contact, billing address, tax identifiers and transaction records. Card details are collected by Bynn's payment processor; Bynn receives only limited details such as card brand, last four digits and expiry date.
Source
You and Bynn's payment processor
Category
Customer Data
What it includes
Input (state, questions, criteria, instructions, images and the Frames of a Session) and Output. It contains Personal Data only if the Customer chooses to include it, for example where an image or a camera Frame shows a person.
Source
The Customer, through the API
Category
Usage Data
What it includes
Request identifiers, Session identifiers, Frame sequence numbers, timestamps, token counts, latency, model identifiers, error codes, API Key identifiers, and the IP address and user agent of each request.
Source
Generated automatically
Category
Safety records
What it includes
Records of requests refused or flagged by the Safety Check and, under a Defence Contract Addendum, of requests served with the Safety Check switched off: the API Key, the time, a cryptographic hash of the request and the check's probability.
Source
Generated automatically
Category
Biometric data
What it includes
Where a Customer uses a Biometric Booster or Collections: the face templates derived from the pictures it submits, the matches they return, and the Face Items it enrolls in its own Collections (a face template, the Customer's reference identifier and label, and the Item Metadata the Customer sets, up to twenty fields and 4 KB an item). Bynn processes them for the Customer as a Processor, keeps no picture and no template of a search after its request, holds Face Items with their Item Metadata until they are deleted, and never uses any of them to improve the Models. The Customer decides what Item Metadata contains, and may not put special categories of personal data in it beyond what its purpose requires and the law permits.
Source
The Customer, through the API or the Console
Category
Celebrities Collection
What it includes
For each public figure: a face template, the public figure's name and a reference identifier.
Source
Pictures of public figures that are publicly available
Category
Wanted Persons Collection
What it includes
For each person whom a public authority has asked to be located: a face template, the person's name, the charges and the issuing country, as the public notice states them, and a reference identifier. These include personal data relating to criminal offences. The Service returns them only to Customers for whose workspace Bynn has enabled the collection.
Source
Public notices by which public authorities ask for help in locating a person
Category
Communications
What it includes
Support requests, feedback, and reports of abuse or security issues, with their contents and contact details.
Source
You
Category
Website data
What it includes
Device and browser information, pages viewed, referring page, IP address, your cookie choices, the browser storage described in the Cookies Policy, and error reports from the Website and the Console, which hold the page, the browser and the error.
Source
Generated automatically
Category
Referral data
What it includes
If you open the Website through a referral link: the link's code, when you first opened it and any campaign tags on it, kept in the Referral cookie, and, if you then open an Account, the fact that it was referred and by which code. Clicks on a referral link are counted per day and campaign tag, with a salted hash of the visitor's IP address used only to count each visitor once a day.
Source
Generated automatically
Category
Partner data
What it includes
If you join the referral program under the Affiliate Program Agreement: your enrollment and the agreement version you accepted, your referral code, the clicks and referrals credited to you, your commission and payouts, and your payout account's identifier, country and status. Bynn's payment processor collects your identity, bank and tax details for that account under its own terms; Bynn does not receive them.
Source
You, generated automatically, and Bynn's payment processor
Categories of Personal Data Bynn collects

3Section 3. How we use Personal Data and our legal bases

#
3.1

Purposes and legal bases. Bynn uses Personal Data for the following purposes. Where the GDPR or the UK GDPR applies, Bynn relies on the legal basis stated for each purpose.

Purposes of processing and their legal bases
PurposeData usedLegal basis
Providing the Service: processing API requests and returning OutputsAccount Data, Customer Data, Usage DataPerformance of the contract with the Customer (Article 6(1)(b)); for Customer Data, the Customer's instructions as Controller
Administering Accounts, authentication and supportAccount Data, communicationsPerformance of the contract; Bynn's legitimate interest in supporting its customers (Article 6(1)(f))
Billing, payment, tax and accountingAccount Data (billing), Usage DataPerformance of the contract; compliance with legal obligations (Article 6(1)(c))
Security, abuse prevention, the Safety Check and enforcement of the Terms of Service and the Acceptable Use PolicyUsage Data, safety records and, where an investigation requires it, Customer DataBynn's legitimate interest in protecting the Service, its customers and the public; compliance with legal obligations
Service notices, such as changes to terms, security notices and incident notificationsAccount DataPerformance of the contract; compliance with legal obligations
Operating, analysing and improving the ServiceUsage Data, Website data, aggregated or de-identified dataBynn's legitimate interest in running and developing its Service
Developing, training, evaluating and improving the Models and the Safety CheckCustomer Data where the Customer has not opted out (Section 4), never biometric data, safety recordsFor Customer Data, the Customer's instructions as Controller under Section 8.4 of the Terms of Service; for safety records, Bynn's legitimate interest in developing accurate and safe Models, with measures to remove or reduce Personal Data before use
Comparing the faces in a Customer's pictures with a Collection, and holding the Face Items a Customer enrollsBiometric dataThe Customer's instructions as Controller under the Data Processing Addendum; the Customer is responsible for the lawful basis and the condition for processing biometric data that its use relies on, including the consent of each person whose face it enrolls where the law requires it (Section 6.9 and Section 6.10 of the Terms of Service)
Maintaining the Celebrities CollectionCelebrities CollectionBynn's legitimate interest in letting Customers recognise public figures in pictures, limited to persons in their public role, and the condition for processing biometric data that Applicable Law provides
Maintaining the Wanted Persons CollectionWanted Persons CollectionThe substantial public interest that Applicable Law recognises in locating persons whom public authorities seek, under the conditions that law sets; for the name, the charges and the issuing country, which relate to criminal offences, processing that Applicable Law authorises with appropriate safeguards (Article 10 of the GDPR): only the details the public authority published for this purpose, used only to answer the searches of Customers that are government agencies or public authorities, or organisations with the approval and the legal right to process such data under the law that applies to them, whom Bynn has verified and enabled for law enforcement or comparable purposes, kept no longer than the notice stands
Product news to business contactsAccount DataBynn's legitimate interest in business communications, or consent where the law requires it; you may opt out at any time
Operating the Website; analytics and marketing cookies only where you allow themWebsite dataStrictly necessary storage: Bynn's legitimate interest in providing the Website you request; analytics and marketing: consent (Article 6(1)(a))
Running the referral program: crediting referrals, applying the referral discount, calculating and paying commission, and preventing referral fraudReferral data, Partner data, Account Data, Usage DataFor a Partner, performance of the Affiliate Program Agreement (Article 6(1)(b)) and compliance with tax obligations (Article 6(1)(c)); for a referred visitor or Customer, Bynn's legitimate interest in giving the discount and credit the referral link offers and in preventing fraud (Article 6(1)(f))
Complying with the law, responding to lawful requests, and establishing, exercising or defending legal claimsAny of the above, as necessaryCompliance with legal obligations; Bynn's legitimate interest in protecting its rights
Purpose
Providing the Service: processing API requests and returning Outputs
Data used
Account Data, Customer Data, Usage Data
Legal basis
Performance of the contract with the Customer (Article 6(1)(b)); for Customer Data, the Customer's instructions as Controller
Purpose
Administering Accounts, authentication and support
Data used
Account Data, communications
Legal basis
Performance of the contract; Bynn's legitimate interest in supporting its customers (Article 6(1)(f))
Purpose
Billing, payment, tax and accounting
Data used
Account Data (billing), Usage Data
Legal basis
Performance of the contract; compliance with legal obligations (Article 6(1)(c))
Purpose
Security, abuse prevention, the Safety Check and enforcement of the Terms of Service and the Acceptable Use Policy
Data used
Usage Data, safety records and, where an investigation requires it, Customer Data
Legal basis
Bynn's legitimate interest in protecting the Service, its customers and the public; compliance with legal obligations
Purpose
Service notices, such as changes to terms, security notices and incident notifications
Data used
Account Data
Legal basis
Performance of the contract; compliance with legal obligations
Purpose
Operating, analysing and improving the Service
Data used
Usage Data, Website data, aggregated or de-identified data
Legal basis
Bynn's legitimate interest in running and developing its Service
Purpose
Developing, training, evaluating and improving the Models and the Safety Check
Data used
Customer Data where the Customer has not opted out (Section 4), never biometric data, safety records
Legal basis
For Customer Data, the Customer's instructions as Controller under Section 8.4 of the Terms of Service; for safety records, Bynn's legitimate interest in developing accurate and safe Models, with measures to remove or reduce Personal Data before use
Purpose
Comparing the faces in a Customer's pictures with a Collection, and holding the Face Items a Customer enrolls
Data used
Biometric data
Legal basis
The Customer's instructions as Controller under the Data Processing Addendum; the Customer is responsible for the lawful basis and the condition for processing biometric data that its use relies on, including the consent of each person whose face it enrolls where the law requires it (Section 6.9 and Section 6.10 of the Terms of Service)
Purpose
Maintaining the Celebrities Collection
Data used
Celebrities Collection
Legal basis
Bynn's legitimate interest in letting Customers recognise public figures in pictures, limited to persons in their public role, and the condition for processing biometric data that Applicable Law provides
Purpose
Maintaining the Wanted Persons Collection
Data used
Wanted Persons Collection
Legal basis
The substantial public interest that Applicable Law recognises in locating persons whom public authorities seek, under the conditions that law sets; for the name, the charges and the issuing country, which relate to criminal offences, processing that Applicable Law authorises with appropriate safeguards (Article 10 of the GDPR): only the details the public authority published for this purpose, used only to answer the searches of Customers that are government agencies or public authorities, or organisations with the approval and the legal right to process such data under the law that applies to them, whom Bynn has verified and enabled for law enforcement or comparable purposes, kept no longer than the notice stands
Purpose
Product news to business contacts
Data used
Account Data
Legal basis
Bynn's legitimate interest in business communications, or consent where the law requires it; you may opt out at any time
Purpose
Operating the Website; analytics and marketing cookies only where you allow them
Data used
Website data
Legal basis
Strictly necessary storage: Bynn's legitimate interest in providing the Website you request; analytics and marketing: consent (Article 6(1)(a))
Purpose
Running the referral program: crediting referrals, applying the referral discount, calculating and paying commission, and preventing referral fraud
Data used
Referral data, Partner data, Account Data, Usage Data
Legal basis
For a Partner, performance of the Affiliate Program Agreement (Article 6(1)(b)) and compliance with tax obligations (Article 6(1)(c)); for a referred visitor or Customer, Bynn's legitimate interest in giving the discount and credit the referral link offers and in preventing fraud (Article 6(1)(f))
Purpose
Complying with the law, responding to lawful requests, and establishing, exercising or defending legal claims
Data used
Any of the above, as necessary
Legal basis
Compliance with legal obligations; Bynn's legitimate interest in protecting its rights
Purposes of processing and their legal bases
3.2

Legitimate interests. Where Bynn relies on its legitimate interests, it has balanced them against your interests and rights, and you may object as described in Section 9.

3.3

No sale and no targeted advertising. Bynn does not sell Personal Data, and does not share it for cross-context behavioural advertising or targeted advertising.

3.4

No automated decisions about you. Bynn does not make decisions based solely on automated processing that produce legal or similarly significant effects for you. A Customer that uses the Service to make decisions about people does so as Controller, under Section 3 of the Acceptable Use Policy.

4Section 4. Model improvement

#
4.1

Customer Data. Under Section 8.4 of the Terms of Service, Bynn may use Input and Output to develop, train, evaluate, improve and commercialise the Models, the Safety Check and the Service, and to create datasets and other works derived from them, unless the Customer has opted out. Biometric data processed by a Biometric Booster or held in a Collection, and the Item Metadata and wanted persons' details a match returns, are never used for this purpose, whatever the Customer's choice. Bynn applies measures designed to remove or reduce Personal Data and other identifiers from Customer Data before it is used for this purpose, to the extent practicable, and does not use it to identify or market to anyone. Bynn does not sell Personal Data. Where Bynn licenses, sells or transfers a Model, a dataset or other derived data to a third party, it first de-identifies the data so that it cannot reasonably be linked to any person, publicly commits not to re-identify it, and requires the recipient by contract not to attempt re-identification; such de-identified data is not Personal Data. Bynn never uses for this purpose Customer Data of a Customer that has opted out or selected zero retention, of a Customer party to an Order Form with Fees unless the Order Form provides otherwise, or submitted under a Defence Contract Addendum. A Customer opts out for its whole Account by the setting in the Console where Bynn provides one, or by notice to privacy@bynn.com, and the opt-out takes effect for data submitted afterwards.

4.2

Safety records. The records of requests the Safety Check refuses or flags may be used to improve the Models and the Safety Check in every case.

4.3

Usage Data. Usage Data, which does not include the content of Input or Output, may be used to operate and improve the Service.

5Section 5. Retention

#
5.1

Customer Data. Input and Output are deleted thirty (30) days after each request, unless (a) the Customer has chosen zero retention, which Bynn offers on every plan, on request, in which case they are not stored after the Output is returned; (b) a longer period is required by law; (c) they are needed to investigate a suspected breach of the Acceptable Use Policy or of Section 4 of the Terms of Service, in which case only what the investigation requires is kept, for as long as it requires; or (d) they, or datasets derived from them, are held under Section 4 for as long as they are useful for that purpose. The request file of a Batch API job is deleted when its results are written, and the results after the period stated in the Documentation.

5.2

Safety records. Records of requests refused or flagged by the Safety Check are kept for ninety (90) days. Logs of requests served with the Safety Check switched off under a Defence Contract Addendum are kept for two (2) years. Safety records are kept for abuse prevention, security and audit, and may be used to improve the Safety Check as Section 4.2 describes.

5.3

Account Data and communications. Account Data and communications are kept while the Account is open and afterwards for as long as necessary to comply with legal obligations, resolve disputes and enforce Bynn's agreements.

5.4

Billing records. Billing records are kept for the period that tax and accounting law requires.

5.5

Usage Data and Website data. Usage Data is kept for as long as needed for the purposes in Section 3 and is then deleted or aggregated. Website data is kept as described in the Cookies Policy.

5.6

Sessions. During a Session, its instructions, state, questions and most recent Frames are held for the life of the Session, solely to answer later Frames, including where zero retention applies, as Section 8.11 of the Terms of Service provides. Frames and their Outputs are Input and Output, and are deleted as Section 5.1 describes once the Session ends.

5.7

Referral and Partner data. The Referral cookie lasts forty-five (45) days and is removed when you open an Account. Daily click counts are kept for twenty-five (25) months. Records of referrals, commission and payouts are financial records, kept for seven (7) years after a Partner's participation ends or after the last payment, whichever is later; the identity of a referred person in them is removed when that person's Account is deleted.

5.8

Biometric data and Collections. A face template that a Biometric Booster derives is deleted when its request ends; the pictures follow Section 5.1. A Face Item and its Item Metadata are kept until the Customer deletes them or the Collection, or until Bynn deletes them under Section 6.10 of the Terms of Service after storage fees go unpaid; a deleted Face Item's face template and Item Metadata are deleted at once and cannot be restored. An entry of the Wanted Persons Collection, its name, charges and issuing country included, is kept only while the public authority's request to locate the person stands: Bynn updates the collection from the public notices every day and deletes an entry at the first update after its notice is withdrawn or lapses. An entry of the Celebrities Collection is kept while Bynn offers that collection, and is deleted when the person asks for it under Section 9 or ceases to be a public figure.

5.9

Batch jobs. The requests of a Batch Job are stored, encrypted, from the moment they are uploaded until the Batch Job's results are written, and are then deleted. Its results are stored, encrypted, for seven (7) days after the Batch Job ends, and are then deleted. A Batch Job that is not finalized within twenty-four (24) hours of its creation is cancelled and its requests deleted. This applies even where zero retention applies, as Section 8.13 of the Terms of Service provides: zero retention does not cover Batch Jobs.

6Section 6. Security

#

Bynn protects Personal Data with technical and organisational measures appropriate to the risk, including encryption in transit and at rest, access on a need-to-know basis, rotation of keys and credentials, and logical separation of each Customer's data. Bynn's information security management system is certified to ISO/IEC 27001:2022 and Bynn holds a SOC 2 report from an independent auditor, each with the scope stated in the certificate and the report, available through Bynn's trust center and on request at security@bynn.com, subject to confidentiality. The measures that apply to Customer Data are described in the Data Processing Addendum. No method of transmission or storage is completely secure, and Bynn cannot guarantee absolute security. Bynn notifies Customers of a Personal Data Breach affecting Customer Data as the Data Processing Addendum provides, and notifies authorities and individuals where the law requires.

7Section 7. Disclosure and Sub-processors

#
7.1

Sub-processors and service providers. Bynn uses service providers in the following categories, each bound by a written agreement that requires it to protect Personal Data and to use it only to provide its services to Bynn: (a) cloud computing and hosting; (b) payment processing; (c) email delivery; and (d) error monitoring for the Website, the Console and the Service. The current list of Sub-processors is available to Customers in the Console and on request at privacy@bynn.com. Customers receive thirty (30) days' notice of changes, as the Data Processing Addendum provides.

7.2

Other recipients. Bynn may also disclose Personal Data (a) to its Affiliates, for the purposes in this Policy; (b) to its professional advisers, under a duty of confidentiality; (c) to courts, regulators, law enforcement or other authorities, where the law requires it or where necessary to protect the rights, property or safety of Bynn, its customers or others, including reports of apparent child sexual abuse material; (d) to a successor or acquirer in a merger, acquisition, financing or sale of all or part of Bynn's business, subject to this Policy; (e) to the Customer, where you are its Authorised User, which may see your activity in its Account; and (f) with your consent.

7.3

Referral program. A Partner who referred you never receives your identity, your contact details or your workspace's name: the Partner sees only that a referral was made, when, its status and the commission it earned. Partner payouts are made through Bynn's payment processor.

8Section 8. International transfers

#

Bynn and its Sub-processors may process Personal Data in countries other than the one in which you live, including the United States. Where Personal Data is transferred from the European Economic Area, Bynn relies on the Standard Contractual Clauses adopted by the European Commission in Implementing Decision (EU) 2021/914 or on an adequacy decision. Where it is transferred from the United Kingdom, Bynn relies on the International Data Transfer Addendum to those clauses issued by the Information Commissioner. A copy of the relevant safeguards is available on request at privacy@bynn.com.

9Section 9. Your rights

#
9.1

European Economic Area and United Kingdom. Where the GDPR or the UK GDPR applies, you have the right to access your Personal Data; to have it rectified; to have it erased; to restrict its processing; to receive it in a portable format; to object to processing based on legitimate interests, and at any time to direct marketing; to withdraw consent at any time, without affecting earlier processing; not to be subject to a decision based solely on automated processing that produces legal or similarly significant effects; and to lodge a complaint with a Supervisory Authority, in particular in the country where you live or work, or with the Information Commissioner in the United Kingdom.

9.2

United States. Where a United States state privacy law applies, including the California Consumer Privacy Act as amended by the California Privacy Rights Act and the comprehensive privacy laws of other states, you may have the right to know what Personal Data Bynn collects and how it uses and discloses it; to access, correct and delete it; to receive it in a portable format; to opt out of its sale, its sharing for cross-context behavioural advertising, targeted advertising and profiling, none of which Bynn carries out; to limit the use of sensitive personal information, which Bynn uses only as those laws permit; to appeal a decision about your request; and not to be discriminated against for exercising any of these rights. You may use an authorised agent, who must provide proof of authority.

9.3

How to exercise your rights. Send your request to privacy@bynn.com. Bynn will verify your identity before acting on it, and responds within one (1) month where the GDPR or the UK GDPR applies, or within forty-five (45) days where a United States state law applies, extendable as those laws permit. To appeal a decision, reply to Bynn's response with the word "appeal"; if your appeal is refused, you may contact the attorney general of your state.

9.4

Requests about Customer Data. Where your request concerns Personal Data that a Customer submitted through the API, Bynn forwards it to that Customer, which decides how to respond, and assists the Customer as the Data Processing Addendum provides. Because Input and Output are deleted after the retention period, Bynn may no longer hold the data concerned.

10Section 10. Children

#

The Service and the Website are not directed at children, and Bynn does not knowingly collect Personal Data, as a Controller, from anyone under eighteen (18). If Bynn learns that it has done so, it deletes that data. A Customer that submits Personal Data of children as Input is responsible, as Controller, for having a lawful basis to do so. Contact privacy@bynn.com if you believe a child has provided Personal Data to Bynn.

11Section 11. Cookies and similar technologies

#

The Website uses cookies and browser storage in three categories: strictly necessary, analytics and marketing. Analytics and marketing technologies are used only with your consent. The Cookies Policy describes each category and how to change your choices.

12Section 12. Changes to this Policy

#

Bynn may update this Policy. Bynn gives at least thirty (30) days' notice of a material change before it takes effect, by email to Account contacts or by a notice on the Website, and shows the date of the latest version at the top of this page.

13Section 13. Contact

#

Postal address: Bynn Intelligence, Inc., 2261 Market Street STE 22340, San Francisco, CA 94114, United States. Bynn's representative in the European Union under Article 27 of the GDPR is Mikael Hedlöf, Östermalmstorg 1, 114 42 Stockholm, Sweden, mikael.hedlof@bynn.com, whom you may contact on any matter under this Policy. Bynn's representative in the United Kingdom under Article 27 of the UK GDPR is Daniel Smedberg, 3-7 Temple Avenue, Temple, London EC4Y 0DT, United Kingdom, daniel.smedberg@bynn.com, whom you may contact on any matter under this Policy.

Privacy questions and requests
privacy@bynn.com
Security issues
security@bynn.com
← previousAcceptable Use Policynext →Data Processing Addendum
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