Scope and operating boundary
This page explains the relevant product boundary, provider dependency and customer responsibility in plain language.
AI transparency
Explain where AI assists, how confidence and policy affect action, when humans take over, what telemetry is kept and which provider facts remain variable.
This page explains the relevant product boundary, provider dependency and customer responsibility in plain language.
It does not invent a legal entity, jurisdiction, provider list, retention period or right that has not been confirmed.
You can understand the practical boundary and identify the facts that belong in an agreed service document.
The text that applies today is published in English in the Rellooma app.
Working legal draft · English canonical
This English text is a non-operative review draft. It is not an effective policy, executed agreement or legal advice. Facts and clauses marked as open must be verified before publication.
DRAFT — NOT EFFECTIVE. No customer agreement or legal commitment is created by this page.
AI may assist with drafts, summaries or configured decisions, but outputs can be inaccurate or incomplete. Human review remains necessary for consequential communications and commitments unless the accepted product configuration proves otherwise.
Model provider, purpose, retention, training use, transfer location and profiling facts must come from the accepted App release and provider agreements. No training exclusion, residency or automated-decision claim is made here.
The public Site assistant remains disabled unless an approved public-only contract is active. It must not access tenant data, private conversations, credentials, internal prompts, CRM writes, refunds or legal commitments.