Security & Embed Integrity

Each site integration has a generated token and server-side domain allowlist. The token appears in publisher page HTML and should be treated as an integration identifier rather than an account password.

BetterLink validates site context before applying publisher settings, localization, or click tracking. Requests that fail validation may be rejected or sent to a safe direct destination. Publishers can rotate integration tokens from the dashboard.

Smart Router v2 can include the current source page when a link is clicked so BetterLink can report where a placement pointing to a currently Unavailable product needs repair. Before storage, BetterLink verifies the integration owner and allowed hostname and removes credentials, query strings, and fragments. Source locations are aggregated only while that Amazon Product Health observation is current and are not tied to a visitor identity.

BetterLink serves its hosted embed script over HTTPS from version-controlled releases. The hosted script URL updates automatically when a new release ships, so publishers never need to change their snippet.

Every release also stays served as an immutable versioned file (for example /smart-router-v2.js) whose bytes never change once published, so existing installs that pin a version with a Subresource Integrity hash keep working. Publishers who want full control over the code that runs on their site can self-host a reviewed copy of the script, loaded as its own script tag with smart-router kept in the file name, and point it back at BetterLink with its data-api attribute.

The Smart Router preserve-mode proxy accepts supported Amazon destinations and rejects non-Amazon destination parameters. A separately created managed BetterLink may point to a stored Amazon URL or another validated HTTP(S) destination. Because the destination is stored by the account owner rather than supplied as an unrestricted redirect parameter at click time, managed links are not general-purpose open redirects. Invalid, unknown, blocked, or unavailable requests may fall back, return an error, or return a not-found response.

BetterLink applies rate limits, origin and ownership checks, input validation, logging, and operational alerts to relevant integration and account endpoints. These controls are designed to reduce abuse and aid investigation, but no security control or monitoring system eliminates all risk.

If you believe you've found a security issue, please reach out via our contact page so we can review it. A machine-readable pointer is published at /.well-known/security.txt.