Scope and operating boundary
This page explains the relevant product boundary, provider dependency and customer responsibility in plain language.
Acceptable Use Policy
Acceptable Use Policy, written around the service you actually use.
Explain prohibited abuse, unlawful messaging, unsafe automation, credential misuse and attempts to bypass provider or workspace controls.
Current limitation
It does not invent a legal entity, jurisdiction, provider list, retention period or right that has not been confirmed.
Decision this page supports
You can understand the practical boundary and identify the facts that belong in an agreed service document.
Current published text
The text that applies today is published in English in the Rellooma app.
Working legal draft · English canonical
Draft clauses for owner and counsel review
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.
Acceptable use & enforcement
Channel/provider dependency
AI role & human review
Safeguards & incident duties
Suspension, termination & data
Prohibited activity
Proposed: do not use the service for unlawful messaging, spam, harassment, impersonation, fraud, malicious code, unauthorised access, data collection without authority, or evasion of channel permissions and security controls.
Messaging responsibility
Customers must establish their own lawful authority, permissions, opt-outs and channel eligibility before sending. A Rellooma feature label does not grant Meta or another provider permission.
Reporting and enforcement
The operational reporting contact, investigation steps, proportionate restrictions, notice and appeal process must be verified before this policy is made operative. Public demos must not receive credentials or private customer conversations.