Skip to content
Home / Security

Security

Last updated: 1 May 2026

Security is a core part of how we build every TemTed Group product. This page describes our security practices and how to report a vulnerability.

Our approach

We apply a defence-in-depth approach across our infrastructure, application, and operational layers. Security is considered at every stage — from architecture reviews and code review to deployment pipelines and incident response.

Infrastructure

  • All services hosted on major cloud providers (AWS, Google Cloud) with SOC 2 Type II certification
  • Network segmentation and least-privilege IAM policies throughout
  • Automated vulnerability scanning on all cloud resources
  • DDoS protection and web application firewall (WAF) at the edge

Data protection

  • All data encrypted in transit using TLS 1.2 or higher
  • Data at rest encrypted using AES-256
  • Passwords hashed using bcrypt with per-user salts — we never store plain text passwords
  • Payment card data handled exclusively by PCI-DSS certified processors (Stripe)
  • Database backups encrypted and tested regularly

Application security

  • Security code reviews as part of every pull request workflow
  • Dependency scanning and automated alerts for known CVEs
  • OWASP Top 10 addressed in our secure development lifecycle
  • Content Security Policy (CSP), HSTS, and secure cookie attributes enforced
  • Rate limiting and abuse detection on all public endpoints

Access controls

  • Multi-factor authentication (MFA) required for all team member access to production systems
  • Role-based access control (RBAC) with principle of least privilege
  • Access logs retained and reviewed for anomalies
  • Offboarding procedures that revoke access within one hour of departure

Compliance

  • GDPR and Australian Privacy Act 1988 alignment
  • COPPA and GDPR-K compliance for ChoreBuddies child-facing features
  • Annual third-party penetration tests
  • Regular internal security audits and risk assessments

Incident response

  • 24/7 monitoring and alerting for security events
  • Documented incident response runbooks
  • Affected users notified within 72 hours of a confirmed breach where required by law
  • Post-incident reviews published internally; material incidents summarised publicly

Responsible disclosure

We welcome security researchers who discover potential vulnerabilities in our products and services. We ask that you follow responsible disclosure principles:

  • Do not access, modify, or delete data that is not yours.
  • Do not perform denial-of-service attacks or disrupt production services.
  • Do not publicly disclose the issue before we have had a reasonable opportunity to investigate and remediate it (we aim to acknowledge within 3 business days and resolve critical issues within 14 days).
  • Do provide clear, reproducible steps so we can confirm the vulnerability.

We commit to working with you in good faith, keeping you informed of our progress, and — where the report leads to a confirmed fix — crediting you (if you wish) in our acknowledgements.

How to report a vulnerability

Send vulnerability reports by email to:

security@temtedgroup.com

Please include:

  • A description of the vulnerability and its potential impact;
  • The affected product, URL, or endpoint;
  • Step-by-step reproduction instructions;
  • Any proof-of-concept code or screenshots (do not include real user data).

Please do not report security vulnerabilities through public GitHub issues, social media, or general support channels.

Bug bounty

We do not currently operate a formal bug bounty programme with financial rewards, but we do recognise researchers in our public acknowledgements list for responsibly disclosed, confirmed vulnerabilities.

Contact

Security team: security@temtedgroup.com
General enquiries: hello@temtedgroup.com