Server-side verification. Encrypted token vault. No API key on the client.

Tierux verifies Google Play purchases server-side through Google Play's Android Publisher API. Apple signed-JWS and certificate-chain validation verifies App Store transactions, while App Store Server Notifications drive subscription lifecycle sync. Client results are untrusted; Tierux derives normalized entitlement state from verified store data. Apple App Store support is implemented with limitations — see platform support.

Raw purchase tokens are never stored on disk. Tierux stores a SHA-256 hash of the token for deduplication and an AES-256-GCM encrypted copy so it can re-verify the purchase against the store on renewal or recovery. The raw token itself is never persisted — only its hash, the encrypted copy, and the normalized entitlement state (active/expired/grace).

No. Tierux uses an identity token + backend proxy pattern. The client SDK sends the purchase to your backend, which forwards it to Tierux with your server-side API key. The spe_ key never ships to a device and never appears in client code.

Purchase tokens are encrypted with AES-256-GCM before being stored. API keys are stored as SHA-256 hashes only — the plaintext is never persisted or logged. All API communication is encrypted in transit over HTTPS/TLS. RTDN webhooks are authenticated via Google-signed JWTs.

Yes. Your subscriber list, entitlement state, and purchase history are always accessible via the Tierux REST API — no vendor approval required, no export queue, no lock-in. Your data stays portable.

Tierux is pre-launch and has not yet completed formal compliance certification. We design for security from the start — server-side verification, no raw token storage, encrypted vaults, and no client key — but independent certification is a future milestone we'll publish when complete.