Skip to content
Help Center Guide · Security & Compliance
3 min readVerified 2026-11-16

Security & Compliance Policies

Review EU AWS Frankfurt (eu-central-1) hosting architecture, TLS/encryption controls, signing certificate storage, and subprocessors.

In This Guide

EU Data Residency & Cloud Infrastructure (eu-central-1)

Passinstance is engineered with an EU-first security and data residency architecture hosted inside Amazon Web Services Europe (Frankfurt, eu-central-1), with workspace legal, privacy, and security controls surfaced under /settings/workspace/security, /settings/workspace/privacy, and /settings/workspace/legal. All primary compute clusters, transactional databases, cache layers, and encrypted object storage operate within private VPC subnets in Frankfurt.

SYSTEM ARCHITECTURE FLOW
INTERACTIVE ARCHITECTURE
FRANKFURT (eu-central-1) SECURITY BOUNDARY
STAGE 01 EDGE & INGRESS LAYER (TLS 1.3 / HSTS / WAF)
CSRF Verification, 1-Second Burst Rate Limiter & Strict DTO Validation
STAGE 02 AWS FRANKFURT (eu-central-1) PRIVATE VPC
Compute: NestJS API & background job queue Workers (Isolated Container Subnets)
Persistence: Encrypted Cloud Database (AES-256 at Rest) & Cache Layer
Key encrypted storage: KMS Envelope Encryption for Apple .p12 & Google Credentials
Media Store: S3 (passinstance-uploads-euc1) with Private OAC Policies
STAGE 03 Outbound Guard (Webhook URL Validator / SSRF Block)
WALLET CLOUD SUBPROCESSORS
Apple APNs (api.push.apple.com)
Google Wallet REST API
TENANT WEBHOOK ENDPOINTS
Public HTTPS Targets Only
Blocks RFC 1918 / Loopback / Metadata

Cryptographic Controls & Certificate Protection

Passinstance enforces strict cryptographic standards for data in transit, data at rest, and wallet signing material:

Security LayerControl StandardImplementation Details
Encryption in TransitTLS 1.3 / TLS 1.2+Enforced across all HTTPS API endpoints (/api/v1/), smart download links (/d/:slug), and APNs HTTP/2 connections.
Database & Storage at RestAES-256-GCMencrypted database volumes, automated database backups, in-memory cache persistence, and S3 buckets are encrypted at rest via AWS KMS.
Apple .p12 Signing KeysEnvelope EncryptionUploaded Apple Pass Type ID .p12 certificates and private keys (CertificatePkey) are encrypted prior to persistence and decrypted only in memory during PKCS#7 .pkpass signing.
Google Wallet CredentialsEncrypted encrypted storage StorageGoogle Cloud Service Account private keys used to sign Save-to-Wallet JWTs and REST PATCH requests are encrypted at rest and never exposed in API responses or logs.
Webhook IntegrityHMAC-SHA256Outbound webhook payloads are signed using tenant-specific secrets (X-Webhook-Signature: sha256=<hex_digest>).

Application Security & Network Boundary Guards

1. SSRF Protection (OutboundUrlUtil & Webhook URL Validator)

Whenever Passinstance initiates outbound HTTP requests — such as delivering push webhooks or fetching remote pass assets — Webhook URL Validator and OutboundUrlUtil resolve target DNS records and block connections to private IPv4/IPv6 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopback addresses (127.0.0.1, ::1), link-local subnets (169.254.169.254 cloud metadata endpoints), and non-HTTPS schemes in production.

2. CSRF & Input Validation Guards

All state-changing dashboard requests enforce Cross-Site Request Forgery (CSRF) token validation and strict Origin checking. Every API DTO is validated at the controller boundary via class-validator with whitelist: true and forbidNonWhitelisted: true to reject unexpected payload properties.

3. Strict Multi-Tenant Isolation

Every database query, background background job queue job, cache key, and S3 asset path is strictly scoped by customerId (or organizationId). Cross-tenant access attempts fail closed with 403 Forbidden or 404 Not Found before any domain logic executes.

Subprocessors & Ecosystem Dependencies

While Passinstance stores all core tenant data in AWS Frankfurt (eu-central-1), delivering native mobile wallet passes inherently interacts with device operating system providers:

JSON
{
  "primaryHostingRegion": "eu-central-1 (AWS Europe Frankfurt)",
  "coreSubprocessors": [
    {
      "provider": "Amazon Web Services EMEA SARL",
      "purpose": "Compute, database, in-memory cache, KMS, S3, SES",
      "location": "Frankfurt, Germany (eu-central-1)"
    },
    {
      "provider": "Apple Inc.",
      "purpose": "Apple Push Notification service (APNs) for iOS/watchOS pass refreshes",
      "location": "Global APNs Edge Network"
    },
    {
      "provider": "Google LLC",
      "purpose": "Google Wallet REST API (`walletobjects`) for Android pass persistence",
      "location": "Global Google Cloud Infrastructure"
    },
    {
      "provider": "Stripe Payments Europe, Ltd.",
      "purpose": "PCI-DSS Level 1 payment processing and subscription invoicing",
      "location": "EU / Global"
    }
  ]
}

Important: Private signing keys (.p12 certificates and Google Service Account JSON keys) are write-only secrets. Neither Passinstance support staff nor workspace administrators can download a raw private key once uploaded; compromised keys must be revoked in the Apple Developer Portal or Google Cloud Console and replaced via /api/v1/certificates.

Review our live compliance posture and legal agreements at /security, /privacy, and /terms.

Related Product & Developer Documentation

Ready to launch your first pass program?

Create your workspace, configure your pass template, and test a real pass in Apple Wallet and Google Wallet before you scale.