Skip to content

Privacy structure

Understand where public-site and product data belong.

Rellooma separates public-site data, authenticated workspace data and provider-channel data.

01

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.

02

Current limitation

This page does not invent an operator address, jurisdiction, subprocessor list or retention period.

03

Decision this page supports

You can review the separation between website, workspace and provider data before deciding what information to share.

Policy outline

The topics this policy must resolve

Each topic remains tied to approved operator, product, provider and policy facts. A missing fact is left open rather than replaced with a default legal promise.

01

Operator & contact identity

This topic will state the approved operating rule, responsibility and practical next step.

02

Privacy roles & instructions

This topic will state the approved operating rule, responsibility and practical next step.

03

Data categories & purposes

This topic will state the approved operating rule, responsibility and practical next step.

04

Legal bases & choices

This topic will state the approved operating rule, responsibility and practical next step.

05

Recipients, providers & transfers

This topic will state the approved operating rule, responsibility and practical next step.

06

Retention & deletion

This topic will state the approved operating rule, responsibility and practical next step.

07

Rights & secure requests

This topic will state the approved operating rule, responsibility and practical next step.

08

AI role & human review

This topic will state the approved operating rule, responsibility and practical next step.