Scope and operating boundary
A complete privacy notice identifies the operator, purposes, data categories, recipients, retention, rights and contact path that apply to the service.
Privacy structure
Understand where public-site and product data belong.
Rellooma separates public-site data, authenticated workspace data and provider-channel data.
Current limitation
This page does not invent an operator address, jurisdiction, subprocessor list or retention period.
Decision this page supports
You can review the separation between website, workspace and provider data before deciding what information to share.
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.
Operator & contact identity
Privacy roles & instructions
Data categories & purposes
Legal bases & choices
Recipients, providers & transfers
Retention & deletion
Rights & secure requests
AI role & human review
Who decides and why
The final notice must identify the responsible entity and assign controller or processor roles separately for each purpose. Responding to an enquiry, securing the Site, administering an account and optional marketing are distinct purposes and require verified lawful-basis decisions.
Data and recipients
The notice should enumerate only observed data fields and actual recipients. The Site contact schema may include name, email, company, market, role, channel, message and bounded attribution fields; current delivery configuration and hosted logs require verification.
Retention and international transfers
Retention periods, hosting locations, subprocessors and transfer safeguards are not inferred. Publish them only after provider and App evidence completes the applicable transfer and retention schedules.
Rights and contact
The final notice must give an operational privacy contact, rights request route and complaint information. Do not promise a response deadline or immediate deletion beyond the verified legal and operational process. Do not send credentials or private conversations through public forms.