Pay My Billy and bill privacy: how to share less sensitive information

People asking for help may feel pressure to prove a bill is real. But an unredacted statement can expose a service address, customer number, account reference, due date, barcode or QR code. Those details can be copied and misused, even if a post is later deleted.

Redact before sharing

• Cover names, street addresses, customer/account numbers, meter identifiers and payment references.
• Remove barcodes and QR codes; these can contain data or open payment workflows.
• Never share bank logins, passwords, OTPs, full card details, security codes or identity documents in a post or direct message.
• Use a flattened image with opaque blocks, reopen it and ensure hidden text is not selectable or visible through transparency.
• Do not send bills to this microsite; it cannot receive or verify them.

Verify the channel and payment path

Reach the project through a first-party URL or social profile that you independently verify. A copied logo or account name is not sufficient. Check whether the product is a demo or live service, who operates it, how data can be deleted, and whether payments go directly to a bill issuer or through an intermediary. Do not assume a demo has secure production controls.

Be suspicious of advance fees, requests to return an overpayment, gift cards, crypto, remote access, secrecy or login codes. Confirm proposed payments directly with the provider using a known number or its verified website. Never let a stranger sign into your account to “help.”

If information has already been exposed

Contact the provider through a verified route and ask whether account security can be strengthened. Change compromised passwords, enable multifactor authentication, review recent sign-ins and contact your bank if financial credentials were shared. Save the URL and sender details for a platform report without reposting exposed documents.

Read our privacy checklist, project source notes, and the overview of Pay My Billy’s demo status.