Verify the person and obligation privately, then publish only what a supporter needs to understand the bill.
The key point
A minimal public profile can use a first name, general location, category, appropriate provider, verified balance, due date, verification status, and reviewed summary.
What to do
- Use a first name or approved display name.
- Keep source evidence and account identifiers private.
- Preview the exact public profile and require publication consent.
What to avoid
What happens next
The privacy goal is not to hide whether a bill is real; it is to avoid publishing information that is unnecessary to understand it. A reviewer can work from the private statement while the public profile uses a smaller set of approved facts. That reduces exposure of addresses, account references, IDs, and sensitive context.
How funding can work
Funding does not change the privacy boundary. A sponsor can define program rules and receive aggregate or permitted reporting, but that does not give the sponsor access to private source documents or the ability to buy a verification label.
Before you submit or help
Verify the person and obligation privately, then publish only what a supporter needs to understand the bill. A minimal public profile can use a first name, general location, category, appropriate provider, verified balance, due date, verification status, and reviewed summary. The original bill should stay private; the public page, when approved, is built from a smaller reviewed set of facts. Posting or verification does not guarantee payment, and live payment availability depends on a supported biller or payment rail.
Related resources
Choose the right path
Post a bill privately, browse approved bills, or fund a rule-based program for a group of verified obligations.