Widget Embed Policy

1. How embedding works

You add a single script tagto your website. That is the only change required on your server or in your site's codebase. You do not host the widget files, upload assets, or maintain a separate configuration outside LinkToast.

The script loads our widget loader, which inserts the widget (via an iframe) next to where you placed the tag. Layout, branding, and content all live in LinkToast Studio. You do not manage them on your site.

After this one-time install, you never need to edit your site again for widget updates. When you publish changes in Studio, the same embed code keeps working; visitors always see your latest published version.

2. Installation snippet

Copy the snippet from Studio after you publish (or from the Code button). It looks like this:

<script src="widget-loader.js" data-widget-id="YOUR_WIDGET_ID" async></script>

• src must point to the hosted widget-loader.js URL we provide (your copied snippet already uses the correct value for your environment).
• data-widget-id is your widget ID.
• async keeps the rest of your page loading smoothly.

Paste the snippet into your page HTML where you want the widget. Putting it just before </body> works well.

3. What you do not need to do

• No extra CSS or JavaScript beyond this one line
• No placeholder <div> or manual iframe markup
• No self-hosting of the loader or widget bundle
• No per-site configuration files. Edit everything in Studio and it ships when you publish.

4. Purpose of the widget

The widget lets you display your partner network (logos, brands, and relationships) on your own site through this lightweight embed. It stays within its own frame and does not rewrite your page outside the widget area.

5. SEO and search engine compliance

To align with common guidance for embedded widgets, links inside the widget experience are handled so outbound connections follow practices such as rel="nofollow noopener noreferrer" and target="_blank" where appropriate.

This helps limit unintended SEO side effects from third-party links shown inside the widget.

Behavior is applied as part of the published widget experience.

6. Security principles

The integration follows common browser security practices:

• noopener / noreferrer on external navigation where applicable
• Isolated presentation via the embed so your page markup outside the widget is not modified by the widget code you add
• No requirement to run arbitrary scripts from your side beyond the single loader line we document

7. Data policy

The embed is designed so that:

• End visitors are not asked to sign in through the snippet itself
• The loader does not exist to fingerprint users or set marketing cookies
• Visual assets (e.g. logos) may load as part of displaying your published widget content

Broader privacy terms for the LinkToast product are covered in our main policies.

8. Performance

• The script loads asynchronously
• The widget iframe uses lazy loading where supported
• Small loader footprint; no heavy client framework required on your site

9. Updates and versioning

You keep the same embed code. Publish a new version in Studio and visitors see the update. You do not need to redeploy your snippet.

If we ever need a breaking change to the embed contract, we will communicate it in advance and document migration steps.

10. Support

If you discover unexpected behavior, please contact:

support@linktoast.com