Ad Policy
Keep ads separate from trust, safety, and claim review
AdSense infrastructure is gated by owner review, privacy review, consent review, mobile placement review, and public disclosures.
What this page adds
- It explains how ads are constrained so they do not overwhelm educational reading or sit next to sensitive research workflows.
- It gives readers a public standard for judging whether monetization is being used carefully or carelessly.
- It shows that ad readiness is not the same thing as permission to publish ads everywhere.
What a careful reader should leave with
You should leave knowing where ads do not belong, what review steps have to happen first, and why trust, privacy, and claim-review surfaces stay more important than monetization.
Ad activation checklist
- Confirm the publisher ID, ads.txt status, and owner setting before any public ad rendering is enabled.
- Review mobile placement, page speed, consent/privacy language, and accidental placement beside trust, intake, or identity-sensitive content.
- Record the pages where ads are allowed, the pages where ads are excluded, and the rollback action if ads appear in the wrong context.
- Confirm that disabled ads render no visible public ad box and no manual display unit.
- Confirm ads do not imply endorsement of public claims, source-review outcomes, identity language, ancestry, descent, legal status, DNA conclusions, tribe, nationality, membership, spiritual interpretation, or oral tradition.
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 manually reviewed slots, but public rendering depends on explicit owner settings and must be checked before promotion. While disabled, public pages should render no visible ad boxes.
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.
- Disabled ads must not leave visible public ad boxes, empty ad frames, or manual display units.
- Ads must not imply endorsement of claims, sources, identity language, ancestry, descent, legal status, DNA conclusions, tribe, nationality, membership, spiritual interpretation, or oral tradition.
- 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.
- Do not enable personalized ads for EEA, UK, or Switzerland visitors unless a consent/CMP workflow is configured and reviewed.
- 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.