Protected web sessions
Website sessions are issued through secure, HttpOnly cookies with Secure enabled in production and SameSite protection. Account sessions can be reviewed and revoked from the Account area.
A practical overview of the controls visible in the current Numelixa website, API and native Android application. This page does not claim independent certification or absolute security.
Website sessions are issued through secure, HttpOnly cookies with Secure enabled in production and SameSite protection. Account sessions can be reviewed and revoked from the Account area.
The native Android app stores its session credential using the platform secure-storage plugin. API requests use HTTPS and the mobile client refuses requests that resolve to a different origin.
Numelixa API keys are random secrets. The server stores a hash for authentication and an authenticated-encryption copy for the account's key-management flow. Keep keys on a trusted server and never embed them in a browser bundle or APK.
Developer webhooks are signed with HMAC-SHA256 over the timestamp and exact JSON body. Verify the signature before parsing or acting on an event, and deduplicate by event ID.
Verification messages belong to the associated activation. Android notifications use private lock-screen visibility. Do not share OTPs, full SMS content, passwords or recovery codes.
The Android app downloads updates through the official Numelixa domain, checks that the downloaded file is a valid APK and verifies the SHA-256 digest when the release provides one.
Use a unique password, keep API keys server-side, review unfamiliar sessions and never send OTPs or passwords to anyone claiming to be support.