# Security Overview / 安全说明

> Source: https://listen.365ui.com/security
>
> Last updated: 2026-11-22

## Security Overview

Last updated: 2026-11-22

### 1. What this page is

For buyers and IT teams filling in a vendor security questionnaire: how the 365UI interpretation service works today. Our commitments on personal information are in the privacy notice and our service commitment is in the terms of service; this page adds no promises of its own. **We do not hold SOC 2 or ISO 27001 certification and have not had a third-party penetration test.**

### 2. How the sound and data flow

- At the venue or in an online meeting: mixer → USB audio interface → the ingest page on a venue laptop (Chrome, nothing to install); in a small room with no mixer, the speakers’ mics → a receiver → the ingest page (or an iPhone or iPad running our app “365UI Interpretation Audio”), or a phone’s own microphone; for an online meeting, Recall.ai (US) sends our bot into the Zoom, Google Meet or Microsoft Teams call to take in the sound (video and recording turned off, anything recorded deleted within an hour).
- Upload: the ingest page, the iOS audio app or the meeting bot’s page sends the sound through LiveKit Cloud to our server on Oracle Cloud (San Jose, California, US), encrypted in transit by WebRTC (DTLS-SRTP).
- Interpretation: the server sends the sound over encrypted connections (TLS) to the primary interpretation engine on Alibaba Cloud Model Studio (Singapore), and switches to the standby engine at OpenAI (US) when the primary is unavailable.
- Listening: interpreted audio and captions reach listeners’ phone browsers through LiveKit Cloud (for rooms with voice and a listener limit of 900 or more, through our servers on Oracle Cloud in San Jose and Phoenix instead, likewise encrypted by WebRTC, and over TURN/TLS on port 443 where UDP is blocked); for listeners who only read captions, caption text is relayed live through Cloudflare Workers (US, holding only the last 30 lines in memory, nothing written to storage); when someone chooses on the ingest page or the client event page to send captions into an online meeting, one language’s captions go to that Zoom, Teams or Webex meeting. All encrypted in transit.
- Website, questionnaires and assistants: listen.365ui.com is hosted on Vercel and served over HTTPS only; orders, questionnaire answers and event records are stored at Upstash (US East); questions to the site and ingest-page AI assistants are answered by our own US server (running Kimi K3, storing no copy) or by Alibaba Cloud.

### 3. Who can reach what

- Listeners: the event’s access code (carried in the QR code) gets a listening token valid for at most 10 minutes (refreshed while connected); it can only listen, cannot send audio or messages, and cannot see other listeners.
- Ingest page: one private link per room, exchanged for a fresh token valid only for the event each time it is opened. The customer can replace the link from their event page; the old link stops working at once and any page still using it is disconnected.
- Customer event page and AV pages: the links work as credentials and we store only their hashes. A leaked link can be revoked and replaced.
- Servers: SSH is the only inbound port, keys only, no passwords; the programs that process audio only make outbound connections and listen on no public port. Only the business owner has administrative access.

### 4. Isolation between rooms

Each room runs as its own process under its own temporary system user; it cannot see other rooms’ processes or environment (including keys), the system files are read-only to it, and it can write only its own directory. Each event can use its own interpretation-engine and delivery keys, revoked after the event.

### 5. Retention and deletion

- Archive of the original sound and transcripts: deleted automatically from the server after 30 days; for self-service events that keep recordings, a copy of each room’s venue recording is also placed in Oracle Cloud object storage (San Jose) for download from the event page and deleted automatically after 30 days; none is kept when the customer chooses “don’t keep” on their event page.
- Event records, questionnaire and AV page answers: deleted 30 days after the event ends (where the organizer chose to keep the transcripts, the event record and transcripts are kept until the organizer changes it back or asks us to delete them); encrypted nightly backups of the order database go to Oracle Cloud and each backup is deleted after 14 days (the decryption key is not kept on our servers).
- Server logs: kept 30 days; they record status, levels and usage, not what was said.
- Interpretation engines and transport: Alibaba Cloud keeps API inputs and outputs for up to 30 days and does not train on them without consent; OpenAI does not train on API data and keeps abuse-monitoring records for up to 30 days, and we have turned off data sharing for our organization; LiveKit does not record and keeps no audio once delivered; the Cloudflare caption relay writes nothing to storage.
- The full list of providers and retention periods is in sections 4 and 5 of the privacy notice (listen.365ui.com/privacy).

### 6. Availability

The primary and standby interpretation engines are both connected: if the primary drops or produces nothing for 12 seconds while someone is speaking, the system reconnects the primary in place first, and switches to the standby if the primary repeatedly hits content limits or stays disconnected past 15 seconds while someone is speaking. A second server starts automatically around self-service event slots. When the ingest page disconnects, the incoming sound is flat, or both engines are unavailable, the system emails the customer and us. Credits for time the service was unavailable for reasons on our side are in section 8 of the terms of service.

### 7. Payments

Payments are processed by Stripe and we never see full card or bank account numbers. The restricted Stripe key the website uses can only create checkout pages and read a payment’s method for invoices (plus settle legacy saved-card overages); it cannot issue refunds or list customers.

### 8. Content the service is not for

The service is not for identifiable patient health information (such as content covered by HIPAA), identity document numbers, financial account numbers or similar sensitive information; see section 9 of the terms of service.

### 9. Reporting a security issue

To report a security issue or send us a questionnaire, write to support@365ui.com. Security incidents involving personal information are notified as described in section 7 of the privacy notice.

## 安全说明

更新日期：2026-11-22

### 1. 这份说明是什么

给采购和 IT 填供应商安全问卷用，写的是 365UI 同传服务现在实际怎么做。对个人信息的承诺以隐私声明为准，服务承诺以服务条款为准，本页不另作承诺。**我们没有 SOC 2 或 ISO 27001 认证，也没有做过第三方渗透测试。**

### 2. 声音和数据怎么走

- 会场和线上会议：调音台 → USB 声卡 → 会场笔记本上的接声页（Chrome 浏览器，不装软件）；没有调音台的小房间是讲者的话筒 → 接收器 → 接声页（或插在 iPhone、iPad 上用我们的 App「365UI 同传接声」），或一台手机自带的麦克风；线上会议由 Recall.ai（美国）派机器人进 Zoom、Google Meet 或 Microsoft Teams 收声（不录像，留下的录制材料一小时内删除）。
- 上传：接声页、接声 App 或会议机器人页面经 LiveKit Cloud 把声音送到我们在 Oracle Cloud（美国加利福尼亚州圣何塞）的服务器，WebRTC 加密传输（DTLS-SRTP）。
- 翻译：服务器经加密连接（TLS）把声音送给阿里云 Model Studio（新加坡）的主用同传引擎；主用不可用时切到 OpenAI（美国）的备用引擎。
- 收听：译音和字幕经 LiveKit Cloud 送到听众手机的浏览器（收听上限 900 人及以上的有译音房间，改经我们在 Oracle Cloud 圣何塞和凤凰城的服务器，同样是 WebRTC 加密传输，封了 UDP 的网络经 443 端口的 TURN/TLS 连接）；只看字幕的听众，字幕文字经 Cloudflare Workers（美国）实时转发（只在内存保留最近 30 句，不落盘）；在接声页或专属页面选择把字幕送进线上会议时，一种语言的字幕发给那场 Zoom、Teams 或 Webex 会议。全程加密传输。
- 网站、问卷和助手：listen.365ui.com 托管在 Vercel，全站 HTTPS；订单、问卷和活动记录存在 Upstash（美国东部）；网页和接声页的 AI 助手由我们自己的美国服务器（运行 Kimi K3，不另存问答）或阿里云回答。

### 3. 谁能访问什么

- 听众：凭每场活动的通行码（二维码里带着）换取最长 10 分钟有效的收听令牌（连接期间自动续期），只能收听，不能发送声音或消息，也看不到其他听众。
- 接声页：每个房间一条专属链接，每次打开现换一张只在活动期间有效的令牌。客户可以在专属页一键换链接，旧链接立即失效，正在用旧链接的页面被踢下线。
- 客户专属页和 AV 页：链接相当于凭据，我们只存它的哈希。链接泄漏时可以作废、换新。
- 服务器：只开放 SSH 一个入站端口，只认密钥、不认密码；处理音频的程序只向外连接，不在公网上监听。有管理权限的只有经营者一人。

### 4. 房间之间的隔离

每个房间是一个独立的进程，以单独的临时系统用户运行，看不到其他房间的进程和环境变量（包括密钥），系统文件只读、只能写自己的目录。每场活动可以使用单独的翻译引擎和传输服务密钥，活动后作废。

### 5. 保存和删除

- 原音和转写归档：在服务器上保存 30 天后自动删除；保存录音的在线下单活动，会后另复制一份会场录音到 Oracle Cloud（圣何塞）的对象存储供客户下载，同样 30 天后自动删除；客户在专属页选择「不保存」时不留归档。
- 活动记录、问卷和 AV 页答案：活动结束后 30 天删除（主办方选择文字稿一直保留的，活动记录和文字稿保存到主办方改回或要求删除为止）；订单库每晚加密备份一份到 Oracle Cloud，每份保存 14 天后删除（解密密钥不放在服务器上）。
- 服务器运行日志：保存 30 天，只记状态、电平和用量，不写讲话内容。
- 翻译引擎与传输：阿里云接口的输入和输出最多保存 30 天，未经同意不用于训练；OpenAI 接口不用于训练，滥用监测记录最多 30 天，我们已关闭组织层面的数据共享；LiveKit 不录制，送达后不保存；Cloudflare 字幕转发不写存储。
- 各服务商的完整清单和保存期限见隐私声明（listen.365ui.com/privacy）第 4、5 条。

### 6. 可用性

主用和备用两个翻译引擎同时连着：主用掉线或现场在讲而主用 12 秒不出结果时，系统先原地重连主用；主用重复触发内容限制，或断开超过 15 秒且现场在讲时，自动切到备用引擎。第二台服务器在自助活动的时段前后自动开机待命。接声页断开、送来的声音是平线、两个引擎都不可用时，系统自动给客户和我们发提醒邮件。因我们一方原因无法收听的补偿见服务条款第 8 条。

### 7. 付款

付款由 Stripe 处理，我们看不到完整卡号或完整银行账号。网站使用的 Stripe 受限密钥只能创建付款页、读取单笔付款的方式用于开具发票（以及对历史存卡订单执行超额补差）；它不能退款，也不能读取客户列表。

### 8. 不适合的内容

本服务不用于处理可识别患者的健康信息（例如受 HIPAA 约束的内容）、证件号码或金融账号等敏感信息，见服务条款第 9 条。

### 9. 报告安全问题

发现安全问题或需要填写问卷，请写信到 support@365ui.com。涉及个人信息的安全事件，我们按隐私声明第 7 条通知。
