Ad Policy

FOBA Site Suite supports AdSense-ready infrastructure, but ads are not a substitute for the educational mission. Public ad rendering is owner-controlled and should stay disabled until disclosure, privacy, consent, and placement review are complete.

Current status

Infrastructure wired; visitor rendering gated. Admins can configure a publisher ID and future manual slots, but public rendering depends on explicit owner settings and should be reviewed before promotion.

Placement rules

• Ads must be clearly labeled and visually separate from navigation, forms, video play buttons, contribution CTAs, and source-review actions.
• Ads should appear only after the page gives visitors the learning frame, identity disclaimer, and privacy context.
• Avoid high-density ads on sensitive pages, including safe-sharing, source-review, claim-review, fact-check intake, community-note intake, corrections, privacy, and pages discussing DNA or identity-sensitive interpretation.
• Auto Ads should stay off until mobile placement, page speed, privacy consent, and accidental sensitive-page placements are reviewed.
• No ad language should invite, reward, or pressure visitors to click ads.

Privacy rules

• Do not send personal emails, form details, raw DNA data, or living-person information in ad or analytics URLs.
• Review cookie, consent, and privacy notices before enabling any third-party ad code.
• Prefer non-personalized or privacy-protective treatment where practical.
• Keep public submissions and review workflows separate from ad targeting or sponsor reporting.

Recommended slot posture

Use a low-density, manually reviewed slot plan. Do not place ads next to identity disclaimers, forms, source-review workflows, safe-sharing warnings, or fact-check decisions.