Skip to content
HighAdsROI
法律

Security

How we protect data in transit, at rest, and in process — across thirteen lines of defence.

Last updated: · Version 1.0

1. Overview

HighAdsROI is a data-sovereignty-first platform. The entire architecture is designed so that customer data never leaves the customer's perimeter. This page describes how we secure both this website and the platform we deliver to customers.

2. Cryptography

  • In transit: TLS 1.3 minimum. HSTS preloaded. Certificate Transparency monitored.
  • At rest: AES-256 (GCP-managed keys; CMEK available on Enterprise plans).
  • PII hashing: SHA-256 with platform-level salt. Plaintext email and phone never persist in BigQuery or Firestore.
  • Secret storage: Cloud KMS / Cloudflare Secrets. No secrets in source.

3. Access control

  • Single sign-on (SSO) via your IdP (OIDC / SAML).
  • Short-lived tokens for all internal services. No long-lived static credentials.
  • Cloud Scheduler routes verified by OIDC + audience match on every invocation.
  • Just-in-time access for engineering. Production access requires reason-of-access + approver.

4. Infrastructure

  • Customer data: Firestore + BigQuery in your GCP project, your region (Sydney australia-southeast1, Tokyo asia-northeast1, or Singapore asia-southeast1).
  • Edge: Cloudflare Workers / Pages — DDoS, WAF, bot management included.
  • Network: Private Service Connect for inter-service traffic. No public ingress to data planes.
  • Backup: Point-in-time recovery 35 days; cross-region replication available.

5. Monitoring

  • Per-event success / permanent-failure metrics.
  • Structured error_kind taxonomy for ad-platform failures.
  • Worker-bypass mode lets ops manually replay events from the data store.
  • SLO-driven alerting; runbooks for each alert.
  • Audit logs retained 365 days; immutable / WORM available on Enterprise.

6. Incident response

Severity-tiered runbooks. Notification SLAs:

  • P0 (data loss / breach): customer notified within 24 hours; regulator within statutory window (72 hours under GDPR; equivalent in AU NDB, NZ Privacy Act, others).
  • P1 (degraded service): customer notified within 4 hours.
  • P2+: weekly status report.

Public status page: status.highadsroi.com (post-launch).

7. Audits and certifications

  • SOC 2 Type II: in progress. Report available under NDA.
  • ISO 27001: planned 2026 H2.
  • Penetration testing: annual third-party. Last test: TBD (post-launch).
  • Internal audits: quarterly. Findings tracked in shared SLA.

8. Responsible disclosure

We welcome security research. Email security@highadsroi.com (PGP key on request). We commit to:

  • Acknowledge within 24 hours.
  • Triage within 5 business days.
  • Fix critical issues within 30 days.
  • Public credit (with your permission).

We do not pursue legal action against good-faith research. No bounty program at launch — we plan to stand one up post-SOC 2.