Security & Data Protection
How KJT Fulfillment Hub protects seller and buyer data.
Encryption
TLS 1.2+ in transit. AES-256 at rest, including databases, file storage and backups.
Access control
Least privilege, role-based access, MFA and prompt de-provisioning.
Secrets
API credentials and tokens encrypted in a secrets store, never in code or browsers.
Incident response
Affected marketplaces notified within 24 hours of a detected incident.
Security program
Kaleb Jay Thoeny LLC maintains written information-security policies covering data classification, access control, encryption, secure development, change management, incident response, business continuity and vendor management. Policies are reviewed at least once a year and whenever our systems or marketplace requirements change. A named person within the company is responsible for security. Personnel with access to personal information receive security and privacy training when they join and at least yearly.
Data classification
| Class | Examples | Handling |
|---|---|---|
| Restricted | Buyer name, address, phone; API tokens | Encrypted, access-logged, minimum access, short retention |
| Confidential | Seller account data, design files, orders without personal data | Encrypted, role-based access |
| Public | Website content, public catalog data | No special handling |
Network and infrastructure
- Production systems run on managed cloud infrastructure in secured data centers.
- Firewalls and network rules allow only required inbound traffic; databases are not publicly reachable.
- Production, development and test environments are separated; real buyer data is not used for testing.
- Workstations used to access production run up-to-date operating systems, disk encryption and anti-malware protection.
Encryption
- All traffic to our website, platform and marketplace APIs uses HTTPS with TLS 1.2 or higher.
- Data at rest, including databases, file storage and backups, is encrypted with AES-256.
- Buyer personal information is never stored on removable media or personal devices.
Access control
- Role-based access limited to staff who need it (least privilege).
- Multi-factor authentication required for all administrative and production access.
- Unique accounts for each person; no shared accounts.
- Access reviewed at least every 90 days and removed within 24 hours when a person changes role or leaves.
- Each seller workspace is isolated so one seller's data cannot be accessed by another, enforced in the application and the database.
Credentials and tokens
- Marketplace API credentials and OAuth tokens are stored encrypted in a dedicated secrets store.
- Credentials are never hard-coded in source code, written to logs or sent to web browsers.
- Credentials are rotated when staff change or on suspicion of exposure.
- Tokens are deleted when a seller disconnects a store or revokes access.
Secure development
- Code changes are peer-reviewed and must pass automated tests before release.
- Dependencies are tracked and updated; known-vulnerable packages are patched.
- External actions (orders submitted to partners, updates to marketplaces) are idempotent to prevent duplicates.
Logging and monitoring
We log access to systems containing personal information and other security-relevant events. Logs do not contain secrets, are protected from tampering, are monitored for suspicious activity and are retained for at least 90 days.
Vulnerability management
- Dependencies and infrastructure are scanned for vulnerabilities at least every 30 days.
- Critical vulnerabilities are remediated promptly according to severity.
- Penetration testing is performed at least once a year and after major changes.
Data retention and deletion
- Buyer personal information is deleted or irreversibly anonymized within 30 days after order delivery, unless law requires longer retention.
- Other order data is kept no longer than 18 months.
- Marketplace account-deletion notifications, including eBay Marketplace Account Deletion notifications, are acknowledged and processed with permanent deletion.
- Individuals can request deletion on our Data Requests page.
Backup and continuity
Databases are backed up automatically with encrypted backups and point-in-time recovery. Restores are tested periodically. Backups follow the same retention limits as live data.
Incident response
We maintain an incident response plan that is tested at least once a year. When a security incident is detected we:
- contain the incident and preserve evidence;
- notify affected marketplaces within 24 hours of detection where their data is involved (for Amazon data, at security@amazon.com);
- investigate the root cause and remediate;
- notify affected sellers, individuals and authorities as required by law;
- review the incident and improve our controls.
Partners and vendors
Production and shipping partners receive only the information needed to fulfill an order. Hosting and service providers are selected for their security practices and are bound by confidentiality and data-protection obligations. We review vendors before use and when their services change.