This document defines the policies and procedures governing how DCKAP Integrator stores data — including inputs received from source systems, data items in processing, outputs awaiting delivery, configuration data, and operational logs — with controls ensuring accuracy, completeness, security, and timely disposal.
2. Data Storage Categories
Data Type
Storage System
Encryption
Retention
Source Payloads (transient)
Message queue (durable)
In-transit: TLS; at-rest: AES-256
24 hours max
Processing State / Checkpoints
Processing state store (Redis)
AES-256
Until job completes
Dead-Letter Queue
DLQ storage
AES-256
7 days (configurable 1-30)
Sync Execution Logs
Log aggregation service
AES-256
90 days
API Request/Response Logs
Log aggregation service (PII masked)
AES-256
30 days
Audit Trail
Immutable audit database
AES-256
1 year
Integration Configuration
Config database
AES-256 (credentials in vault)
Lifetime of customer account
API Credentials (secrets)
Dedicated secrets vault
AES-256, customer key
Until customer removes them
Security Events / SIEM
SIEM platform
AES-256
1 year
3. Storage Security Policies
3.1 Encryption at Rest
All persistent storage uses AES-256 encryption.
Encryption keys are managed by a dedicated key management service (KMS), not stored alongside data.
Customer API credentials are encrypted using a per-customer encryption key derived from the master KMS key.
3.2 Access Controls
No storage system is publicly accessible — all are within the private network perimeter.
Access to log storage requires a dedicated service account with read-only access.
Direct database access in production requires multi-party authorisation (break-glass procedure).
3.3 Data Minimisation
DCKAP Integrator does not permanently store source or destination business data. The platform is a conduit:
Source payloads are queued, processed, and discarded within 24 hours.
No customer transactional records (orders, inventory, etc.) are stored in DCKAP’s databases beyond the processing window.
Only metadata about the sync (timestamps, counts, status) is retained in logs.
