Security
What a site with a Content-Security-Policy must allow, the microphone, where the widget may appear, and what keeps visitors' calls in bounds.
Content-Security-Policy
A site that sends a Content-Security-Policy needs our address in these directives:
script-src https://talk.madein10.com
connect-src https://talk.madein10.com
img-src https://talk.madein10.com
media-src https://talk.madein10.com
frame-src https://talk.madein10.com
font-src https://talk.madein10.comfont-srcis only needed on Persian or Arabic pages (the widget loads a font for Arabic script there).img-srcalso covers your own uploaded launcher icon.- No
'unsafe-inline'or'unsafe-eval'is needed: the widget's styles are a constructed stylesheet.
Add these to the directives you already have; don't replace them. talk.madein10.com is a placeholder address that will change when the product has its name.
The microphone
The call runs in our page, inside the panel's iframe, and needs the microphone there. A site that sends Permissions-Policy: microphone=() must allow it for us, or the call can't hear the visitor:
microphone=(self "https://talk.madein10.com")Where the widget may appear
- Only on your deployment's sites. The widget first asks us for its settings; the answer can be read only by a site the key allows, so on any other site (or with a revoked key) nothing shows. The answer is never cached, so revoking a deployment takes the widget down on the next page load.
- Only framed by your sites. The call's page is served with
frame-ancestorsset to the deployment's sites only. - Nothing private is in the page. A publishable key (
pk_…) is made to sit in a web page. It can only start calls with its one character, on its sites, within its caps. Your deployment's note, sites and caps are never sent to visitors. Secret keys (sk_…) never belong in a page.
Caps are the real protection
A script outside a browser can claim to be any site. What stops it from running up calls is the deployment's caps, checked on every call:
| Check | What happens past it |
|---|---|
| The key | A revoked or wrong key: no widget, no call |
| The site | A site the deployment doesn't list: refused |
| 20 calls a day per network address and deployment | Refused |
at_once, per_day, daily_spend_usd | Busy |
per_visitor_per_day | The visitor has used their calls for today |
max_call_seconds | The call ends at that length |
Visitors' calls are charged like any call, so set the caps to what you're happy to pay for. The defaults are 180-second calls, 3 a day per visitor, 2 at once and 50 a day, with no spending cap (Install).
Visitors only ever see "busy"
Anything about your balance, prices or our service is answered to the visitor as busy, never as the reason. They see your deployment's busy message, or ours ("busy right now"). Your organization's own limit on calls at once (10 unless we raised it for you) counts the widget's calls too.
Between your page and the call
The call runs in our page, inside the panel's iframe. Your page and ours talk only through postMessage, checked both ways: the widget takes messages only from the frame's own window at our origin, and our page takes them only from its parent window at your site's origin, which must be one of the deployment's sites. Our page sends tool calls and the transcript only to that exact origin (never *), and only once the call has started there. What your page sends back (a tool's answer, the context) is the visitor's browser speaking: at most 4 KB and 1,000 characters, and the character is told it's from the page, never instructions.
A bot check
An invisible check that a real person's browser pressed Talk, verified before a widget call starts, per deployment. It's built but not switched on yet. It will need nothing from your site: the check runs in our call page and shows itself only if it needs a click.