Security
How Binai is built to keep each project’s sessions to its own team, and the providers that help us run it.
Effective November 3, 2026
Draft. This document is being reviewed and may change before Binai’s public launch.
How it is built
- Encrypted in transit. Every page, API call and session connection uses HTTPS or secure WebSockets.
- One isolated store per session. Each support session lives in its own Cloudflare Durable Object, which holds its transcript and canvas and nothing else.
- Access by project. Operators connect with a verified session token, and only to sessions of the project they are signed into. End users get a signed token for their own session only, valid for seven days.
- Private instructions stay private. Notes operators send to the agent are filtered out before anything reaches the end user’s browser.
- Screens are not recorded. Shared-screen frames are used for the next answer and dropped. Live video is relayed, not stored.
- Attachments are files someone sends. Images, audio and video attached in the chat are stored in Cloudflare R2 and deleted with the session, on the project’s retention period.
- Write-only secrets. Authorization headers for your external tools can be set but never read back from the interface; only the server uses them.
- HTTPS-only tools. External tools (MCP servers) must use HTTPS. Every call the agent makes is written to the audit log.
- Automatic deletion. Transcripts, canvases and files attached in chat are deleted after your project’s retention period.
- An audit log of status changes, hand-offs, replies, tool calls and setting changes, for your admins.
What you control
- Who joins each project and whether they are an admin or a member.
- Whether end users must sign in before starting a session.
- How long transcripts and attached files are kept, how often screen frames are taken, and usage limits.
- Which external tools the agent may call.
Subprocessors
These providers process personal data to help us run Binai. We tell customers by email before adding or replacing one.
| Provider | What it does | Data | Location |
|---|---|---|---|
| Cloudflare, Inc. | Hosting and delivery (Workers), file storage for chat attachments (R2), the session store (Durable Objects), AI models (Workers AI), and live screen video for operators (Realtime, when enabled). | All service data, request data, session content, files people attach in chat, screen frames in transit | Global network; United States |
| Convex, Inc. | Database for projects, settings, knowledge, the session list, the audit log and usage counts. | Account data, project data, session list entries, audit log | United States |
| Clerk, Inc. | Sign-in, user accounts and organizations (projects and roles). | Names, email addresses, sign-in data, organization membership | United States |
The AI model is the one your project selects on Workers AI, run by Cloudflare. External tools you connect to your agent are chosen and run by you or your own providers; they are not our subprocessors.
Data processing agreement
If you need a data processing agreement for your end users’ data, write to legal@binai.app.
Report a vulnerability
If you find a security problem, write to security@binai.app with the steps to reproduce it. Please give us a reasonable time to fix it before telling anyone else, and do not access other customers’ data or disrupt the service while testing. We reply within three working days.