Privacy-by-Design Governance & GDPR Compliance
Passinstance enables European and global organizations to operate digital wallet loyalty, ticketing, and membership programs in strict compliance with the EU General Data Protection Regulation (GDPR) and CCPA. Through Privacy Compliance API (/api/v1/customer/:customerId/privacy-settings/*) and Dashboard Workspace Settings -> Privacy (/settings/workspace/privacy), workspaces can enforce data minimization, automate retention purging (RETENTION_POLICY_KEYS), and execute verifiable Data Subject Rights (DSR) workflows.
Privacy & Data Retention API Reference (Privacy Compliance API)
All privacy, retention, and GDPR Data Subject Rights endpoints are tenant-scoped under /api/v1/customer/:customerId/privacy-settings:
| Endpoint Path | Method | Auth | Functionality | |||||
|---|---|---|---|---|---|---|---|---|
/api/v1/customer/:customerId/privacy-settings | GET | Bearer | Retrieves workspace tracking, legal, and privacy overview settings. | |||||
/api/v1/customer/:customerId/privacy-settings/retention | GET / PATCH | Bearer | Lists or updates (request payload) retention policies keyed by RETENTION_POLICY_KEYS. | |||||
/api/v1/customer/:customerId/privacy-settings/retention/activity | GET | Bearer | Lists recent scheduled and manual retention execution runs (RetentionRunStatus: `SCHEDULED | RUNNING | COMPLETED | COMPLETED_WITH_WARNINGS | FAILED | CANCELLED`). |
/api/v1/customer/:customerId/privacy-settings/retention/:policyKey/preview | POST | Bearer | Runs a non-destructive dry run returning the exact count of eligible records for :policyKey. | |||||
/api/v1/customer/:customerId/privacy-settings/retention/:policyKey/run | POST | Bearer | Executes the policy immediately (supports ?dryRun=true). | |||||
/api/v1/customer/:customerId/privacy-settings/data-subject-search | POST | Bearer | Searches passes, delivery records, and scans via { query } (3–256 chars, matching email, phone, serial, or externalId). | |||||
/api/v1/customer/:customerId/privacy-settings/data-subject-export | POST | Bearer | Generates a GDPR Article 15/20 IDataSubjectExportPayload JSON archive for { query }. | |||||
/api/v1/customer/:customerId/privacy-settings/data-subject-delete | POST | Bearer | Executes GDPR Article 17 anonymization/deletion (request payload). |
Automated Data Retention Policies (RETENTION_POLICY_KEYS & RetentionAction)
To enforce storage limitation (GDPR Article 5(1)(e)), Privacy Compliance API defines 7 canonical policy keys (RETENTION_POLICY_KEYS):
-
Pass Lifecycle Keys:
neverWalletAddedPasses,passesWithoutActiveWalletRegistrations,passesByCreationAge,expiredPasses,passesNotModifiedSince. -
Delivery Log Keys:
emailDeliveryRecords,smsDeliveryRecords.
Each policy configures enabled (boolean), retentionDays (RETENTION_MIN_DAYS to RETENTION_MAX_DAYS, aligning with presets like DataRetentionPolicy: KEEP_FOREVER | DELETE_AFTER_30_DAYS | DELETE_AFTER_90_DAYS | DELETE_AFTER_1_YEAR | DELETE_AFTER_7_YEARS | CUSTOM), and action (RetentionAction: 'delete' | 'anonymize'):
{
"policies": {
"neverWalletAddedPasses": {
"enabled": true,
"retentionDays": 30,
"action": "delete"
},
"expiredPasses": {
"enabled": true,
"retentionDays": 90,
"action": "anonymize"
},
"emailDeliveryRecords": {
"enabled": true,
"retentionDays": 365,
"action": "delete"
}
}
}
Before executing a purge, call POST /api/v1/customer/:customerId/privacy-settings/retention/neverWalletAddedPasses/preview to inspect affected record counts without mutating data.
Executing GDPR Data Subject Rights (request payload / request payload / request payload)
When a passholder submits a subject access request (SAR) or right-to-erasure request:
-
1
Locate Records (
POST .../data-subject-search): Submit{ "query": "customer@example.com" }(also matchesexternalId, phone, orserialNumber) to return groupedIDataSubjectSearchResultGroupmatches across passes and logs. -
2
Export Portable Archive (
POST .../data-subject-export): Submit{ "query": "customer@example.com" }to receiveIDataSubjectExportPayload({ exportedAt, workspaceId, queryLength, groups, totalCount }). -
3
Verified Erasure (
POST .../data-subject-delete): Requires{ query, confirmationPhrase: "DELETE PERSONAL DATA", reason, requestVerified: true, resourceIds? }:
{
"query": "customer@example.com",
"confirmationPhrase": "DELETE PERSONAL DATA",
"reason": "Verified GDPR Article 17 erasure request #DSR-4410",
"requestVerified": true
}
Response (200 OK — IDataSubjectDeletionSummary):
{
"passesAnonymized": 2,
"deliveryRecordsDeleted": 6,
"skippedProtected": 0
}
Important: Executing server-side erasure (
POST .../data-subject-delete) anonymizes/purges personal data in Passinstance databases and respects active retention holds (retentionHoldUntil). However, because Apple Wallet stores signed.pkpassfiles locally on the user's iPhone, the passholder must still tap Remove Pass inside Apple Wallet to delete the cached card from their physical device.
Review our complete legal commitments in the Privacy Policy and Security & Trust Center.
