Privacy policy
This policy explains what BuyerProtection collects, how it is held and used, who can receive it, where processing can occur and how to ask for access, correction or deletion.
Who operates BuyerProtection
BuyerProtection is a product operated by GOV ASSIST PTY LTD trading as TRUSTEDSITE, ABN 97 697 294 410. This policy covers buyerprotection.com.au, public store checks, merchant accounts, controlled commerce connections, Order Passports, support and privacy requests. Counterparty-specific data terms remain separate.
What is public
A public result is limited to the merchant or business name, official domain, current proof state, source and validity window. Buyer receipts, email, delivery evidence, support conversations, claim files and private order records stay private. Unknown simply means no public BuyerProtection proof record is available yet.
What we collect
Merchant records can include name, work contact, company, domain, optional ABN, authentication, consent and verification evidence. Authorised order records can include an order reference, amount, currency, fulfilment and refund state, integrity metadata, evidence and issue history. Support and privacy requests include submitted details and authority evidence. BuyerProtection also uses a first-party pseudonymous session identifier that can last up to one year; product events can record an IP-derived hash, user agent, page, action and time, while hosting and security systems can create operational logs.
How we collect, hold and use it
Information can come from a buyer or merchant, a merchant-authorised platform such as Shopify, the bundled TrustedSite proof engine, a signed link or technical activity while the service is used. Records are held in the application hosting environment and configured providers. We use them to secure accounts, verify merchant and domain authority, publish the correct proof state, maintain Order Passports, reconcile limited commerce events, handle incidents and appeals, investigate misuse, answer requests, measure controlled pilots and retain an auditable decision history.
Who can receive it and overseas processing
BuyerProtection uses configured hosting, commerce, email and support connections described in the public provider register. A merchant-authorised platform supplies only approved integration fields; TrustedSite provides the bundled merchant and domain proof record; disclosure can also occur where required or authorised by law. Overseas processing can apply. Observed Railway runtime region: us-east4-eqdc4a Contract status, Australian cross-border review and provider roles are recorded separately for each counterparty.
Partner introductions
When a merchant accepts a signed partner invitation and separately consents, the partner can receive agreed aggregate milestones such as account created, public proof live or commerce connected. Customer, order and payment records, account access and decision rights stay with their authorised owners.
Retention, deletion and security
The public lifecycle register separates account, security, order, support, provider and backup records. Transient records use guarded expiry; final schedules remain human-approved. Deletion records valid authority, provider follow-through and backup follow-through as separate events. Signed links, origin checks, rate limits, encryption controls and audit records protect each path.
Privacy complaints, access, correction and deletion
You can request access, correction or deletion without special legal words. Name the record without pasting the sensitive data. We verify identity or authority before disclosing or changing it, then keep intake, scope, human decision, execution evidence, response and closure separate. To make a privacy complaint, use the privacy route or email support@buyerprotection.com.au and explain what happened and the outcome you seek. We use a 30-calendar-day operational target where reasonable; applicable law and facts control each case.
Human decisions, appeals and corrections
Automated controls validate signatures, authority, expiry, integrity and required fields. The applicable human authority owns merchant verification, incident classification, adverse action, correction, revocation, appeal and every guarantee decision.
Changes, contact and alternate formats
Material changes are dated on this page. Bank and platform pilots use counterparty-specific data terms alongside this policy. For a privacy request, complaint or accessible copy, use the published contact route. Security vulnerabilities use the separate security channel.
Privacy question
Tell us whether you are the buyer, merchant or authorised representative and which store, order or account the request concerns. Use the secure follow-up path for any identity evidence.