Server-side credentials
Private OneHub credentials remain on route handlers and Cloudflare secrets rather than in client bundles.
Essia communicates security in buyer language: who can send, what purpose exists, how consent is recorded and where request evidence lives.
These terms describe how businesses may use Essia services provided by ELASTIC ESSENCE LLC for A2P SMS, verification and notification workflows.
Private OneHub credentials remain on route handlers and Cloudflare secrets rather than in client bundles.
Account verification, operational service messages and optional marketing consent are modeled as separate decisions.
OneHub request IDs are preserved through the site layer for support, audit and incident review.
UI states identify throttling and avoid hiding operational failures behind generic success messages.
Forms ask only for the fields required by the contract or the sales workflow.
Terms explain prohibited traffic, abuse patterns, opt-out expectations and suspension rights.
The public site separates account, operational and optional marketing consent, and the security pages explain data purpose, retention and user-right handling.
You are responsible for using Essia only for lawful business communications, keeping credentials secure and ensuring message content matches the declared purpose.
Account access, API keys and session tokens must be protected. You must notify Essia if you believe credentials were exposed or misused.
SMS delivery depends on carriers, routes, destination rules and recipient devices. Essia may provide reasonable status, request ID and support information, but cannot guarantee every carrier outcome.
Usage fees may depend on destination, channel, volume, route quality, support level and commercial agreement. Taxes or carrier charges may apply.
These terms describe how businesses may use Essia services provided by ELASTIC ESSENCE LLC for A2P SMS, verification and notification workflows.