Welcome to Maixin Technology Co., LTD

Maixin Technology Co., LTD operates its own Amazon seller account and develops private internal tools to support Amazon store operations, including buyer communication, order workflow, 4PX self-fulfillment, shipment tracking, and delivery-related customer service.

This website provides public information for privacy, Amazon data handling, security practices, and internal fulfillment workflow documentation.

Amazon Data Policy Security Overview

About Maixin Technology Co., LTD

Maixin Technology Co., LTD has been operating on Amazon for several years and focuses on consumer electronics and accessory products. Our product categories include wireless earphones, HDMI splitters, VGA adapters, and other 3C digital accessories.

We operate our own Amazon seller account. Our internal systems are used only for our own store operations and are not provided to third-party sellers as a SaaS service.

To support day-to-day operations, we develop and use private internal tools for order workflow support, buyer communication workflow, 4PX self-fulfillment, tracking number management, and delivery-related customer service.

4PX Self-Fulfillment Workflow

Our business includes Amazon seller-fulfilled orders. We currently use 4PX as our logistics service provider and have our own 4PX API account. Our internal ERP project is intended to replace our existing third-party ERP workflow and support our own Amazon store operations.

Fulfillment Process

A buyer places an order on Amazon and the order enters our seller-fulfilled workflow.
Our internal ERP identifies Amazon orders that require seller fulfillment.
The system uses the minimum shipping-related information needed to create a logistics order, including Amazon order ID, SKU, item quantity, recipient name, shipping address, country/region, state/city, postal code, and necessary delivery contact details.
The system submits the necessary shipping information to 4PX through our 4PX API account to create an international logistics order.
4PX returns the logistics order number and tracking number.
Our operations personnel use the 4PX tracking number to complete the Amazon shipment confirmation workflow.
After shipment, the system uses the 4PX tracking number to follow shipment progress and support delivery-related customer service.
If there are delivery exceptions such as address issues, failed delivery, package pickup, returns, or buyer inquiries about package location, authorized personnel use the order and 4PX tracking information to resolve the issue.

Shipping-related Amazon information is used only for order fulfillment, logistics label generation, tracking management, shipment confirmation support, delivery exception handling, returns, and delivery-related customer service. It is not used for advertising, profiling, resale, data brokerage, or unrelated analytics.

Privacy Policy

Effective Date: April 21, 2026

This Privacy Policy explains how Maixin Technology Co., LTD collects, uses, stores, protects, retains, and deletes information processed through our internal operational tools and public website.

1. Scope

This policy applies to information processed through our internal systems used to support our own Amazon seller account operations, including order workflow support, shipment handling support, buyer communication workflow, tracking management, and delivery-related customer service.

2. Information We Process

Order-related operational information
Shipment and fulfillment workflow information
Shipping-related information required to create 4PX logistics orders
Buyer communication content and related metadata
Technical logs, support records, and security event records

3. Purpose of Processing

We process information only for legitimate internal business purposes, including order management, 4PX shipment preparation, tracking number management, buyer communication support, delivery exception handling, troubleshooting, compliance, and security monitoring.

4. Sharing

We do not sell or share Amazon information with third parties for their own independent marketing, advertising, resale, data brokerage, or unrelated analytics purposes.

For seller-fulfilled orders, shipping information required for delivery may be submitted to 4PX, our logistics service provider, only for the purpose of creating logistics orders, delivering packages, shipment tracking, delivery exception handling, and returns processing.

Where technical infrastructure providers are used for hosting or transmission, they act only as technical service providers supporting our internal operations.

5. Retention and Deletion

Amazon shipping-related PII is retained only for the period necessary for order fulfillment, shipment tracking, and delivery-related customer service. After delivery is completed and there are no open customer service, return, claim, or dispute issues, related PII is deleted or anonymized within 30 days. If there are unresolved delivery exceptions, returns, claims, or customer service issues, the maximum retention period is no longer than 90 days.

6. Security

We use administrative, technical, and organizational safeguards designed to protect information against unauthorized access, misuse, disclosure, loss, or alteration. These safeguards include access control, AES-256 encryption for data at rest where applicable, encrypted transmission, controlled credentials, logging, monitoring, and incident response procedures.

7. Contact

For privacy-related questions, please contact maixintec@gmail.com.

Amazon Data Handling Policy

This policy describes how Amazon-provided information is handled within our private internal ERP and operational tools.

1. Nature of the Application

Our application is a private internal ERP tool used only to support the operation of our own Amazon seller account. It is not offered as a public SaaS product and is not provided to third-party sellers.

The public website hosted at maixintec.com is used only to display company information, privacy policy, Amazon data handling policy, security overview, and contact information. It does not store Amazon information.

2. Categories of Amazon Information

Buyer communication content and related message metadata
Order status and fulfillment workflow information
Shipping-related information required for seller-fulfilled orders
Operational identifiers necessary to match Amazon orders with 4PX logistics orders and tracking numbers

3. Minimum Necessary Use

Amazon information is processed only to the minimum extent necessary for legitimate internal operational purposes such as checking order status, preparing 4PX shipments, generating or obtaining logistics labels, managing 4PX tracking numbers, supporting Amazon shipment confirmation workflow, and resolving delivery-related issues.

4. Use of Direct-to-Consumer Shipping Information

Shipping-related information obtained for seller-fulfilled orders is used only to create 4PX international logistics orders, associate the correct 4PX tracking number with the correct Amazon order, support shipment confirmation, follow shipment progress, and handle delivery exceptions such as failed delivery, address issues, pickup notices, returns, and buyer inquiries about package location.

5. Prohibited Uses

No advertising use
No unrelated profiling
No resale or onward transfer for unrelated third-party commercial use
No data brokerage
No unrelated analytics resale

6. Access Control

Access to Amazon information is limited to authorized personnel with a legitimate business need to know. Administrative access is controlled through individual credentials and follows the least privilege principle.

7. Storage, Retention, and Deletion

Amazon information is stored only on controlled systems used for internal operations. Public access to production data stores is restricted. Shipping-related PII is deleted or anonymized within 30 days after delivery is completed and no open issue remains. If an unresolved delivery exception, return, claim, or customer service issue exists, retention is limited to no longer than 90 days.

8. Logs

Application logs are designed not to intentionally store complete recipient names, complete addresses, phone numbers, or other full PII. Security-related logs are retained for at least 12 months. Access to logs is restricted to authorized personnel.

9. Incident Response

We maintain procedures to identify, contain, investigate, remediate, and review security incidents. If a security incident involving Amazon information is detected, Amazon will be notified within 24 hours through security@amazon.com in accordance with Amazon policy requirements.

Security Overview

Network Protection

The public website and internal ERP are separated. Namecheap hosts only the public website and policy pages and does not store Amazon information.
Systems handling Amazon information are configured to minimize public exposure.
Databases and internal file storage are not publicly accessible.
Firewalls and service-level access controls restrict unnecessary ports and services.
Administrative access is limited to authorized personnel through secure authentication.
Data in transit is protected using encrypted transport.

Encryption and Key Management

Amazon information stored at rest is protected using AES-256 encryption where applicable.
SP-API credentials, 4PX API credentials, encryption keys, and sensitive configuration data are not hard-coded in source code or public repositories.
Access to credentials and keys is restricted to authorized personnel.
Credentials and keys are rotated when leakage is suspected, when personnel access changes, or after a security incident.

Password and Access Control

Minimum password length: 12 characters.
Password complexity includes uppercase letters, lowercase letters, numbers, and special characters.
Administrative access is restricted to authorized personnel.
Multi-factor authentication is enabled where applicable.
Shared administrative accounts are not used for access to Amazon information.

Operational Security

Logging and Monitoring

Authentication, login, access, administrative actions, API calls, export/download actions, system errors, and security-related events are logged.
Monitoring is used to identify suspicious activity, abnormal IP access, repeated failed logins, high-volume access, abnormal exports, unauthorized access attempts, and system anomalies.
Security-related logs are retained for at least 12 months.
Logs are designed not to intentionally store full PII unless temporarily required for troubleshooting or audit purposes.

Backup and Recovery

Backups containing Amazon information are encrypted.
Backups are stored in a geographically separated backup location to support continuity and recovery.
Restore procedures include backup integrity checks, recovery steps, recovery validation, and access review.
Recovery Time Objective (RTO): 24 hours.
Recovery Point Objective (RPO): 24 hours.

Vulnerability Management

Code and configuration changes are reviewed before release.
Dependency checks, security checks, and operational testing are performed during the development lifecycle.
Critical vulnerabilities are targeted for remediation within 7 days.
High-risk vulnerabilities are targeted for remediation within 30 days.
Remediation progress is tracked until verified closure.

Incident Response

Identify and validate the suspected incident.
Contain affected systems, credentials, or accounts.
Review logs and assess potential impact.
Rotate affected credentials or keys where needed.
Remediate root cause and restore operations.
Document corrective actions and required notifications.
Notify Amazon within 24 hours at security@amazon.com if Amazon information is involved.

Contact

Organization: Maixin Technology Co., LTD

Primary Contact: Bean.H

Email: maixintec@gmail.com

Incident Contact: maixintec@gmail.com

Country: China