Security policy · DCE-06
Data Classification and Encryption Policy
1. Purpose and scope
This policy defines how Enigmatech Mexico SAPI de CV ("Enigmatech") classifies the information it handles, how each class must be protected, and the encryption we apply to sensitive data in transit and at rest. It applies to all information handled by personnel, systems and subprocessors on our behalf. It supports the Information Security Policy.
2. Classification levels
| Level | Definition | Examples |
|---|---|---|
| Restricted | Disclosure could seriously harm individuals, customers or Enigmatech, or break a legal or contractual obligation. | Personal data of customers' buyers, employees and end users; data obtained from Amazon, TikTok Shop and other sales channels (buyer names, shipping addresses, postal codes, phone numbers, email addresses, order contents); passwords, access tokens, API keys and encryption keys; tax files and electronic signature certificates; sensitive personal data such as biometric templates where a customer enables that feature. |
| Confidential | Internal business information whose disclosure could harm a customer or Enigmatech. | Customers' business data (products, prices, inventory, sales figures), source code, infrastructure configuration, security logs, contracts. |
| Internal | Information meant for personnel only, with low impact if disclosed. | Internal procedures, non-sensitive operational notes, team plans. |
| Public | Information approved for publication. | Published policies, marketing material, public documentation. |
Customer data is Restricted or Confidential by default. When in doubt, use the higher level. The owner of an information asset assigns its level, and the Security Lead resolves disputes.
3. Handling rules
| Activity | Restricted | Confidential | Internal |
|---|---|---|---|
| Storage | Only in approved production systems, encrypted at rest. Never on personal devices, personal accounts or removable media. | Approved company systems only. | Approved company systems only. |
| Access | Named people with a documented need; MFA required. | Personnel who need it for their role. | Personnel. |
| Transmission | Encrypted channels only (TLS). Never by personal email or chat. | Encrypted channels only. | Company tools. |
| Sharing with third parties | Only with approved subprocessors under a data protection agreement, or on the customer's documented instruction. | Under a confidentiality agreement. | With approval. |
| Logging | Secrets and tokens are never written to logs; personal data in logs is kept to the minimum needed. | As needed. | As needed. |
| Disposal | Secure deletion under the retention schedule; devices are wiped before reuse or disposal; paper is shredded. | Secure deletion. | Normal deletion. |
4. Encryption in transit
- Every public endpoint of the Platform, including its APIs and webhooks, requires HTTPS with TLS 1.2 or higher, and TLS 1.3 wherever both ends support it. Plain HTTP is redirected to HTTPS, and weak protocols and ciphers are disabled.
- Traffic between our edge network (Cloudflare) and our origin servers is encrypted.
- Connections from our servers to the database and to third-party APIs (including the Amazon Selling Partner API, TikTok Shop, payment processors and email providers) use TLS.
- Personnel access production systems only over encrypted channels (HTTPS consoles, SSH).
5. Encryption at rest
- The production database, its backups and file storage are encrypted at rest with AES-256 by our infrastructure providers.
- Tax files kept in object storage are in private, encrypted buckets.
- Third-party credentials, including Amazon (Login with Amazon) refresh tokens and client secrets, TikTok Shop access and refresh tokens, app secrets and webhook secrets, are stored in the managed secrets vault, which encrypts them with authenticated encryption. Database tables keep only references to the vault entries.
- User passwords are never stored; only salted hashes are kept by the authentication provider.
- Endpoints use full-disk encryption (see the Endpoint Protection Standard).
- Where the mobile apps must hold sensitive captures offline, they encrypt them on the device (AES-GCM) until they are sent.
- Approved algorithms are AES (GCM, CBC with a random IV, or XTS) with keys of 128 bits or more (we use 256 bits) and RSA-OAEP with keys of 2048 bits or more. DES, RC4, Blowfish, Twofish and RSA keys shorter than 2048 bits are not allowed.
6. Key management
- Encryption keys for the database, storage and vault are managed by the infrastructure providers' key management systems, which cover key generation, storage, rotation and revocation. Keys are accessible only to the providers' and our own services, never to application code or personnel, and are rotated at least once a year.
- Application secrets and API credentials are generated with a cryptographically secure random generator, are unique per environment and are rotated at least once a year, when a person with access leaves, when a compromise is suspected, and after any incident that could have exposed them.
- Only the Security Lead and the named engineers who run production can manage secrets.
7. Data minimization
We collect and keep only the personal data needed for the purpose a customer uses the Platform for. From Amazon, TikTok Shop and other sales channels we request only the data needed to manage the seller's products, inventory, orders, fulfillment, cancellations and returns. Data obtained from each channel is tagged with its origin (the sales channel and the channel's own identifiers), so it can be located, protected, retained and deleted according to the Data Retention and Deletion Policy. Personal information obtained from Amazon is never stored on removable media, endpoints or public links.
8. Exceptions and enforcement
Exceptions follow the process in section 7 of the Information Security Policy. Mishandling Restricted data is a serious violation and may lead to disciplinary action.