PRIVACY NOTICE
How website and connected checkout data can be used.
Last updated 10 August 2026. Contractual roles and merchant-specific instructions remain defined by the applicable agreements.
Roles and scope
The merchant determines products, customer relationship and configured providers. HustlePay provides checkout-orchestration software and can process session/order context to provide that service. PSPs process payment-method information under their own terms and notices.
The website can also process contact requests, technical logs and consent/preferences needed to operate and protect the service.
Data categories and purposes
- Order ID, amount, currency, description, line items, fees, shipping, tax and return/callback URLs.
- Name, billing email, phone, company and billing address when supplied by the connected store.
- Session IDs, timestamps, status/callback and technical security data.
- Information entered in sales, demo, support, investor or privacy forms.
Data is used to create and reconcile sessions, return status, provide onboarding/support/security response, answer enquiries and meet applicable obligations. The public WordPress connector does not store full card numbers or CVVs.
Sharing, retention, transfers and rights
Data can be shared with the merchant, its configured PSPs and service providers needed to host, secure, communicate and support the service. Retention depends on data type, purpose, security, contractual and legal needs. Where required, transfer safeguards should be used.
Depending on applicable law, individuals may request access, correction, deletion, restriction, portability or objection and may complain to their data-protection authority. Use the privacy route with safe order/merchant context and never send payment credentials.
Cookies and third-party content
Essential storage can support security, language, session and preference functions. Analytics or marketing technologies should run only where configured and permitted by the consent choice. Embedded third-party content can receive technical information under its own notice.
Privacy questions
Does HustlePay store full card numbers or CVVs?
The public WooCommerce connector says it does not store full card numbers or CVVs. Payment-method collection remains in the connected checkout and PSP flow. Merchant-specific roles, retention, transfer safeguards and request handling remain subject to the applicable agreements, configured services and governing law.
What order data can HustlePay process?
The connected flow can use order ID, amount, currency, items, fees, shipping, tax, callback details and customer billing/contact context needed for the service. Merchant-specific roles, retention, transfer safeguards and request handling remain subject to the applicable agreements, configured services and governing law.
Who decides why checkout data is processed?
The merchant determines the customer relationship and store purpose; HustlePay provides the connected orchestration service and PSPs process payment-method information under their own notices. Merchant-specific roles, retention, transfer safeguards and request handling remain subject to the applicable agreements, configured services and governing law.
How long is data retained?
It depends on the data type, service purpose, security need and contractual or legal requirement. Merchant-specific terms can define additional details. Merchant-specific roles, retention, transfer safeguards and request handling remain subject to the applicable agreements, configured services and governing law.
How can I make a privacy request?
Use the privacy contact route with safe merchant or order context. Never include passwords, API secrets, full card details or CVVs. Merchant-specific roles, retention, transfer safeguards and request handling remain subject to the applicable agreements, configured services and governing law.
Does the website use cookies?
Yes, essential storage can support security, sessions and preferences. Analytics or marketing technologies should run only where configured and permitted by the consent choice. Merchant-specific roles, retention, transfer safeguards and request handling remain subject to the applicable agreements, configured services and governing law.
Ask a privacy question
Identify the merchant or order context without including payment credentials.