Legal Center
Policies for a customizable companion platform.
These pages explain how Amadeuz accounts, subscriptions, generated responses, memory, user-created companions, custom voice uploads, ratings, and reports are handled.
Terms of Service
The rules for using Amadeuz, creating companions, chatting with public or private personas, and using voice and memory features.
Read TermsCreator responsibility
Creators are responsible for the companion names, descriptions, knowledge, images, and custom voice uploads they submit. Custom voice uploads require rights confirmation.
Reports and moderation
Public companions can be rated and reported. Amadeuz may review, restrict, unpublish, or remove companions that violate policy or user rights.
Billing and access
Paid plans add private/unlisted companion creation, higher knowledge limits, larger message allowances, and priority. Custom voice upload and avatar customization are available on every plan.
View plansCookies and growth measurement
Essential storage keeps the service working. A consent-independent first-party count measures browsers, not people: the API sets an opaque HttpOnly cookie and keeps only its HMAC for up to 400 days. It has no URL, query, account link, IP address, browser user-agent, or fingerprint, and is not shared with third parties. Browsers that block analytics or run without JavaScript are not measured. We may also count TikTok-labelled landing requests in a non-identifying daily aggregate. With active optional consent, TikTok can receive a PageView only from the public homepage or plans/pricing page, after query strings and fragments are removed. With explicit Allow growth measurement consent, TikTok may also receive server-side reports of real Stripe Checkout Session starts and Stripe-verified initial paid subscription purchases. Those reports are limited to a click ID when present, IP address, browser user-agent, random event ID/time, plan, value, currency, and the generic public /plans URL. TikTok receives no emails, names, account IDs, card data, chat or bot content, sensitive URLs, or recurring-renewal events; withdrawing consent suppresses pending reporting. The internal Plans count uses an opaque first-party cookie and purpose-separated HMAC with no URL/query/referrer/IP/user-agent/account data, while checkout starts use a separate account HMAC never sent to TikTok.
Read the full cookie and measurement description in the Terms, including separate first-party statistics, limited TikTok sharing, retention, and withdrawal.