Privacy & Data Handling Policy

1. Scope & Objective

This Data Handling and Privacy Policy defines the security controls, data classification, retention, and operational procedures implemented by Markus Lukas Macalla (Retail Operations & In-House Technologies) to safeguard Amazon Information and customer Personally Identifiable Information (PII) obtained via the Amazon Selling Partner API (SP-API). All systems and workflows are operated strictly for our own internal e-commerce retail accounts and comply fully with the Amazon Acceptable Use Policy (AUP) and Data Protection Policy (DPP).

2. Data Collection & Purpose Limitation

We collect Amazon Information solely through authorized, authenticated Amazon SP-API endpoints via Login with Amazon (LWA) OAuth 2.0 over TLS 1.3 encrypted channels. Customer PII (such as buyer names and shipping/billing addresses) is retrieved strictly and exclusively for fulfilling legal tax obligations under German and European VAT regulations (e.g., German Value Added Tax Act / § 14 UStG) to generate and upload commercial tax invoices to buyers via Amazon’s VAT Calculation Service (VCS Lite / Upload Your Own Invoices).

3. Data Retention & Automated Disposal

In accordance with Amazon DPP requirements:

• PII Retention Period: Personally Identifiable Information is retained only as long as strictly necessary for order fulfillment and invoice generation, and in no event longer than 30 days after order shipment.
• Automated Purging: Automated daily scheduled jobs securely wipe and overwrite customer PII records from all databases upon reaching the 30-day post-shipment threshold.
• Anonymized Records: Non-PII tax records and financial summaries are retained solely to fulfill statutory German tax audit obligations (GoBD) without storing customer PII.

4. Cryptography & Encryption Standards

• Encryption at Rest: All databases, storage volumes, and backups containing Amazon Information are encrypted using AES-256 (Advanced Encryption Standard with 256-bit keys). Encryption keys are managed via a dedicated Key Management Service (AWS KMS) with annual automated key rotation.
• Encryption in Transit: All communications, API interactions, and internal network traffic mandate TLS 1.3 (or minimum TLS 1.2) with strict forward secrecy.
• No Plaintext Credentials: API keys, LWA secrets, and database credentials are encrypted at rest, never stored in source control, and dynamically injected at runtime via secure secret managers.

5. Network Security, Logging & Endpoint Protection

• Network Isolation: Production databases and application containers operate inside private subnets without public internet exposure, protected by stateful firewalls and default-deny ingress rules.
• Strict PII Logging Exclusion: Personally Identifiable Information is strictly prohibited from being written to application or server logs. Automated log scrubbers sanitize incoming payloads before writing. Audit logs are retained for 12 months with bi-weekly security reviews.
• Endpoint Protection (EDR): All developer workstations run active Anti-Virus and Anti-Malware solutions with real-time scanning, daily definition updates, USB/removable media blocking, and full-disk BitLocker encryption.

6. Access Control & Non-Sharing Commitment

We enforce the Principle of Least Privilege and Role-Based Access Control (RBAC). Access to systems handling Amazon Information requires unique named user accounts and mandatory Multi-Factor Authentication (MFA). We never sell, rent, or transfer customer PII to third parties or marketing providers.

7. Incident Response & Amazon Escalation

Our Incident Response Plan mandates that in the event of any suspected unauthorized access, security incident, or data breach affecting Amazon Information, our Incident Management Point of Contact will notify Amazon Information Security immediately at [email protected] within 24 hours of detection.