Scope and operating boundary
This page explains the relevant product boundary, provider dependency and customer responsibility in plain language.
Data retention & deletion
Data retention & deletion, written around the service you actually use.
Map active records, exports, media, logs, backups and provider copies to actual retention, expiry, deletion and recovery behavior.
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.
Account and record lifecycle
Data categories & purposes
Media, cache & backups
Retention & deletion
Rights & secure requests
Schedule required
The final schedule must cover public enquiries, host/security logs, workspace records, conversations, attachments, knowledge, usage/billing records and backups, with purpose, trigger, period or criteria, deletion method, exceptions and evidence for each category.
Access and deletion
Account export and deletion behavior must be tested in the App-owned environment. This Site run does not inspect or mutate App customer data. Do not promise a fixed deletion window or immediate backup erasure without operational evidence.
Exceptions
Any legal retention, security hold or backup rotation exception must be narrow, access-controlled and explained in the final reviewed notice.