Avatar Embed Launch Checker

How to use Avatar Embed Launch Checker

Before embedding a conversational avatar, make the allowed origin and human authorization/fallback declarations explicit. This creates a bounded launch checklist, not a security scan.

1. Enter only approved named public HTTPS origins where the embed will appear.
2. Declare the embed URL, necessary device permissions, consent/rights status and actual fallback-test outcome.
3. Resolve held entries, then inspect real browser behavior, contracts, notices and client approval separately.

Good to know

• Only URL syntax and entered origin equality are checked. URLs are never opened; DNS resolution, CSP, actual permission policy and remote response content are unverified.
• Credentials, IP literals, non-HTTPS URLs and local/private-style suffixes are refused. A public-looking hostname can still resolve privately; passing is not an authorization or safety certificate.
• Each field is limited to 8,000 UTF-16 characters; CSV inputs use the exact displayed header and at most 100 data rows. Quoted commas, doubled quotes and quoted newlines are supported. Empty/duplicate identities, unsupported controls and unpaired surrogates are refused.
• Exports are editable review records. Spreadsheet-like text is apostrophe-prefixed in CSV to reduce formula execution risk; inspect your actual spreadsheet/import settings before sharing.
• Everything runs locally in your browser. No AI model, upload, provider account, calendar, call, video render, automatic outreach, publication or saved input. Enter only information you are authorized to process; declarations remain unverified.