跨校合作的關鍵在於資料主權與合規邊界能否被清楚劃定。面對國外機構的法規差異與跨境要求，Uedu 優學院推出 UFO Platform（Uedu Federated Observation Platform）：採「自主管資料」（Bring Your Own Database, BYODB）設計，國外合作學校將對話資料完整保留在自己的系統，而 Uedu 只提供前端介面與研究流程所需的觀測與品質控管。資料不集中、權責不混淆，合作因此更可預期、更可審核。這條聯邦式路徑之所以能成立，是因為我們是自行開發系統。前端、資料模型、權限與寫入協定皆由我們掌握，才能因地制宜地切換到 BYODB，讓國外團隊把資料駐留在其雲端或校內設備，同時維持一致的研究流程與度量標準。對國內合作，我們則選擇集中託管路徑，以單一治理規則提升維運效率與安全稽核的一致性。
政策註記｜適用範圍
UFO Platform／BYODB 僅提供給國外合作團隊（境外機構）使用。
國內合作一律由優學院集中託管，不開放 BYODB。
我們做什麼：前端與觀測層
Uedu 提供清晰易用的前端介面與研究工作流，涵蓋登入與權限、研究場次管理、資料品質檢查與儀表板觀測。UFO Platform 僅在獲授權的前提下讀取唯讀檢視或去識別的彙整指標，不搬運、也不保存原始對話內容。需要近即時回饋時，前端以安全通道寫入合作方提供的資料端點，最終存放位置與存取規則由合作方自主管理。
你們掌握什麼：資料主權與合規邊界（國外適用）
對話資料存放在合作學校自選的環境，可採用自有雲端帳號（如 AWS、Vultr），也可使用校內設備（例如 Synology NAS 搭配資料庫與 S3 相容物件儲存）。資料所在區域、備份頻率、留存年限、存取名單與稽核規則由合作學校決定；研究結束或參與者撤回同意時，由合作學校直接執行刪除與封存。Uedu 不保留原始對話副本，也不在未經允許的情況下產生衍生資料。
技術樣貌：簡單、安全、可稽核
前端與合作方系統透過 TLS 與權杖驗證互通，寫入遵循最小必要權限，僅暴露必須的 API 或資料庫連線。儀表板預設走唯讀視圖，也可改以去識別摘要的 webhook 提供近即時監看。常見部署包含國外合作方自有雲端（AWS／Vultr 的資料庫與物件儲存）或校內 Synology NAS；Uedu 提供資料表結構、遷移腳本與連線設定範例，加速上線。所有事件與版本皆留痕，方便後續核查。
研究倫理與同意：依在地規範落地
不同國家的規範與流程各異。UFO Platform 尊重在地規範，由合作方 IRB 或等同機制主導同意書、目的聲明與使用範圍。Uedu 提供可參考的同意條文與資料地圖以協助審查，但最終決定權與責任留在資料擁有者的邊界內。
如何開始：從你們的資料端點出發（國外適用）
合作方提供資料庫或物件儲存的連線資訊與必要的角色／權限，Uedu 匯入結構與金鑰設定，完成端到端測試後即可啟用。若日後需要從雲端搬回校內，或由校內轉往雲端，只要在合作方系統完成遷移，前端設定即可無縫切換。
為何內外有別
我們選擇國外走聯邦、國內用託管，並非技術限制，而是治理策略。因為我們是自行開發系統，擁有協定與架構的話語權，才得以在國外以 BYODB 滿足資料駐留與跨境合規，同時在國內維持統一安全標準與較低維運複雜度。這種分流讓產品路線更可控、審查文件更一致、風險與成本更可預期，也讓未來的跨校比較能以去識別指標進行，而不牽動原始資料外流。
常見提問
Uedu 會保存原始對話嗎？ 不會。原始對話只存在合作方系統（國外）。國內合作則由優學院集中託管，依契約提供刪除與封存證明。
可以改變儲存位置嗎？ 國外合作可在合作方系統內自由遷移（雲端／校內）；國內合作採集中託管，不開放 BYODB。
儀表板怎麼看得到資料？ 以唯讀檢視或去識別摘要呈現，欄位可由合作方控管；國內合作由優學院受管環境提供相同觀測能力。
跨校比較要如何進行？ 交換小而清楚的去識別指標與一致度量，不交換原始內容。
UFO 聯邦觀測平台：在資料留在各校的前提下，提供可比較、可檢核、可重現的聯邦觀測與治理層。
聯絡我們
若你們是國外機構並希望以「自主管資料」的方式接入 Uedu 前端，歡迎來信洽談技術對接：張家凱 博士｜ckchang@uedu.tw。
國內合作請直接洽詢優學院集中託管方案，我們將依貴校規範與時程安排試辦與上線計畫。
Cross-institution collaboration depends on whether data sovereignty and compliance boundaries are clearly defined. To address regulatory differences and cross-border requirements for overseas institutions, Uedu is introducing the UFO Platform (Uedu Federated Observation Platform). The design follows a Bring Your Own Database (BYODB) model in which overseas partner schools keep all conversational data within their own systems, while Uedu provides only the front-end interface plus the observation and quality-control functions needed for research workflows. Data are not centralized and responsibilities are not blurred, which makes collaboration more predictable and auditable. This federated path is possible because we build the system ourselves. With full control over the front end, data model, permissions, and write protocols, we can adapt BYODB to local conditions so that overseas teams retain data in their cloud or on-prem environments while preserving consistent research processes and metrics. For domestic collaborations, we use a centralized hosting approach to strengthen operational efficiency and audit consistency under a single governance rule.
Policy note | Scope
UFO Platform / BYODB is offered only to overseas partner institutions.
Domestic collaborations are centrally hosted by Uedu and do not support BYODB.
What we do: the front end and observation layer
Uedu provides a clear, usable front-end and research workflow that covers sign-in and permissions, session management, data quality checks, and dashboards. The UFO Platform reads only read-only views or de-identified aggregates with explicit authorization. It does not move or store raw conversational content. When near real-time feedback is required, the front end writes through a secure channel to partner-provided endpoints; final storage location and access rules remain under the partner’s control.
What you control: data sovereignty and compliance boundaries (overseas only)
Conversational data reside in the environment chosen by the partner school. This may be the partner’s own cloud account (e.g., AWS, Vultr) or on-prem infrastructure (such as a Synology NAS paired with a database and S3-compatible object storage). The partner determines location, backup frequency, retention period, access lists, and audit policies; when a study ends or a participant withdraws consent, deletion and archiving are executed directly by the partner. Uedu does not retain raw conversational copies and does not produce derived data without permission.
Technical footprint: simple, secure, auditable
Communication between the front end and partner systems uses TLS and token-based authentication. Writes follow the principle of least privilege and expose only the necessary APIs or database connections. Dashboards default to read-only views and can be switched to de-identified webhook summaries for near real-time monitoring. Common deployments include partner-owned cloud resources (AWS/Vultr databases and object storage) or an on-prem Synology NAS. Uedu provides table schemas, migration scripts, and connection examples to accelerate onboarding. All events and versions are logged to support later audits.
Research ethics and consent: aligned with local rules
Regulatory processes differ across countries. The UFO Platform respects local governance: the partner’s IRB (or equivalent) leads consent wording, purpose statements, and data-use scope. Uedu supplies sample consent language and data maps to aid review, but final authority and responsibility remain within the partner’s boundary.
How to start: begin from your endpoints (overseas only)
The partner provides database or object-storage connection details and the required roles/permissions. Uedu loads the schema and keys, completes end-to-end tests, and enables the workflow. If a later move from cloud to on-prem—or on-prem to cloud—is needed, the migration occurs within the partner’s system, and the front-end configuration switches over seamlessly.
Why we differentiate overseas vs. domestic
Choosing federated for overseas and hosted for domestic is a governance strategy, not a technical constraint. Because we develop the system ourselves, we hold the protocol and architecture mandate needed to meet data-residency and cross-border compliance overseas via BYODB, while maintaining unified security standards and lower operational complexity domestically. This split keeps the product roadmap controllable, aligns documentation for review, makes risk and cost more predictable, and enables future cross-institution comparisons through de-identified indicators without moving raw data.
FAQ
Does Uedu keep raw conversations? No. For overseas collaborations, raw conversations stay only in the partner’s system. For domestic collaborations, Uedu centrally hosts and provides deletion and archival certificates per contract.
Can the storage location change? Overseas partners may migrate within their own systems (cloud/on-prem). Domestic collaborations are centrally hosted and do not support BYODB.
How do dashboards see data? Through read-only views or de-identified summaries with partner-controlled fields. Domestic collaborations provide the same observation capability within Uedu’s managed environment.
How will cross-institution comparisons work? By exchanging small, clear de-identified indicators and consistent metrics definitions, not raw content.
UFO Platform — Uedu Federated Observation Platform: a federated observation and governance layer where raw data stay with each institution.
Contact
If you are an overseas institution and wish to connect to the Uedu front end with a BYODB setup, please reach out for technical onboarding: Dr. Chia-Kai Chang | ckchang@uedu.tw.
For domestic collaborations, please contact us about Uedu’s centralized hosting offering. We will align a pilot and launch plan to your policies and timeline.
