不可变版本 / Immutable version 2026-10-25.3. 本副本不加载分析或应用脚本 / No analytics or app scripts.
适用于托管组织、席位、组织资产与策略，以及订单实际提供的企业发行物或自建网关。
2026-10-25.3 · 2026-10-25
本附件适用于 Laintas Enterprise 的相应功能，与平台服务条款、隐私政策、数据用途说明及收费与退款政策共同适用。仅在本附件明确的产品事项上补充或优先于总条款；强制性法律及双方有效的个别协商约定优先。以购买或使用时明确提供且依法有效接受的版本为准，网页更新不自动改变已有订单。
托管组织管理与客户自建网关是不同部署方式，不承诺每个客户自动获得全部部署或功能。订单应明确组织、席位、许可期限、发行物、部署方、费用、支持和数据位置。托管模式可由 Laintas 保存组织、成员、资金、策略、审计和云资产；自建模式相应数据可保留在客户设施，但许可证验证、下载、选用上游及支持仍可能有对外通信。不能概括承诺所有企业数据永远不离开客户服务器。
客户应指定有权管理组织的人员，对成员邀请、角色、策略、工具、模型来源及数据访问范围作合理配置，并依法向成员告知审计、费用和工作数据处理。管理员可能访问组织用量、审计及资产，但组织权限不当然授予访问成员全部个人文件或私人对话。离职、移交、权限撤销和凭据轮换须及时处理，Laintas 按实际控制范围提供协助。
席位资金池、企业订阅和组织存储是不同项目。出资人按确认范围从个人余额划入资金，成员选择活动席位后在授权产品、模型和策略内使用；席位余额不足、停用、封顶或策略未满足时拒绝，不静默转扣成员个人余额。关闭席位时未使用资金按实际规则退回原出资账户，出资账户注销及未决争议另依法律和已确认处理规则结算。内部退回不等于自动向银行卡退款，外部退款适用统一收费政策。
组织应有权发布、同步和执行其 Skills、流程、提示词及代码，并确保上游许可允许相应用途。托管云资产可保存在私有对象存储，版本、权限和账单等元数据由平台保存；自建部署由客户配置存储和备份。签名校验、策略执行与防篡改只说明相应技术验证，不保证资产全部合法安全。企业私有发行物按其许可证和订单使用，不因个人版源码可见而成为可公开分发的代码。
涉及客户委托处理时，应在订单或数据处理约定中明确目的、类别、期限、指令、转委托、跨境、协助权利、安全事件、删除或返还。仅提供通用产品不自动承诺特定 SLA、驻留地区、赔付额度或认证资质；如有要求需书面约定。客户负责其设施、备份、主密钥和第三方账户，Laintas 负责其实际提供和控制的部分。终止前应安排迁移、撤销访问、处理剩余资金和依法留存记录，不能把停止许可理解为平台可任意处置客户数据。
组织应由有权限人员采购、分配席位及制定策略，并向成员说明哪些组织数据、用量、资产或审计记录可被管理员查看和控制。个人账户与加入组织的关系不使个人全部聊天、余额或私有文件自动归组织所有；具体访问范围以有效约定和部署为限。成员离开或权限撤销后，组织资产与个人资料分别处理，不能继续使用已被撤销的组织资金。组织内部授权争议应提供权限及操作记录，平台按自身角色协助，不把管理员所有操作都当然认定为已获成员个人信息同意。
涉及受托处理、保密资料或特定驻留要求时，应在传输前明确处理目的、期限、方式、数据种类、主体范围、地域、服务商、协助权利请求、安全事件通知及退出删除安排。自建网关仍可能调用外部模型、搜索、授权和平台账务，必须按实际流向核对；不能仅凭自部署就承诺全部数据永不离开组织。若未另行约定，不默示提供行业专属认证、无限制审计、固定响应时限或零留存；依法必须履行的安全和个人信息保护义务仍然适用。
选用组织席位时应核对组织、席位和当前资金策略；所选席位不可用或预算不足时，当前相关路径拒绝调用，不静默转扣个人资金。充值、分配到池、成员消费、未结用量与关闭退回是不同账目。关闭资金池后可退未使用部分按记录返回原出资方的内部余额，不当然原路退到银行卡或成为管理员收益；原充值如需外部退款另按收费政策办理。关闭前应处理正在运行和未结任务、成员权限及资料导出，存在争议的部分应单独核查。
采购订单应明确实际交付范围、订阅期、部署方式、支持、软件许可及约定的服务等级。控制台可见某入口不代表已购买专属服务器、无限模型额度或实施服务。终止或不续费前，应按合同安排迁移、导出、权限撤销和保密资料处理；没有自动导出能力的内容可请求按实际可行方式协助，不能保证所有第三方系统和本机资料均能一键迁移。终止后依法保留的财务、安全和争议记录继续受目的及保密限制，未履行预付款与应付有效用量另行清算。
For hosted organisations, seats, assets and policies, and enterprise distributions or self-hosted gateways actually supplied under an order.
2026-10-25.3 · 2026-10-25
This annex applies to the relevant Laintas Enterprise functions together with the Platform Terms, Privacy Policy, Data Use Notice and Billing and Refund Policy. It supplements or overrides general terms only on its stated product matters. Mandatory law and valid individually negotiated agreements take priority. The version expressly provided and validly accepted at purchase or use applies; a web update does not automatically change existing orders.
Hosted organisation management and customer-hosted gateways are distinct. Not every customer automatically receives every deployment or feature. Orders identify the organisation, seats, licence term, distribution, deployment owner, fees, support and data location. Hosted mode may keep organisation, membership, funding, policy, audit and cloud-asset data with Laintas. Self-hosted mode can keep corresponding data at customer facilities, while licensing, distribution, chosen upstream and support may still communicate externally. No blanket promise is made that all enterprise data always stays on customer servers.
Customers appoint authorised administrators and configure invitations, roles, policies, tools, model sources and data scope, with lawful member notice about audit, spending and work-data processing. Administrators may access organisation usage, audit and assets but not automatically every personal file or private conversation. Handle departures, handover, revocation and key rotation promptly; Laintas assists within its actual control.
Seat pools, enterprise subscriptions and organisation storage are separate items. Funders transfer balance within confirmed scope; members select active seats and use authorised products, models and policy. Exhausted, disabled, capped or policy-ineligible seats refuse rather than silently charging personal balance. Closing returns unused funds to the original funding account under the actual rules; funder closure and disputes follow law and confirmed treatment. An internal return is not an automatic card refund; external refunds follow the billing policy.
Organisations need rights to publish, sync and execute skills, flows, prompts and code and appropriate upstream licences. Hosted assets may be in private object storage with platform metadata for versions, permissions and billing; customers configure storage and backup when self-hosting. Signatures, policy and tamper checks establish particular validations, not complete legal or safety guarantees. Private enterprise distributions follow their licences and orders and are not publicly redistributable merely because the personal edition is source-available.
Where processing is on customer instructions, the order or processing agreement should define purposes, categories, term, instructions, subprocessors, transfers, rights assistance, incidents and deletion or return. A general product does not automatically promise a particular SLA, residency, compensation or certification; agree such requirements in writing. Customers control their facilities, backups, master keys and external accounts; Laintas is responsible for what it supplies and controls. Plan migration, revocation, remaining funds and legally retained records at termination; licence expiry does not permit arbitrary disposal of customer data.
Authorised staff should procure, assign seats and set policies, telling members what organisational data, usage, assets and audit records administrators control. Joining an organisation does not automatically transfer every personal chat, balance or private file to it; access remains within valid agreement and deployment. Treat organisational assets and personal data separately after departure and do not use revoked funding. Provide authority and action records for internal disputes. Laintas assists within its role without assuming administrator actions establish all member privacy consents.
Before entrusted processing, confidential use or residency-restricted transfer, agree purpose, duration, methods, categories, individuals, location, providers, rights assistance, incident notification and exit deletion. Self-hosted gateways may still call external models, search, identity and platform accounting. Verify actual flows rather than promising that all data stays inside merely because of self-hosting. Without separate agreement, industry certification, unlimited audits, fixed response times and zero retention are not implied; mandatory security and personal-data duties still apply.
Check organisation, seat and funding policy when selecting a seat. Current relevant paths reject unavailable or insufficient seats without silently charging personal funds. Deposits, pool allocations, member usage, unsettled calls and closure returns are distinct entries. Refundable unused pool funds return to the recorded original funder’s internal balance, not automatically to a bank card or administrator income. External refunds of original deposits follow billing policy. Address running and unsettled tasks, access and exports before closure, reviewing disputed portions separately.
Orders should define deliverables, term, deployment, support, licences and agreed service levels. A console entry does not establish purchase of dedicated servers, unlimited model allowance or implementation work. Arrange migration, exports, revocation and confidential-data handling before termination or nonrenewal. Request feasible assistance where automatic export is unavailable, without a universal one-click migration promise for third-party or local systems. Legally retained financial, security and dispute records remain purpose- and confidentiality-restricted. Reconcile undelivered prepayments and valid outstanding usage separately.