Add Powered by Custd

Use a normal link when a product or website uses Custd and you want to identify the service. The smallest recommended version is text only:

<a href="https://custd.com/?ref=your-project&amp;source=powered-by">
  Powered by Custd
</a>

Replace your-project with a short, non-personal project slug such as example-app. Keep source=powered-by unchanged. Do not put a user ID, email address, tenant ID, or other personal or secret value in the URL.

When the visitor opens Custd, the browser tracker records only a valid project slug and the fixed powered-by source for aggregate attribution reporting. It does not retain the full query string. Consent and Do Not Track settings still take precedence, so attribution is best-effort.

The destination accepts attribution query parameters but publishes https://custd.com/ as its canonical URL. The link must remain an ordinary crawlable <a href>; do not replace it with JavaScript navigation or a tracking redirect.

Add the optional Custd icon

The public Custd icon is available at https://custd.com/icon-192.png. When visible text is present, treat the icon as decorative so assistive technology announces the link once:

<a href="https://custd.com/?ref=your-project&amp;source=powered-by">
  <img
    src="https://custd.com/icon-192.png"
    width="20" height="20" alt="" aria-hidden="true"
  />
  Powered by Custd
</a>

You may copy the icon into your own repository if the attribution must render without a request to Custd. Do not alter the icon, use it without the Custd name, or make it the only accessible content of the link.

React example

React escapes the query string when it renders the link, so use the normal & character in JSX:

<a href="https://custd.com/?ref=your-project&source=powered-by">
  <img
    src="https://custd.com/icon-192.png"
    width="20"
    height="20"
    alt=""
    aria-hidden="true"
  />
  Powered by Custd
</a>

Consumer responsibilities

The consuming project owns where the link appears and how it matches that product's interface. Before publishing it:

keep Powered by Custd visible, or provide that exact accessible name if space genuinely prevents visible text;
verify keyboard focus, contrast, mobile layout, and the link destination in the consumer's rendered interface;
use one repository-local test at the existing footer or attribution owner; and
confirm the project is allowed to state that it uses Custd.

No Custd script, stylesheet, package, account signup, or runtime API call is required to add the attribution.