Readers come here looking at PayID-routed deposits — a push payment, not a card transaction — and the way data moves through the New Payments Platform is genuinely different from older banking rails. Worth being upfront about what flows through this website, and what doesn't.
About this site / Who we are
This is an independent editorial site run from Australia. There is no parent corporation, no investor block, no payment processor with a seat at the table. Two writers and an occasional contractor produce the testing notes and write-ups. We are not a bank, not a financial adviser, not an authorised representative of any operator. Nothing on the site is personal advice — it's published opinion based on our own testing of cashier flows, withdrawal behaviour, and operator terms.
Why we collect this information (purposes)
We collect the minimum data needed to do four things and nothing more:
- serve pages reliably (server logs, cache headers)
- know which guides get read so we can update the ones that matter (aggregate analytics)
- respond to an email you send us (your message, your reply address)
- account for affiliate clicks so the referring operator pays the agreed fee
We do not collect data to "build a profile" of you, to retarget you with ads off-site, or to sell anything to a data broker. If a future feature would require that, we would not ship it under the current site name without rewriting this notice first.
Information we collect when you visit
Standard HTTP request data lands in our server logs: IP address, user agent string, referrer, timestamp, the URL you asked for. These logs rotate on a short cycle and exist mainly to investigate errors and abuse. They do not contain any bank identifier, PayID handle, mobile number, ABN, or NPP routing detail — none of that ever touches this site. PayID transactions happen between your bank app, the addressing service, and the operator's acquirer; we sit nowhere on that path and have no way of intercepting it even in principle.
If you submit something to a contact form, we receive what you wrote and the address you wrote it from. If you subscribe to a list, we receive your email address and the timestamp at which you ticked the consent box. That is the complete list of personal data points this site receives by design.
Sharing information with others
We do not sell, lease, or barter visitor information. Limited operational sharing is unavoidable: our hosting provider necessarily sees server traffic, our CDN handles cached delivery, and our analytics vendor processes anonymised event counts on our behalf under a written data processing agreement. Affiliate networks see the outbound click and may set their own attribution cookie at the destination site — once you click out, you are on the operator's surface and their privacy policy governs from that point. If a regulator or court compels disclosure of records we hold, we comply with the narrowest reading of the order and notify the affected person where allowed by law.
Your rights under the Privacy Act 1988
Under the Australian Privacy Principles, you have the right to ask whether we hold personal information about you, to see it, to ask us to correct it, and to ask us to delete it where there is no lawful reason to retain it. For most readers the answer to "do you hold anything about me?" is genuinely no — only the people who have emailed us or subscribed to a list will have any record at all.
How to make a complaint or request
Send a written complaint to privacy@payid-casinos.com.au. Tell us what happened, what outcome you want, and any reference (email subject line, approximate date). We aim to acknowledge within five business days and resolve within thirty. If our response is unsatisfactory you can escalate to the Office of the Australian Information Commissioner (OAIC), the regulator responsible for the Privacy Act 1988.
How to contact us
General editorial and privacy contact is the same inbox: privacy@payid-casinos.com.au. We don't operate a phone line. Postal correspondence is not accepted because we do not maintain a public registered office address for editorial security reasons; the operators we review attract a certain volume of hostile mail and we'd rather not be that target.
