MMyPay QR
Privacy

PRIVACY NOTICE · DRAFT FOR REVIEW

How MyPay QR handles personal information.

This draft explains the information used to provide and protect MyPay QR. It must be reviewed before a live customer pilot.

Information we handle

  • Member name, email, private MPQ identity and sign-in records.
  • QR details, recipient status and connected payout-account status.
  • Payer MPQ identity, payer email, amount, payment status, date and Stripe reference.
  • Support messages and technical, fraud-prevention and security records.

Stripe collects payment-method and connected-account payout information on its hosted services. MyPay QR and its service providers retain information needed to authenticate, process, support and reconcile payments, but the payer and payee see each other's MPQ identity rather than each other's email, phone number, PayID, bank details or card details.

Why we use it

  • Provide account access, QR payment pages and payment records.
  • Process, confirm and reconcile payments.
  • Answer support requests, resolve complaints and prevent misuse.
  • Meet applicable legal, security and record-keeping obligations.

Service providers and location

MyPay QR uses Stripe for payments and connected accounts, Supabase for authentication and data services, Resend for authentication email, and OpenAI Sites infrastructure for the web service. These providers may process information outside Australia under their own service terms and privacy arrangements.

Security, access and retention

We use access controls, encryption and audit records designed to protect information. We retain information only while it is reasonably needed for service, security, dispute and legal purposes. Final retention periods must be approved before live use.

You may ask to access or correct personal information by contacting us. We may need to verify your identity first.

Draft updated 13 September 2026.

Return to MyPay QR