Data Security Overview
Who is responsible for the data
- 重庆利必达智慧科技有限公司Developer and operator of RapidaOS; connected entity for Amazon and TikTok Shop
- 重庆蝶小影科技有限公司Connected entity for Shopee
RapidaOS is developed and operated by the Rapida team (重庆利必达智慧科技有限公司). Store data from each marketplace is handled by the entity connected to that marketplace.
Company names are shown in their registered Chinese form; they have no official English names.
Overview
| Area | Current practice |
|---|---|
| Marketplace connections | Under marketplace review; no marketplace is connected yet. Once connected: read-only, authorized by the seller on the marketplace’s own page |
| Buyer personal data | Not retrieved |
| Data location | Mainland China, Alibaba Cloud China South 1 (Shenzhen) |
| In transit | HTTPS with HSTS |
| Sensitive fields | Bank account numbers and restricted files encrypted at the application layer with AES-256-GCM |
| Access | By role and assigned scope; out-of-scope queries return empty; administrators have no business-data access by default |
| Audit | Writes and sign-in security events are recorded in the audit log |
1. Marketplace connections
Our Amazon, TikTok Shop and Shopee integrations are still under marketplace review, and no store is connected yet. Once connected, they will work as follows:
- Sellers authorize access on the marketplace’s own authorization page. We never handle marketplace passwords or verification codes.
- Only read permissions are used. We do not change prices, inventory or advertising, issue refunds, or message buyers.
- Buyer names, addresses, phone numbers and other buyer personal information are not retrieved.
- Access tokens returned by the marketplace are treated as restricted data: stored with the application-layer encryption described below, kept out of logs, and never provided to AI models.
2. Accounts and access control
- Users sign in with a work email and password. Passwords are stored as salted scrypt hashes, must be at least 10 characters with both letters and digits, and common weak passwords are rejected.
- Signing in from a new device or network requires a one-time code sent to the work email (6 digits, valid for 10 minutes).
- Five failed attempts lock the account for 15 minutes and trigger an email notice; attempts per IP address per minute are capped.
- Finance processing and payment execution accounts follow stricter session rules: a verification code at every sign-in, sessions that expire after 24 hours, and suspension after 2 hours of inactivity.
- Every request is checked on the server against the user’s role and assigned scope. Out-of-scope queries return empty results.
- System administrators have no access to business data by default.
- Viewing a full bank account number requires a dedicated permission, and every view is recorded in the audit log.
- No one can approve a document they created or requested, and processing and payment cannot be carried out by the approver or the requester. This is enforced on the server.
- When an account is disabled, all of its sessions and trusted devices are revoked immediately.
3. Encryption and keys
- In transit: HTTPS across the site, with automatically issued and renewed certificates and HSTS.
- Application layer: bank account numbers and restricted uploaded files are encrypted with AES-256-GCM before they are written to the database or disk. Each ciphertext is bound to its record and cannot be decrypted if moved elsewhere. If the key is unavailable, the system refuses to handle this data rather than falling back to plaintext.
- Keys: master keys are kept only in an environment file on the server. The source repository contains no plaintext secrets.
4. Network and hosting
- Hosted in Alibaba Cloud’s China South 1 (Shenzhen) region.
- Only the entry service exposes web ports (80 and 443). The database and cache run on an internal network with no outbound access and no published ports.
- Uploaded files are stored on the same server’s data disk.
- Database schema changes are made only through migration files in the source repository.
5. AI models
AI assistance is still in development. The following rules are already enforced in code:
- The model service points by default to Alibaba Cloud Model Studio (Bailian) endpoints in mainland China.
- If restricted data is detected in the input, the AI run stops and is handed to a person.
- Sensitive values such as supplier names and amounts are replaced with placeholders before reaching a model; the mapping is never stored or returned to the model.
- AI can use read-only tools only. The system has no tools that let AI send messages, file declarations or make payments. Document extraction calls carry no tools at all.
6. Audit logging
- Writes record the user, time, record, values before and after, and source (user interface, import, scheduled job or AI).
- Security events such as sign-ins, verification codes, trusted devices and lockouts are recorded in the audit log.
- Audit records are append-only; the system provides no way to edit or delete them.
7. Revocation and deletion
- Sellers can revoke RapidaOS’s access at any time from the marketplace’s app authorization page. Once stores are connected, data retrieval for a store stops as soon as its authorization is found to be invalid, and the connection is marked “Not authorized”.
- Sellers can email support@rapidaos.com to request deletion of store data obtained through their authorization. We verify the requester’s relationship to the store, delete the data and confirm the outcome.
8. Measures in progress
The following are planned and not yet complete. They will move into the sections above once done:
- Off-site database backups to Alibaba Cloud object storage, with regular restore tests (scripts written, not yet in operation).
- Moving uploaded files to a private Alibaba Cloud Object Storage Service (OSS) bucket.
To report a security issue, email support@rapidaos.com.