Skip to content
Console
Try one

    Private Beta Guide

    Know what to expect, what Thalovant measures, how to get help, and how to leave the invitation-only private beta.

    Use this guide after you receive a private-beta invitation. The beta is invitation-only; this page isn’t a self-enrollment form.

    Your invitation should name the feedback contact, explain the current beta purpose, and link the consent summary that applies to your participation. Ask questions before you accept. Keep a copy of the invitation and consent summary for your records.

    Participation is optional. You can stop participating or ask for account deletion through the invitation contact or the normal support route.

    1. Accept the invitation and create your account. Use the normal registration, verification, sign-in, and two-step security flow.
    2. Choose one real goal. Try a public hub, create a private setup, connect a client, or use an SDK path that matches why you joined.
    3. Complete one useful interaction. Account creation alone isn’t first value.
    4. Check what the product shows. Review Dashboard, status, limits, Billing, and the owner page for what you used.
    5. Return on another day. A later useful activity helps show whether the product remains useful after setup.

    Start with First Setup or the First Successful Setup if your invitation doesn’t name a more specific route.

    The beta uses aggregate, privacy-safe milestones such as registration, onboarding, first value, successful return activity, latency, errors, support load, and reliability. The activation measurement doesn’t store prompts, replies, memory content, email addresses, tokens, credentials, or secret material in milestone metadata.

    Thalovant keeps the invitation and consent record in a restricted operational system. The repository evidence used for release decisions contains only random participant IDs, timestamps, aggregate counts, accountable owner roles, and opaque evidence references.

    Account copy

    Download your retained account data from Profile before deletion if you want a copy.

    Safe support

    Share the page, goal, visible status, and request ID—not tokens, setup links, connection files, or private content.

    Stop anytime

    Contact the invitation owner or support to withdraw, request deletion, or ask what evidence remains restricted.

    Use Get Support for setup, access, billing, runtime, or reliability questions. Mention that you’re in the private beta and use the pseudonymous case reference provided by support. Never post passwords, API keys, recovery codes, payment details, private customer data, prompts, replies, setup links, or connection files.

    For a broad outage, check the visible status information before changing your setup. For a security, privacy, account-takeover, cross-tenant, or unsafe-response concern, stop the affected activity and contact the invitation owner or support immediately.

    1. Contact the invitation owner or support and say whether you want to withdraw only or also delete the account.
    2. Download an account export from Profile first if you want a retained copy.
    3. Use the normal account deletion action. Deletion also erases linked activation and product telemetry associated with the account.
    4. Ask the invitation owner to confirm that your pseudonymous record is no longer used as active cohort evidence.

    Read Profile and Security for the export, retention, session, and deletion behavior.

    Set it up Prepare a support request