Security & Data Handling

Last updated 2026-05-11. This page describes how JobMaster handles your data today. It will be expanded as the Service grows and as we publish formal certifications.

Where your data lives

JobMaster is hosted entirely in Google Cloud Platform's Sydney region (australia-southeast1). Compute runs on Cloud Run, data sits in Firestore (native mode), files in Cloud Storage. None of these is replicated outside Australia for normal operation. Backups live in the same region.

Per-user data isolation

Every user account has a dedicated namespace in Firestore and a dedicated bucket prefix in Cloud Storage. Firestore security rules and bucket-level IAM constrain reads and writes to the namespace owner. There is no shared write path, no global "admin" view that aggregates user content, and no analytics layer that pools profile data across accounts.

Encryption

• In transit: TLS 1.2 or higher between you and the Service, between the Service and Google Cloud, and between the Service and every third-party processor.
• At rest: All Firestore documents and Cloud Storage objects are encrypted by Google Cloud KMS. Database backups inherit the same encryption.
• Secrets: API keys for AI providers, Stripe webhook secrets, and email-sender keys are stored in Google Secret Manager, accessed only at runtime, never logged.

AI provider data handling

JobMaster calls leading AI models (from Anthropic, OpenAI, and Google) when you generate a tailored document, score a job, or extract insights. We pass only the inputs needed for the task and discard the response after delivering it to you. We use each provider's API tier under default API terms, which (at the time of writing) do not authorise model training on inputs. We do not opt into training-eligible programs, and if any provider changes their default we will publish a notice and seek your continued consent.

Authentication

The SaaS tier uses Firebase Authentication: email-and-password with bcrypt-equivalent hashing, plus Sign in with Google as an optional path. Multi-factor authentication is on the roadmap. Passwords are never stored in plaintext, never logged, and never sent to any third party.

Logs and observability

Standard request logs are retained for 90 days for security and abuse detection. Logs include IP, user agent, timestamp, and the URL requested; they do not include resume content, cover-letter content, or pipeline data. Application errors are recorded with redacted stack traces only.

Data deletion

Account deletion is final. When you cancel and request deletion, your namespace and all associated objects are removed from Firestore and Cloud Storage within 30 days. Backup snapshots roll over within 90 days; after that no copy remains. Billing records are retained for 7 years as required by Australian tax law (and contain only billing metadata, not profile content).

Reporting a vulnerability

If you believe you have found a security issue, please email contact@jobmaster.com.au with the subject "Security report". We take every report seriously and aim to respond within two business days.

Third-party processors

• Google Cloud (Sydney) - hosting, storage, secrets.
• Stripe - card payments. Card details never reach JobMaster servers.
• Resend - transactional email (welcome, billing receipts, password resets, support replies).
• Anthropic / OpenAI / Google AI - leading AI models called only when you trigger an AI action.