Data Handling & Protection Policy

This policy outlines the technical and governance framework established by Ledermode GbRto classify, process, encrypt, store, and dispose of data accessed through our ecommerce software integrations and marketplace operational pipelines.

The objective is to ensure that seller confidential records and consumer personal data remain safeguarded throughout their lifecycle, maintaining strict adherence to Amazon's Data Protection Policy (DPP) and European data protection standards (GDPR / DSGVO).

Ledermode GbR classifies data into distinct risk tiers to ensure proportional safeguards:

• Class 1 — Public Information: Public catalog information, generic product descriptions, manufacturer brands (Gizeh, OCB, Clipper, Satya, Goloka, Golden, HEM), and public website pages. Handled without confidentiality restrictions.
• Class 2 — Internal Commercial Data: Warehouse stock quantities, pricing formulas, supplier replenishment schedules, and internal SKU mappings. Restricted to authenticated operational personnel.
• Class 3 — Confidential API Credentials: Amazon SP-API Client Secrets, OAuth Refresh Tokens, API private keys, and administrative server credentials. Guarded by hardware/secret encryption and zero-plaintext storage rules.
• Class 4 — Restricted Personal Data (PII): End-customer delivery recipient names, physical street addresses, postal codes, and city locations. Isolated with the highest protective controls and subject to automatic disposal post-fulfillment.

A foundational pillar of our architectural design is the strict separation between operational marketplace data (listings, inventory, prices) and customer Personally Identifiable Information (PII):

• Independent Database Schemas: Catalog and inventory records are stored in relational schemas completely divorced from order recipient delivery queues.
• Access Decoupling: Operational feeds updating product descriptions or inventory counts execute under service accounts that do not hold permissions to read customer delivery addresses.
• Temporary In-Memory Processing: Customer addresses required for dispatch are processed ephemerally during shipping label generation and not retained in non-volatile data stores.

All data exchanges and sensitive storage mechanisms utilize verified modern cryptography:

• Encryption in Transit: External communications with Amazon SP-API endpoints and user web traffic are strictly enforced over Transport Layer Security (TLS 1.2 or TLS 1.3) using strong cipher suites. Unencrypted HTTP traffic is systematically blocked or redirected.
• Encryption at Rest: Sensitive operational state, token caches, and backup archives are encrypted at rest using industry-standard AES-256 encryption.
• Key Isolation: Encryption keys are segregated from application code, managed via protected environment variables, and rotated periodically.

Access to data is governed by the Principle of Least Privilege:

• Every internal operator or automated job receives only the minimum permissions necessary for its assigned task.
• Administrative server access requires multi-factor authentication (MFA) and SSH key authentication.
• Shared or generic administrative accounts are strictly prohibited.
• Access permissions are revoked immediately upon role re-assignment or departure of personnel.

To ensure business continuity without compromising privacy obligations:

• System configuration and catalog mappings are backed up on encrypted off-site volumes.
• Customer PII is explicitly excluded from long-term backup archives.
• Backup restoration procedures are verified annually to confirm disaster recovery capability.
• Decommissioned storage drives are sanitized in accordance with DIN 66399 standards.

Inquiries regarding our data classification methodology or technical safeguards may be addressed to: