Use what the job needs. Keep the boundary visible.

1. What we collect

Depending on how you deal with us, we may collect your name, business contact details, role, organisation, enquiry content, correspondence, purchase and billing records, service requests, approvals, account/workspace information and information needed to configure or support an agreed service. Website and service providers may also create technical and security logs such as IP address, browser, requested page and timestamp.

2. Public enquiries

Website enquiries are submitted through a controlled MySidekick gateway and may be recorded in MySidekick's CRM and operating evidence so the enquiry can be handled, reconciled and followed through without losing context. Submitting an enquiry does not authorise access to your systems or start material Sidekick work.

3. Online payments

Online payments are processed by the selected payment provider. MySidekick receives transaction, customer, subscription and billing-status identifiers needed to reconcile the purchase and operate the service, but does not receive or store your full card number. Payment-card details remain with the payment provider.

4. Customer workspace

For customers we may process organisation membership, authorised-user roles, plan and service state, Sidekick configuration, approvals, activity/evidence, connected-system status, onboarding progress, support requests and billing state. Access is scoped to the relevant organisation, membership and entitlement.

5. Why we use information

We use personal information to respond to enquiries, assess fit, process purchases, administer subscriptions, onboard customers, configure and operate agreed services, maintain security and evidence, provide support, manage billing and meet legal obligations. An enquiry is not automatically a marketing subscription.

6. What not to send

Do not submit passwords, API keys, access tokens, confidential documents, health information or other sensitive personal information through public forms or general email. Where an agreed service needs protected information, an approved access method is established first.

7. Service providers

We use providers where reasonably required for hosting, email, documents, automation, CRM, payment processing, customer access and other approved service functions. Providers may operate global infrastructure. Customer-specific systems are selected and authorised separately.

8. Security and access boundaries

We use role-based access, approved credential stores, bounded workflow authority, provider security features, evidence and change controls appropriate to the service. No online system can be guaranteed completely secure.

9. Retention

We keep personal information only as long as reasonably needed for its purpose, to operate the service, meet financial/legal obligations, resolve disputes and retain necessary evidence. Records are deleted, de-identified or securely disposed of when no longer required, subject to law and legitimate operational needs.

10. Access, correction and complaints

You may request access or correction, or raise a privacy complaint, by emailing privacy@mysidekicks.au. We may need to verify identity and authority first. If a complaint remains unresolved, you may contact the Office of the Australian Information Commissioner.

11. Automated activity

MySidekick may use automation to route, prepare and perform agreed work. Material customer actions remain subject to the applicable purpose, system access, testing, service state and human-authority boundaries. We do not treat payment or a public enquiry as blanket authority over customer systems.

12. Cookies and analytics

WordPress, the hosting provider and payment/customer-access services may use essential technical mechanisms and maintain access, security and performance logs. Any optional analytics or marketing technologies will be reflected in this policy and the required notice or choice before use.

13. Changes

We may update this policy when our services, providers or legal obligations change. The current version and effective date will be published here.