Security & trust

Keep authority scoped, explicit and observable.

Rellooma keeps access tied to the right workspace and stops a live action when permission or channel readiness is uncertain.

Scope and operating boundary

Sensitive workspace changes and provider actions are checked on the server. General analytics and operational logs do not need raw customer-message content.

Current limitation

No certification, compliance status, uptime commitment or provider approval is claimed here without current evidence.

Decision this page supports

Customers can distinguish implemented controls, operational prerequisites and facts that still require verification.

Four connected checks

Security sits around the action—not in a badge.

Each layer answers a different question before a person or automation can rely on the result.

Workspace authority

The server checks the user, role and workspace boundary. Seeing a control in the interface does not grant authority by itself.

Provider readiness

Authentication, connection health and channel capability remain separate. A connected label alone does not authorize a send.

Message-safe telemetry

Operational measurement uses bounded states and identifiers; raw customer-message text stays out of general analytics.

Public Ask isolation

Ask Rellooma uses public product knowledge only. It cannot read a private workspace, change CRM data or send a customer message.