資料管理資訊與同意規則

客戶營運的程序： 在為其自己的領域創建的合作夥伴計劃中，使用者定義合作夥伴和收購客戶的資料管理的目的、法律依據、資訊、報酬和支付。在功能的技術提供過程中，AIOS Business 可以在記錄的指令框架內充當資料處理器。

AIOS 附屬計劃： AIOS業務的業者作為獨立的資料控制者處理申請、唯一推薦識別、佣金結算、支付、稅務、聯繫和詐欺預防所需的資料。

防止資料保存濫用： IP位址、裝置和會話識別碼本身不決定排除。透過一起評估多個訊號，系統可以阻止明顯的重複或要求手動檢查。 AIOS Business 不會收集不必要的完整瀏覽記錄。

付款詳情： 整个银行帐号、IBAN 或 PayPal ID 可以加密存储，并且只能稍后以屏蔽形式显示在授权用户界面上。批量支付导出只能针对授权运营商进行，仅限于必要的数据。

強制確認： 注册者声明他已阅读此信息并请求创建帐户。为此所需的数据管理的主要法律依据是合同的签订和履行，而不是普遍的、无限的同意。

自願行銷貢獻： “请求 AIOS 商业新闻、优惠和广告材料”可以通过选中单独的默认为空的复选框来输入。拒绝这样做并不构成注册的障碍，也不会对使用服务造成不利。

撤銷： 在 可以隨時透過使用已傳送訊息、帳戶設定或帳戶中的取消訂閱連結來撤銷同意，無需任何理由或費用。 support@aios-business.com 。撤销并不影响此前数据管理的合法性。

使用者的責任： 使用者通常是自己的收件者清單、活動目標和訊息的資料控制者。他有義務適當地通知接收者，核實法律依據，並在必要時核實同意，處理資料主體的請求，並立即驗證選擇退出和反對。

AIOS商務的角色： 根據使用者的記錄說明處理建立、處理、安排、傳送和衡量活動結果所需的資料。 AIOS Business 不會將收件者清單用於其自身的廣告、分析、銷售或獨立商業目的。

運輸與測量服務提供者： 實際發送時，發送者、接收者、內容、附件和傳遞元資料可以被傳送到使用者連線的服務提供者。只有在使用者提供了法律依據和電子通訊規則規定的條件的情況下，開啟或點擊測量才能被啟動。連線啟動前會顯示服務提供者的名稱、目的地國家和條件。

When Gmail newsletter sending is connected, AIOS Business requests only OpenID and email identity plus the gmail.send permission needed to send messages initiated by the user. The verified email address identifies the sender, and Gmail tokens are used solely to send messages approved by the user in AIOS. AIOS does not request access to read, download, modify or delete messages, drafts, contacts or Drive files.

OAuth tokens are encrypted, isolated by organization and user, cannot be displayed again, and may be used only by the server-side Gmail sending process. Only the sender, recipients, subject, content and attachments needed for the requested send are transferred to Google. AIOS does not sell Google user data or use it for advertising, profiling, credit decisions or AI-model training. The connection can be removed in AIOS, access can be revoked in the Google Account, and stored credentials are deleted when the connection or account is deleted.

Google API Services User Data Policy · Limited Use

AIOS uses two isolated Microsoft flows. Microsoft sign-in or registration for an AIOS account uses OAuth 2.0 Authorization Code with PKCE and OIDC and only openid, profile, email and User.Read; it does not create a Microsoft 365 data connection and no access or refresh token is retained. The separate Microsoft 365 Connector uses openid, profile, email, offline_access and User.Read, with individually selected Files.Read, Mail.Read, Calendars.Read and Contacts.Read permissions and, for work or school accounts, Chat.Read and Sites.Read.All. Files.ReadWrite, Mail.Send and Calendars.ReadWrite are optional. Selecting them never performs an action. The technical Microsoft scope of Files.ReadWrite and Calendars.ReadWrite can be broader than the actions AIOS exposes, but AIOS provides no delete operation. AIOS never asks for or stores a Microsoft password.

AIOS binds accounts using the Microsoft tenant and object identifiers; an existing AIOS account is never linked solely because its email matches a Microsoft email. Search terms and the necessary access token are sent to Microsoft Graph and permitted results are shown in the current task. Ordinary Connector search terms and result contents are not retained; this does not apply to separately selected Company Knowledge sources. Company Knowledge synchronizes only OneDrive or SharePoint files, or direct folder contents, explicitly selected by the user. Supported text, metadata and provenance links are stored in the AIOS knowledge store; unsupported or oversized Office formats are catalogued as metadata only. Sending mail, creating a calendar event and saving a OneDrive draft each require a complete preview, a short-lived one-use approval bound to the browser and session, AIOS password confirmation and a separate execution command. On successful or failed execution, AIOS immediately replaces the complete preview with a content-free marker. The digest, status, limited result or error code and security events may be retained for no more than 30 days; an unexecuted preview may also remain for no more than 30 days. A bounded hourly maintenance job deletes the record and its events at the 30-day boundary, with an additional deletion check on the next action; deletion is retried after a transient storage failure. Account or Connector deletion starts immediate removal. AIOS does not sell this data or use it for advertising, credit decisions or AI-model training.

Connector access and refresh tokens are encrypted, isolated by organization and user, cannot be displayed again and are used only server-side. ID tokens are never stored persistently. Security events may contain fixed identifiers, event type, outcome, error code and timestamp, but never tokens. A selected Company Knowledge source can be removed separately; its stored AIOS document and index are deleted only when no other active selection references them. Disconnecting the Connector deletes its credential and associated Microsoft knowledge sources; consent can also be revoked in the Microsoft account. Deleting the AIOS account removes Microsoft identity bindings, connection data, knowledge sources and logs.

Microsoft Privacy Statement · Work or school account permissions · Personal account permissions