Scope and operating boundary
This page explains the relevant product boundary, provider dependency and customer responsibility in plain language.
Subprocessors
Subprocessors, written around the service you actually use.
Publish only providers actually used for hosting, database, channel delivery, AI, email, analytics or support, with factual purpose and location where verified.
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.
Provider inventory & changes
Data categories & purposes
Recipients, providers & transfers
Safeguards & incident duties
Retention & deletion
Inventory status
A publishable inventory must identify each legal provider, service, data categories, processing location, transfer mechanism, contract status, and change-notice process. Site hosting/security services must be separated from App processors and independent channel/payment providers.
No inferred vendor list
A DNS record, SDK, deployment setting or provider name in source code does not alone prove the contracting entity, data flow, transfer mechanism or authorisation. Those facts remain gated until verified against current owner/provider records.
Changes
The final DPA must define the applicable authorisation and objection process for further processors. No advance-notice period is promised by this draft.