Trust and compliance

Messaging governance for OTP, notifications and customer consent.

Essia communicates security in buyer language: who can send, what purpose exists, how consent is recorded and where request evidence lives.

LGPD-awareConsent statesRequest IDsServer-side secrets
Last updated: September 2, 2026

Terms of Service

These terms describe how businesses may use Essia services provided by ELASTIC ESSENCE LLC for A2P SMS, verification and notification workflows.

01

Server-side credentials

Private OneHub credentials remain on route handlers and Cloudflare secrets rather than in client bundles.

02

Consent separation

Account verification, operational service messages and optional marketing consent are modeled as separate decisions.

03

Request traceability

OneHub request IDs are preserved through the site layer for support, audit and incident review.

04

Rate-limit handling

UI states identify throttling and avoid hiding operational failures behind generic success messages.

05

Data minimization

Forms ask only for the fields required by the contract or the sales workflow.

06

Acceptable use

Terms explain prohibited traffic, abuse patterns, opt-out expectations and suspension rights.

Acceptable Use

How does Essia approach LGPD?

The public site separates account, operational and optional marketing consent, and the security pages explain data purpose, retention and user-right handling.

Acceptable Use

Terms of Service

These terms describe how businesses may use Essia services provided by ELASTIC ESSENCE LLC for A2P SMS, verification and notification workflows.

Acceptable Use