What we check before installation
The host must support the required server components, a protected place for application data, and the routes used to deliver the toolbar and save preferences. The website’s security policy must allow its own required assets and requests. Changes to caching, compression, or minification should be checked against the actual runtime.
Use a staging copy for installation testing where possible. Confirm the launcher on desktop and mobile, save a visitor preference, open another page, and start a new browser session to verify restoration. Submit a report and verify that the website owner can retrieve it.
A script field is only one part of the picture
A website builder may allow a JavaScript snippet while preventing the server-side components needed for client-hosted storage. That is why a universal paste-only promise would be misleading. Platform names alone do not describe every plan, hosting arrangement, or customization restriction.
Tell us about your website and the tasks your visitors need to complete. We can use that information to determine the appropriate installation path.