The policy pages a faucet actually needs
Terms, privacy and a plain statement of the earning rules — as editable database rows, not hardcoded markup, so they can be kept honest.
Policy scaffolds, cookie consent, data export and country blocking.
4 entries
Terms, privacy and a plain statement of the earning rules — as editable database rows, not hardcoded markup, so they can be kept honest.
No third-party consent script. A dismissible banner, a stored choice, and ad code that only loads once consent exists.
Export as JSON, delete as anonymise-and-keep-the-ledger — because financial records have to survive a deletion request.
GeoIP at the edge or in PHP, applied to earning and signup rather than to content, with a message that says what happened.