PADI Axelerant
padi.com Enterprise Architecture
v1.1 · 6 November 2026
Work in progress · Version 1.1, last updated 6 November 2026
Architecture

Data architecture

What data the estate holds, where it lives, how long it is kept and how it moves between systems.

Data flows

Figure 6. Data flows. Personal member data stays on the server and in the browser session; it is never cached at the edge.
Figure 6. Data flows. Personal member data stays on the server and in the browser session; it is never cached at the edge.

Data inventory and classification

Dataset Classification System of record Copies Region Retention
Published content and translations Public Drupal (Acquia) Varnish, Cloudflare, OpenSearch, Next.js caches Acquia, AWS us-west-2 (Oregon); Cloudflare global Life of content; Cloudflare up to 24 h
Draft content, revisions Internal Drupal Crowdin files during translation As above Drupal revision history
Media assets Public Acquia DAM Renditions at Cloudflare (7 days) and in the Next.js image cache DAM region (to confirm) DAM policy
Shops, courses, prices, places Public PADI Travel FinderDB, OpenSearch AWS us-west-2 FinderDB point-in-time recovery 14 days, two index generations
Shop booking, banking and legal fields Restricted PADI Travel None: 58 columns are excluded from the copy n/a n/a
Member file (shop membership) Internal PADI core FinderDB (store numbers only) AWS us-west-2 Replaced on each file
Finder translations Public FinderDB Crowdin AWS us-west-2, Crowdin Not rebuildable from PADI Travel, protected by point-in-time recovery
Member identity and tokens Personal, Restricted PADI Cognito httpOnly session cookies on .padi.com (8 h) Cognito us-west-2 Refresh token 30 days
Member records (certifications, eCards, courses, club, logbook) Personal PADI platform Next.js server memory, 5 min to 6 h, per server Acquia region In-memory only
Device fingerprint Personal PADI collector None PADI PADI policy
Telemetry (traces, metrics, finder logs) Internal, may contain Personal Datadog Finder logs archived to S3 Datadog US1 (United States), AWS us-west-2 Finder log index 30 days, full archive 1 year, Lambda logs 30 days
Translation memory Internal Crowdin n/a Crowdin (to confirm) Crowdin policy

Controls on personal data

  • Personal pages (account, MyPADI, sign-in) are sent private, no-store, so neither Cloudflare nor Varnish keeps them. A privacy test checks that no cached response carries a cookie.
  • Member data is fetched server-side. The browser receives rendered pages and an httpOnly session.
  • Traces are redacted of emails and member ids before export. Some PADI API paths carry an email or member id in the URL, which is why redaction is needed.
  • The finder copy of PADI Travel excludes personal, banking and legal columns at the source.