Publisher Agreement

1.1 Content Requirements

To qualify as a CyberAdX Network publisher, your property must:

• ›Publish content primarily relevant to cybersecurity, privacy, enterprise technology, compliance, or adjacent professional topics
• ›Maintain a professional editorial standard consistent with a B2B audience of security practitioners, CISOs, compliance officers, and enterprise IT professionals
• ›Not be directed at children under 13 or operate in categories prohibited under the Advertising Policy
• ›Be owned and operated by a legal entity capable of entering into a binding agreement

1.2 Traffic & Quality Standards

• ›Minimum 500 monthly unique visitors at time of application (exceptions considered for high-quality niche properties)
• ›Traffic must be substantially human — properties with bot-heavy traffic profiles will be declined or removed
• ›No traffic purchased from incentivised traffic networks, click farms, or pop/redirect traffic sources

1.3 Application & Approval

All publishers must apply and receive written approval before integrating the Pixel. CyberAdX reserves the right to approve or decline any application at its sole discretion. Approval of one domain does not automatically extend to subdomains or related properties.

3.1 Required Components

Publishers must integrate the following components exactly as documented:

• ›p.js — Page analytics script, loaded via the /px/ same-origin proxy
• ›cax-slots.js — Ad carousel script, loaded deferred from /public/
• ›CyberAdXPlacement component — One instance per ad zone, with correct data-zone, data-format, and dimensional attributes
• ›functions/px/[[path]].js — Cloudflare Pages Function proxying /px/* to px.cyberadx.network

3.2 Prohibited Modifications

• ›Publishers may not modify, decompile, or create derivative works of pixel code
• ›Publishers may not inject additional ad calls, redirect pixel requests to third-party endpoints, or load the pixel from domains other than the approved property
• ›Publishers may not deploy the pixel on domains not listed in their approved sellers.json entry
• ›Publishers may not disable or circumvent the Turnstile bot-filtering step

3.3 Zone Configuration

Ad zones are defined in the CyberAdX admin system and must be implemented per the specifications provided during onboarding. Zone IDs, formats, and dimensional constraints must match the approved configuration exactly.

3.4 ads.txt Requirement

Publishers must maintain the following entry in their property's ads.txt file, using their specific seller ID (as assigned during onboarding and listed in sellers.json):

Removal of this entry, or addition of competing ad networks without prior written approval from CyberAdX, may result in immediate suspension from the Network.

4.1 Editorial Independence

CyberAdX does not control publisher editorial content. Publishers retain full editorial independence. However, publisher content must not:

• ›Promote illegal activities, offensive hacking tools, or services designed for unauthorised access
• ›Contain malware, phishing content, or deceptive download prompts
• ›Engage in content farming, AI-generated content without editorial review, or mass scraping of third-party content without attribution
• ›Target or knowingly collect data from children under 13
• ›Defame individuals or organisations with unsubstantiated claims

4.2 Copyright Compliance

Publishers are solely responsible for ensuring their content does not infringe third-party intellectual property rights. Publishers agree to maintain a DMCA/copyright complaint process or designate CyberAdX as their DMCA notification point of contact, in which case CyberAdX's DMCA policy applies.

4.3 Sponsored Content Disclosure

All CyberAdX display ad units are rendered by the pixel with a "Sponsored" label or aria-label attribute. Publishers must not obscure, remove, or modify these labels. Sponsored articles must carry clear disclosure labels per the Advertising Policy.

5.1 Revenue Share Structure

Revenue share percentages are defined in each Publisher's individual onboarding documentation or supplemental agreement. The standard network revenue share model applies as follows:

5.2 Reporting & Dashboard Access

Publishers receive access to a reporting dashboard showing: impressions, clicks, CTR, campaign breakdown, zone performance, and estimated revenue. Reports are updated on a rolling basis from D1 event logs.

5.3 Payment Schedule

Publisher revenue payments are processed monthly, with a minimum payout threshold of $50. Balances below threshold roll forward to the next month. Payment is via ACH or wire transfer; publishers are responsible for providing accurate banking details.

5.4 Revenue Disputes

Publishers must raise revenue disputes in writing within 30 days of the relevant reporting period. CyberAdX's D1 impression and click logs are the authoritative record. CyberAdX will investigate and respond within 15 business days.

7.1 Term

This Agreement is effective from the date of written approval by CyberAdX and continues until terminated by either party.

7.2 Termination by Publisher

Publishers may terminate this Agreement with 30 days' written notice to [email protected]. Upon termination, the publisher must remove the Pixel code from their property and remove the CyberAdX entry from their ads.txt.

7.3 Termination by CyberAdX

CyberAdX may terminate this Agreement immediately, without notice, for:

• ›Violation of these terms, the content standards, or the pixel integration requirements
• ›Fraudulent traffic, click farming, or impression stuffing
• ›Sustained low traffic quality resulting in high IVT rates
• ›Failure to maintain required ads.txt entries
• ›Any legal or regulatory action against the publisher property

For material but non-fraudulent violations, CyberAdX will provide 14 days' notice and an opportunity to cure before termination.

7.4 Effect of Termination

Upon termination: (a) domain is removed from the allowlist within 24 hours; (b) pending revenue payments for verified impressions/clicks prior to termination will be paid on the normal schedule; (c) publisher data in D1 is retained for 90 days then deleted per standard retention policy.