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.
Cryptographic Controls & Certificate Protection
Passinstance enforces strict cryptographic standards for data in transit, data at rest, and wallet signing material:
| Security Layer | Control Standard | Implementation Details |
|---|---|---|
| Encryption in Transit | TLS 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 Rest | AES-256-GCM | encrypted database volumes, automated database backups, in-memory cache persistence, and S3 buckets are encrypted at rest via AWS KMS. |
Apple .p12 Signing Keys | Envelope Encryption | Uploaded 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 Credentials | Encrypted encrypted storage Storage | Google 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 Integrity | HMAC-SHA256 | Outbound 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:
{
"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 (
.p12certificates 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.
