Privacy policy
What we collect when you use Binai, why, who helps us process it, how long we keep it, and what you can ask us to do with it.
Effective November 3, 2026
Draft. This document is being reviewed and may change before Binai’s public launch.
Who we are
Binai is operated by Nei Digital (RFC NDI200826LX9), with its address at Av. de las Américas 320, Interior 02, Altamira, 45160 Zapopan, Jalisco, Mexico (“we”, “us”), which is responsible for the personal data described here. This policy covers the Binai website at binai.app, the Binai back office used by our customers’ teams, and the support pages and chat sessions Binai runs for them. Questions about it go to privacy@binai.app.
Two kinds of people, two roles
Binai is used by companies (“customers”) to give support to their own users (“end users”). That gives us two roles:
- For customers and their operators (the people who sign up, set up a project and answer sessions), we decide why and how account data is used. We are the controller of that data.
- For end users (the people who open a customer’s support page and chat with the agent), we process the conversation on that customer’s behalf and on its instructions. The customer is the controller. If you contacted a company through a Binai support page, that company’s own privacy policy applies to you, and it is the first place to send requests about your data. We will help it answer them.
What we collect
Account data (customers and operators)
- Your name, email address and sign-in details, handled through our authentication provider, Clerk.
- The organizations (projects) you belong to and your role in each.
- Project settings: branding, the welcome text, agent instructions, the chosen AI model, usage limits, retention and notification settings.
- Knowledge you add (articles and procedures) and the external tools (MCP servers) you connect, including any authorization header you give us for them.
- An audit log of actions in your project: status changes, hand-offs, replies, tool calls and setting changes, with who made them and when.
- Daily usage counts (sessions, messages, model use) used to apply your plan’s limits.
Session data (end users, on our customers’ behalf)
- The name you type when you start a session, if you give one (it is optional), or your account details if the project requires you to sign in.
- Your messages, the agent’s and operators’ replies, files you or an operator attach in the chat (images, audio and video), and what the agent draws on the canvas.
- If you choose to share your screen: still frames of the tab or window you share, sent to the AI model and to operators watching the session, and live video to operators. Frames and video are not stored. Each frame is used for the next answer and then dropped.
- A short summary of the session, written by the AI model when the session closes, and the session’s status and timestamps.
Technical data
- Standard request data processed by our hosting provider (IP address, browser type, time of request) for delivering the service, security and abuse prevention, and error logs.
- Items kept in your browser, described on the Cookies page.
We do not sell personal data, we do not use it for advertising, and we do not use session content to train AI models.
How we use it
| Purpose | Data | Basis |
|---|---|---|
| Running the service: accounts, projects, sessions, the agent and the canvas | Account data, session data | Our contract with the customer |
| Applying plan limits and billing | Usage counts, plan | Contract |
| Security, abuse prevention and fixing errors | Technical data, audit log | Our legitimate interest in a safe, working service |
| Service messages (changes, incidents, security notices) | Email address | Contract and legitimate interest |
| Anything else we are legally required to do | As required | Legal obligation |
How the AI agent uses your data
Each session’s messages, images someone attaches (when the agent looks at one), the current canvas and, while you share your screen, the latest frame are sent to the AI model the customer has chosen so it can answer. Models run on Cloudflare Workers AI. The agent may search the customer’s knowledge and call the external tools the customer has connected; when it does, the parts of the conversation needed for that call are sent to those tools. Those tools are chosen and controlled by the customer, not by us.
AI answers can be wrong. Operators can read every session and take over at any point.
Who processes it for us
We use a small number of service providers (subprocessors) to run Binai. They process data only to provide their service to us. The current list, with what each one does, is on the Security page.
When a customer has not set up live video through Cloudflare Realtime, screen sharing between an end user and an operator uses a direct WebRTC connection between their browsers, which lets each side’s browser see the other’s IP address.
How long we keep it
- Session transcripts, canvases and attached files are deleted automatically after the retention period the customer sets for the project, counted from when the session closes. The default is 30 days. A customer may choose to keep them without a time limit.
- The session list entry (the end user’s name if given, status, summary, timestamps) and the audit log are kept while the project exists, so the customer’s team can review past sessions. A customer can ask us to delete them sooner.
- Screen frames and video are never stored.
- Account data is kept while the account is active and deleted within 90 days after it is closed, except what we must keep by law (for example, invoices).
Where it is processed
Our providers run on infrastructure in several countries, including the United States. Where the law requires it, we rely on appropriate safeguards for these transfers, such as standard contractual clauses.
Your rights
Depending on where you live, you can ask to access, correct or delete your personal data, to object to or restrict how we use it, to receive a copy of it, and to withdraw consent where we rely on it. In Mexico these include your ARCO rights (access, rectification, cancellation and opposition); in the European Union and the United Kingdom, your rights under the GDPR; in California, your rights under the CCPA.
- Customers and operators: in Mexico, an ARCO request must include your name, a way to reply to you, a copy of an ID, and a clear description of the data and what you want done with it. Write to privacy@binai.app. We answer within 30 days.
- End users: contact the company whose support page you used. If you write to us instead, we will pass your request to that company and help it answer.
You can also complain to your local data protection authority.
Security
Traffic is encrypted in transit, access to customer data is limited to each customer’s own team, and secrets such as tool authorization headers are write-only from the interface. More on the Security page.
Children
Binai is a business tool and is not directed at children under 16. Customers should not use it to collect children’s data without the consent the law requires.
Changes
When we change this policy we update the effective date above. If a change matters, we tell customers by email or in the back office before it applies.