Designed with publisher control in mind.

Publishers explicitly authorize their sites

A connection is initiated by a WordPress administrator or publisher. Before it is approved, the publisher reviews the target site, confirms that they have authority to connect and monetize it, and accepts the applicable Publisher Terms and participation agreement.

Authorization is site-specific. Connecting one site does not automatically authorize another property.

Site credentials can be revoked

A connected site receives a credential used for communication with the SilentAds service. The plugin does not display that credential in its normal interface.

Disconnecting revokes the site connection and requires the publisher to complete the connection flow again before reconnecting. Publishers can separately pause monetization without disconnecting the site.

What the WordPress integration uses

SilentAds uses limited site and content information needed to establish the publisher connection and evaluate eligible published content. Verified categories currently include:

• site URL and hostname, site name, site or publisher identifiers, plugin version, enabled or paused monetization state, and values needed to authorize and operate the connection;
• eligible post or page URL, title, excerpt, published text content, categories, tags and site locale for contextual matching;
• match decisions and operational information needed to return or cache a result, diagnose faults, maintain the service, prevent abuse and support security.

Ordinary infrastructure and server logs can contain technical request information such as IP address, timestamp, requested resource and user-agent information. The Privacy Policy provides the fuller account of personal-data handling.

The publisher plugin stays lightweight

The current WordPress plugin does not introduce visitor analytics, fingerprinting, tracking pixels or automatic affiliate redirects merely by being installed.

Commercial or affiliate tracking belongs at the appropriate intentional commercial action and may be subject to the applicable provider or programme requirements. This does not mean that ordinary web infrastructure can never produce technical server logs.

Matching decisions are cached

Match decisions may be cached to avoid unnecessary repeated processing. Matching is associated with eligible editorial activity and scheduled processing rather than ordinary visitor page views.

Publishers can pause monetization while remaining connected. The plugin also provides diagnostics and maintenance controls, including a public service reachability check and a separate match-cache clear action.

Report a security concern

If you believe you have identified a security issue affecting SilentAds, please contact support@silentads.ai with enough information for us to understand and reproduce the issue.

Where practical, include:

• the affected URL or component;
• steps to reproduce the issue;
• the effect you observed;
• relevant timestamps.

Current security posture

SilentAds does not currently claim third-party security certifications or formal compliance attestations that we have not obtained. Product availability should not be read as a claim of a certification that is not listed here.