Security & data governance
How we protect client data and systems
We take the security of our clients' websites, systems and information seriously. Our approach focuses on sensible access controls, secure development practices, responsible data handling and the careful management of third-party services.
Our approach
Security built into delivery and support
Security is part of how we manage client projects and ongoing support – not a separate exercise bolted on at the end. Exact controls depend on the platform, the engagement and what access we are given.
Controlled access
Access to client systems is limited to team members who need it for the work.
Multi-factor authentication
MFA is used on supported platforms and services wherever it is available.
Least privilege
We aim to grant only the access required for the task, not broad admin rights by default.
Credential hygiene
Passwords, API keys and credentials are handled carefully and should not be shared through email or chat.
Maintained software
As part of ongoing technical management, we keep software, plugins and dependencies maintained where we are responsible for them.
Environment separation
Where the platform and project allow it, development or staging environments are kept separate from production.
Secure deployment
Production changes are intentional, tested where practical, and limited to authorised team members.
Third-party care
Specialist platforms are selected for suitability and reliability, with clear understanding of shared responsibilities.
Data handling
Client information is accessed for agreed services and removed or returned when it is no longer required.
Access & accounts
How access to client systems is managed
Practical controls for logins, credentials and production access – applied consistently across the tools we use to deliver work.
- Access is provided only to team members who need it for delivery or support.
- Multi-factor authentication is used on supported services.
- Credentials should be stored in appropriate password-management tools – not shared through email or chat.
- Access should be removed when it is no longer required.
- Production access is limited to authorised personnel.
- Client credentials and API keys should not be committed to source control.
Client data
Information we may encounter
Digital agency work can involve a range of client information. We only access what is required to perform the agreed services, and we do not intentionally collect or retain information that is not needed for the engagement.
What is stored, where, and for how long depends on the project and the platforms involved – including hosting, CMS, CRM and analytics tools chosen for that work.
- Website content and media
- Contact and enquiry information
- Analytics and tracking data
- CRM or marketing-platform information
- Website administration data
- Source code and project repositories
- API credentials and service tokens
- Client documents and project assets
Development & deployment
How we build and ship changes
Practices that fit a digital agency delivering websites, marketing systems and ongoing technical care – not enterprise software theatre.
Environments
Where appropriate for the platform, we use development or staging environments before changes reach production.
Testing before release
Changes are reviewed and tested to a practical level before production deployment.
Controlled repositories
Source code is stored in controlled repositories rather than ad-hoc file sharing.
Secrets outside code
Environment variables, API keys and other secrets are kept out of source code.
Authorised production changes
Production changes are restricted to authorised team members working on the engagement.
Ongoing maintenance
Software, plugins and dependencies are maintained as part of ongoing technical management where that is in scope.
Third-party platforms
Specialist infrastructure and SaaS
Modern digital projects rely on specialist providers for hosting, analytics, CRM, email and related services. We select platforms based on suitability, security features, reliability and project requirements.
Each provider has its own security and privacy responsibilities. Eightball Media does not control the internal security practices of those platforms.
- WP Engine and other hosting providers
- HubSpot
- Google Analytics, Google Tag Manager and Google Ads
- WordPress and related plugins where used
- Email delivery services such as Resend
- Other client-approved platforms required for the engagement
Privacy & data protection
Personal information handled with care
Personal information is handled in accordance with applicable privacy obligations and the requirements relevant to the particular project. For Australian clients, that includes obligations under the Privacy Act 1988 and the Australian Privacy Principles where they apply.
This page is an overview of our security posture – not legal advice and not a substitute for our Privacy Policy.
Security incidents
If something goes wrong
If a security incident affecting client systems or information is identified, we work through a practical response. Specific notification timing is set by the engagement agreement and any applicable legal obligations – not by a blanket public promise.
01
Identify and assess
Understand what has happened, what systems or information may be affected, and the likely impact.
02
Contain
Limit further exposure where possible – for example by restricting access or isolating affected systems.
03
Notify
Inform the appropriate internal and client contacts where notification is required.
04
Coordinate
Work with relevant technology providers when their platforms or expertise are needed.
05
Remediate
Fix the issue and restore normal operations as safely and promptly as circumstances allow.
06
Review
Review the cause and take reasonable steps to reduce the chance of recurrence.
Corporate & supplier governance
Need information for your supplier review?
We can provide relevant information about our security practices and technology stack as part of a client's supplier onboarding or governance process. Contact us and we'll provide what is relevant for your security or procurement review.
Requirements vary depending on:
- –The nature of the services being provided
- –The systems being accessed
- –The type of information involved
- –The client's internal security requirements
- –Applicable regulatory obligations
Documents & policies
Supporting material
Public documents are linked below. Additional policies and evidence can be shared on request as part of a supplier or security review.
- Privacy PolicyHow we handle personal information submitted through this website.View
- Security OverviewThis page – our public summary of security and data governance practices.View
- Terms of UseTerms for using the Eightball Media website.View
Available on request
The following may be provided for corporate supplier reviews where relevant. They are not published as standalone public documents.
- Information Security Policy
- Data Retention & Deletion Policy
- Incident Response Policy
- Business Continuity Policy
- Supplier / subprocessor information
- Cyber insurance certificate
- Completed security questionnaire
Talk to us about security or supplier onboarding
Share your questionnaire, security checklist or procurement requirements and we will provide the relevant information for your review.