Dodatni pogoji izdelka.
Effective: September 18, 2026
These Additional Product Terms apply when a Customer uses Mellovy’s AI agents, automated actions, usage measurement, or third-party connections. They supplement the Commercial Terms of Service and any deployment-specific terms accepted by Customer. Capitalized terms have the meanings given in the Commercial Terms of Service.
1. Agents and automated actions
An agent can process Customer Data and, when configured and authorized by Customer, use tools or connected systems to perform actions. Available actions depend on the service, the configuration, the permissions Customer grants, and the connected systems. Customer is responsible for selecting instructions, data sources, permissions, recipients, and workflows, and for ensuring that each authorized user is permitted to configure and use them.
Customer will grant an agent only the permissions needed for its task, review its activity, and revoke permissions that are no longer needed. Customer should test workflows before enabling actions that communicate externally, modify records, or are difficult to reverse. Customer will apply human review and approval where required by law or appropriate to the consequences of an action. Mellovy does not guarantee that an agent will interpret instructions correctly or produce the intended result.
2. Third-party connections
Customer may connect external services, systems, APIs, or tools (“Connections”) where the relevant functionality is available. Customer must have the rights and authority needed to make a Connection, grant access, and permit the requested data flows and actions. The terms and privacy notices of the third-party provider also apply to Customer’s use of that service. Customer should review the permissions requested and may revoke them through Mellovy or the third-party provider where that option is available.
Mellovy does not control an independent third-party service and is not responsible for its acts, omissions, availability, or changes. This does not limit Mellovy’s responsibility for its own obligations under the agreement. Mellovy may disable a Connection where reasonably necessary to address a security risk, legal requirement, or material technical change. Where practicable, Mellovy will notify Customer and provide a reasonable opportunity to discontinue or reconfigure the affected Connection.
3. Usage measurement and limits
Mellovy measures platform work in “credits.” A credit is an internal unit of consumption; it is not money and has no fixed cash value. Metered operations include model input and output tokens, cached input tokens, tool invocations, evaluation runs, judge calls, and stored bytes. The applicable rate card converts those operations into credits. The public self-service plans state the weekly credit allowance for the organisation, shared across its members. A negotiated Order must state the allowance, the meter to which it applies, the measurement period and reset, and any different measurement or limit that applies to that Customer.
At an included allowance limit, Mellovy stops admitting additional work that would exceed it. Paid overage is off by default. Mellovy will permit and charge for overage only if the organisation’s owner separately enables it after receiving and accepting an Order that states the operation or credit rate, how that rate converts into money, the billing basis, and both the maximum credit use and maximum monetary charge for the billing period. A credit cap alone is not a monetary spending limit. If those terms have not been accepted, no overage charge is due and additional work stops at the included allowance. Continued use does not authorize a new fee or a higher limit.
Mellovy will make the included allowance and applicable measurement terms available before the Customer places its Order. Usage records may be provisional while work is running and will be reconciled against actual consumption when the work completes. Customer should notify Mellovy promptly if it identifies a material error in a usage report or invoice. Customer will pay undisputed amounts when due under the Commercial Terms of Service.
4. Changes to measurement or limits
Mellovy may update the technical method used to measure usage for security, technical, or legal reasons. A change that increases charges, reduces an accepted allowance, or materially affects an agreed workflow will be notified in writing at least 30 days in advance and will take effect no earlier than the next billing period, unless Customer accepts it earlier or an immediate change is required by law or to address a security risk. No change applies retroactively. Customer may terminate the affected service before the change takes effect.
5. Model training and improvement
Mellovy does not use Customer Data or Output to train or fine-tune general purpose or customer-specific AI models unless Customer separately opts in under this Section. Processing required to provide, secure, support, or maintain the service, and measurement of operational events for billing or security, do not by themselves constitute model training.
An opt-in is effective only through a separate written Training Schedule signed by both Parties or a distinct authorization by a Customer administrator where the service presents the same information and records the authorization. The Training Schedule will identify the data categories covered, the training purpose, the relevant model or service, any model provider that receives the data, the retention period, and how the authorization can be withdrawn. The opt-in is off unless Customer has affirmatively enabled it. It does not extend to other Customer workspaces or data categories that are not identified in the authorization.
Customer may withdraw the authorization for future training at any time by using the available control or sending written notice to [email protected]. Withdrawal stops new use for training after the time reasonably required to apply the change, which will be stated in the Training Schedule. Withdrawal does not mean that previously trained model parameters can necessarily be reversed or that information already incorporated into a model can be removed. Mellovy will not represent that such removal is possible unless it can in fact be performed.
Customer’s authorization is a contractual instruction from Customer. It does not itself establish a lawful basis, satisfy a notice duty, or constitute consent from an individual whose personal data is included. Training involving personal data will not begin until the Parties have documented the applicable roles, lawful basis, notices, and instructions in the relevant data protection terms. Mellovy will not send Customer Data to a model provider for training unless that provider’s contract and settings permit the use described in the Training Schedule.
Feedback alone does not authorize use of related Customer Data or Output for model training. A beta, preview, or experimental feature is not an exception to this Section unless the applicable Training Schedule expressly identifies that feature and the relevant data use.
6. AI law, transparency, and human review
Each Party is responsible for the obligations that apply to it under applicable law based on its actual role and conduct. These terms do not change which Party is a provider, deployer, importer, or other regulated actor under applicable AI law. Customer is responsible for its configuration and use of the service, including information to its own users where required. Mellovy is responsible for obligations that apply to Mellovy in its own role.
Customer will not remove or bypass disclosures, labels, or safeguards provided by Mellovy where they are required by law. Customer will not configure an agent to mislead a person about whether they are interacting with AI or about the origin of generated content where applicable law requires disclosure. Customer remains responsible for assessing whether its use requires human oversight, impact assessment, record-keeping, or other safeguards.
7. Beta and preview features
A feature identified as beta, preview, experimental, or test is provided for evaluation and may be changed or discontinued. Unless the Order states otherwise, such a feature has no separate service level. The label does not itself authorize model training or change the data-processing terms.
8. Export and deletion
Customer may export Customer Data using the export functions made available for the applicable service. The export formats and scope depend on the service and deployment described in the Order. Return or deletion of personal data is governed by the DPA. If mandatory rules on switching between data-processing services apply to the service, the Parties will follow those rules and identify the relevant exportable data and process in the Order or a written transition plan.