01
Scope and common rules
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.
02
Hosted, self-hosted and purchased scope
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.
03
Administrator authority and member notice
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.
04
Seat funds, closure and refunds
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.
05
Assets, policy and software licensing
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.
06
Processing, support, security and exit
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.
07
Enterprise procurement, administrators and personal accounts
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.
08
Processing agreements and provider controls
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.
09
Seat budgets, funding fallback and closure
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.
10
Contract end, migration and service commitments
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.