Last updated: August 17, 2026

These terms govern use of the AStack website, dashboard, APIs, SDKs, session runtimes, and rendered-character services.

AStack creates authenticated conversational-AI sessions that can accept voice, text, and image input and return generated speech plus a rendered Unreal character stream.

• A server SDK creates sessions using a private API key.
• A browser SDK connects with time-limited session credentials.
• The session runtime coordinates ASR/VAD, language generation, Qwen3-TTS, Runtime MetaHuman Lip Sync, and UE Pixel Streaming.
• The control plane records session, usage, billing, error, and performance metadata.

• Provide accurate account information and keep your authentication credentials secure.
• Keep API keys on trusted servers; do not embed them in browser or mobile application code.
• Use session credentials only for the session and end user for which they were issued.
• Revoke exposed keys and report suspected unauthorized access through the support form.
• You are responsible for your application, end-user notices, consent flow, and the content sent through your account.

Do not use AStack to break the law, violate another person's rights, bypass access controls, disrupt the service, distribute malware or spam, or create non-consensual impersonation or synthetic media.

• AI output can be inaccurate, incomplete, delayed, or unsuitable for a particular purpose.
• Review output before relying on it or presenting it as factual.
• Performance depends on the selected runtime, model state, network path, browser, and input.
• No public uptime or latency SLA currently applies unless a separate written agreement says otherwise.
• The public status page does not currently publish real-time service telemetry.

You authorize AStack and its runtime providers to process submitted content as required to run the requested session. You remain responsible for having the rights and permissions needed to submit that content.

AStack may change the service, models, runtime provider, limits, or pricing. Material account-facing changes should be reflected in the dashboard or these published pages before they take effect for new usage.

Questions about these terms can be submitted through the support form.