Compliance Toolkit

Pre-submission checks, whitelist documents, and BOV declarations — one place.
!
Fill the fields, attach the files, press the button — the check runs and the document comes back right here (30–90 sec). Hard rules (GEO lists, bans) live in the backend knowledge snapshot and policy sources, not in this page. Results are drafts: final review stays with Compliance.
White-list Document CheckerQuick check of the site and documents before a certification submission
The exact domain that goes into the application. A redirect to another domain at review time = rejection.
Each platform has its own access mechanism: certification / written permission / rep allowlist.
Availability depends on the platform — impossible combos are stopped before any site check.
Validated against live policy / KB lists for the chosen platform + vertical — only eligible markets pass the gate.
Licences, LegitScript / G2 certificates, registration docs, agreements. Attach the same files in the chat.
Document Composer for WLNeutral supporting documents for whitelist / certification applications
Affects checks only, not branding. Default: platform-neutral.
For casino listings: Casino brand · Offer URL · Licence holder · Licence URL. Licence links must point to the official regulator registry.
No agency branding by default — Point2Web appears in a WL document only if you explicitly ask for it here.
BOV Declaration BuilderGoogle Business Operations Verification — consolidated one-file PDF
From the account header. The same ID is injected everywhere in the document automatically.
Must be the domain attached to the ad account. The client's legal entity must be in its footer, Privacy and Terms.
Take the tag from the account name: [IT] / [OWN] / [LQ] — the tag is authoritative. LQ → no declaration, you get the provider site checklist instead.
10-second check: Admin → Policy → Account → “About this advertiser” card. If it says Point2Web while the site / licences are the client's — reset first, then BOV.
Registration doc + agreement (Annex / IO) as separate files, EIN if available. Never the same file for two requirements. The owner named in the EIN letter (“… SOLE MBR”) is whose ID goes into identity verification.
Landing Page Library
Reference page structures for the difficult verticals. Each guide is built from two sources: the platform's written rules and our own approval / rejection history. Use them at two moments — before a submission, to shape the page; and after a rejection, to walk the list and spot what most likely went wrong and what to improve. They are field-tested patterns, not a guarantee: platforms review case by case.
PointBoard Compliance Toolkit · hard rules live in the policy files, precedents in the case history — this page only collects the inputs.