REDTRAFFIC ADVERTISER & PUBLISHER GUIDELINES
(Issued by XXX LLC, Colorado, USA)
Effective Date: October, 2025
PART I — ADVERTISER GUIDELINES
1) Ads Transparency for EU End‑Users (DSA)
Advertisers are responsible for ensuring their campaigns comply with all applicable laws in every location where ads appear, including the EU Digital Services Act (DSA). To meet the DSA’s Ad Transparency obligations and help EU end users identify the advertiser behind an ad, Redtraffic will display transparency information extracted from data provided by the advertiser under the advertiser’s sole responsibility.
What will be shown to EU end users:
The name of the natural/legal person or business on whose behalf the ad is presented; and, when different, the person or entity who paid for the ad.
Meaningful information about the main parameters used to determine why the ad was shown to that user (e.g., targeting criteria).
Notes: Campaign approval/rejection is at Redtraffic’s sole discretion. Active campaigns are continually reviewed and may be stopped at any time without prior notice.
2) General Rules for All Advertising Campaigns
No malware/phishing, browser lockers, scareware, forced redirects, or auto‑downloads.
No deceptive claims, fake chat requests, misleading push‑subscription flows, or imitation of native OS/system alerts.
No infringements of third‑party IP/trademarks, or use of celebrity images without permission.
No adult/sexual content targeting markets where prohibited by law (e.g., local prohibitions).
Animated elements must not flicker or blink; image/text rotations should not switch faster than ~1 change per 2 seconds.
Auto‑sound is prohibited for display/video (unless clearly permitted for specific formats).
All creatives (gif/png/jpg/mp4 display banners) should be ≤150 KB per file where feasible; heavier assets may be rejected at Redtraffic’s discretion.
Popunder: products/apps must not auto‑redirect to app stores or open apps without user action.
No deepfake/faceswap/undressing apps. Crypto/forex/binary are restricted and subject to prior approval.
Banners/landing pages must be 18 U.S.C. §2257 compliant where applicable.
3) Specific Rules — Mainstream Category (and Sub‑Categories)
No visible nudity (no nipples/genitals).
No pornographic wording.
Suggestive content (e.g., bikini focus, provocative poses, or dating content oriented to sexual encounters) will be categorized as “SEXY” and may be blocked by some mainstream publishers.
4) Specific Rules — In‑Stream Video (VAST)
Video duration: minimum 10 seconds, maximum 30 seconds.
Skip behavior: if using a VAST link, set the skip button to 5 seconds.
Creative format: MP4 is recommended for broad player compatibility.
Quality: video must be easily viewable and match the product/offer shown on the landing page.
Rights: advertiser must own or be authorized to use all materials in the video; proof may be required.
Redtraffic may reject any in‑stream campaign at its sole discretion.
5) Specific Rules — Native Advertising
Global Native specs (subject to change):
Images: 300×300 (PNG/JPEG).
Native videos: ≤1.5 MB, 16:9, ≤10 seconds; sound off in thumbnails.
No borders/margins; landing page should present real content (e.g., article/tutorial/blog).
Adult Native specifics:
Simple pictures only; no overlays (logos/watermarks allowed only for video thumbs if applicable).
No design elements like buttons/arrows/split images; images must be adult/sexy in nature (non‑adult dating profiles may be accepted).
Mainstream Native specifics:
No nudity (bikini only).
No sexual/vulgar text.
Minimal design elements (e.g., small text, buttons, split images, arrows/circles/logos) can be accepted within reason.
6) Specific Rules — Push Notification / Instant Message Advertising
No misleading titles/text (e.g., fake chat requests).
Banner image: 720×480 or 192×192 (JPEG/PNG/GIF).
Title length: up to ~30 characters; Description: up to ~40 characters (browser limits may vary).
No looping/browser‑locking behaviors; no forced subscriptions.
7) Technical & Creative Requirements (All Formats)
HTTPS delivery for creatives and landing pages is required.
Autoplay with sound is prohibited; sound must be user‑initiated.
A visible, working close/skip control is required for interstitials/video where applicable.
Creatives must not degrade user experience, block navigation, or simulate system warnings.
We reserve the right to request source files or proofs of rights and to remove/ban creatives that fail compliance checks.
8) Enforcement & Penalties
Redtraffic may suspend, pause, or terminate campaigns/accounts at any time for violations.
Funds may be withheld where fraud, malvertising, or policy breaches are detected.
Repeat or severe violations may lead to permanent bans and notification of compliance partners.
By submitting any creative or campaign to Redtraffic, you agree to comply with these Guidelines and acknowledge that violations may result in immediate suspension or termination.
PART II — PUBLISHER GUIDELINES
1) Ads Transparency for EU End‑Users (DSA)
Publishers must comply with the DSA. Except for micro/small enterprises that are not designated as very large online platforms under the DSA, publishers must ensure that EU end users can clearly identify, in real time, that a specific placement is an advertisement via prominent markings and that ad transparency fields are displayed as required (advertiser identity and meaningful information about targeting parameters).
2) General Publisher Rules
Websites must comply with IP/copyright/trademark laws and have a working DMCA/DSA copyright notice and contact.
Adult sites must comply at all times with 18 U.S.C. §2257 and display a valid compliance statement.
No illegal content/keywords; no promotion of illegal activities (e.g., rape/incest/drug use/hacking).
No incentive traffic (PTC/PTR etc.) and no artificial generation of impressions or clicks.
Sites under construction, thin‑content pages, or sites with excessive ad density may be rejected.
Shared/free‑hosting domains may be rejected for quality/security reasons.
Zones and scripts must not inject unauthorized redirects, cloaking, or code that harms user experience.
3) In‑Stream Video Publishing Rules
We recommend enabling a skip button after ~5 seconds and placing it clearly at the bottom‑right.
Apply reasonable frequency capping (e.g., 1 hour).
Ad should pause on click and resume on click; stop when the viewer leaves the page.
Autoplay is not accepted; ads should load/play only when the user clicks play on the site’s video (industry standards).
On mobile, keep the user in the browser—do not force full‑screen that prevents clicks.
Ensure implementation quality so clicks/views are accurately tracked; incorrect implementations may be declined.
4) Outstream Publishing Rules
Place Outstream between content (not at the very top). Below‑the‑fold placements often perform better; on mobile, around the middle of content is recommended.
Use the provided code rather than custom players to preserve viewability and CTR; custom implementations may be rejected.
Playback should start only when ~50% of the unit is in view; pause when it leaves view; resume upon return.
Use responsive width (100% of container) and avoid height restrictions to maintain aspect ratio.
We recommend keeping default branding (e.g., “Ads by Redtraffic”) to improve engagement quality.
Ensure implementation accuracy; we may decline incorrect setups.
5) Publisher Payments
Publishers must keep ad zones active at the time of payout requests.
Eligibility, payment methods, fees, and withholding rules follow Redtraffic’s Terms (see Payments to Sellers).
Payments may be withheld in cases of fraud, invalid traffic, or policy breaches as described in the Terms.
6) Monitoring & Account Actions
We regularly audit sites and zones. Non‑compliant properties may be paused or removed without prior notice.
In severe cases, accounts may be closed and unpaid balances forfeited where permitted by the Terms and applicable law.
PART III — LEGAL & CONTACT
1) Legal Disclaimer
XXX LLC shall not be held liable for any damages, losses, or legal costs arising from advertisers’ or publishers’ violations of these Guidelines or applicable law. Each user of the Redtraffic platform is solely responsible for ensuring compliance with all applicable regulations, and agrees to indemnify and hold harmless XXX LLC, its officers, and affiliates from any resulting claims, penalties, or liabilities.
2) Jurisdiction
These Guidelines are governed by the laws of the State of Ohio, USA. The courts of Cuyahoga County, Ohio, have exclusive jurisdiction over disputes that are not subject to arbitration, as further described in the Terms.
3) Updates
We may update these Guidelines to reflect changes in technologies, standards, or law. Updates will be posted on redtraffic.com. Continued use of the platform constitutes acceptance of the revised version.
4) Contact
XXX LLC Address of LLC Broomfield, CO 80023 United States Email: help@redtraffic.com
