数据保护政策Data protection policy

Quanzhou Shenlan Engine Network Technology Co., Ltd. publishes this policy to explain how we protect business data customers place in Shenlan Engine. In-product links to the data protection policy point here.

The Privacy policy covers notice, purpose, and rights for personal information. This policy covers ownership of business data, safeguards, subprocessors, incidents, retention, and deletion. Read them together. Rights over personal information follow the Privacy policy. Where a contract states a security duty or a disposal rule, the contract governs that point.

This policy does not cover our employees’ personnel records. Those records are not described to customers.

Customers keep the rights and interests in their business data. Providing the system does not give us ownership of a customer’s catalog, orders, images, shop authorizations, or production files.

We process that data to deliver the multi-tenant SaaS, on-demand production, and the open platform. The purposes are limited to the functionality you select, security, performing the contract and legal duties, and troubleshooting when you ask for support.

Where the data includes personal information, the customer is the personal-information handler and we process it on the customer’s instruction. Notice and a lawful basis are the customer’s duties. See processing on instruction in the Privacy policy.

What is actually stored depends on the functionality a customer turns on and the actions they take. The table lists categories the system may process. Not every customer produces every category.

• Process data only for the agreed purpose. Do not use customer business data for advertising unrelated to the service;
• Separate data by tenant. Do not provide one customer’s business data to another customer;
• Grant only the access a task needs;
• Do not sell customer business data;
• Do not use customer business data to train a general-purpose model offered to others.

• Only people authorized for their work may access customer data in production;
• People who can reach customer data are bound by confidentiality;
• Access changes when a role changes, and is removed when someone leaves;
• Customer data is not downloaded into an uncontrolled personal environment for a purpose other than support or a security investigation.

Technical measures follow the risk of the processing. This policy does not claim a particular security certification. If a certification status is relevant, it is stated in a separate note to the customer.

• The website and the service are accessed over HTTPS / TLS;
• Shop authorization credentials and open-platform keys are access-controlled, and the people who can see them in clear text are limited;
• Tenants are logically isolated, so one tenant’s actions do not read or write another tenant’s business data;
• Sensitive administrative actions are logged for security investigations and fault finding;
• Backups exist to the extent needed to run and restore the service. They age out on the rolling backup cycle.

Retention of personal information is in retention in the Privacy policy.

The customer’s administrator assigns roles inside the tenant. The system enforces those permissions. The customer should disable or change members who leave or change roles.

Our support staff open business data inside a customer tenant only in two cases: the customer has asked for support, or it is necessary to handle a security incident that is already underway. They look only at what the task requires.

We may use infrastructure, communications, and security providers to run the service. We require them to process data only on our instruction and to protect it in line with their role. Email 80505883@qq.com to ask for the current categories of principal providers. This page does not list vendor names that can change, so the public text does not fall behind the actual engagements.

After you connect a shop, catalog, order, and fulfillment data is exchanged with that platform according to your actions. Those platforms are sales channels you choose. They are not our subprocessors. Channels named on this website include Mercado Libre, SHEIN, TikTok Shop, Temu, Shopee, Ozon, and Shopify. Whether data moves, and which fields move, depends on that platform’s API and your configuration.

Data already synced to a third-party platform has to be handled on that platform. Deleting the copy in Shenlan Engine does not delete the platform’s copy.

Our operating company is in the People’s Republic of China. When a customer lists, pulls orders, ships, or coordinates production for an overseas shop, the related business data is sent to the overseas platform and its providers that the customer selected. We do not on our own sell or provide customer business data outside China.

Notice for cross-border personal information is in cross-border transfer in the Privacy policy. If we ourselves need to provide personal information outside China, we follow the procedures the law requires.

If an incident may leak, damage, or lose customer business data or personal information, we will:

1. contain it first: block the abnormal access, isolate the affected scope, rotate the related credentials, and fix the known flaw;
2. determine the tenants, data categories, and likely impact;
3. report to the competent authority when the law requires it;
4. notify affected customers without undue delay, including the nature of the incident, the categories involved, the likely impact, what we have done and will do, and steps the customer should consider;
5. keep a record of how the incident was handled.

Notice goes out after an initial check, and we do not hold it without reason. We will not replace unknown facts with guesses.

If the risk comes from a password, authenticator, or API key on the customer’s side, the customer should reset it immediately. We will help once we know, but we cannot hold the customer’s credentials for them.

During the service term we keep the business data the functionality needs. While the contract is in force, a customer can take a copy of data they are allowed to access through features the product already provides. Where an export does not exist yet, email a written request to 80505883@qq.com.

After the contract ends, the customer should export what they need to keep within the agreed period, or within a reasonable period if none was agreed. After that, we delete or anonymize business data in the tenant, except where:

• the law requires us to keep it;
• an unresolved dispute or security investigation requires it, and then only for that matter.

Copies in backups age out on the rolling cycle. They are not a reason to keep using the data. Data already synced to a marketplace has to be handled on that marketplace.

Specific periods for personal information are in retention in the Privacy policy.

The system works from the data that enters it and from the customer’s configuration. The customer is responsible for:

• the lawful basis for processing buyer, recipient, and similar personal information, and for informing those people;
• shop authorizations that come from someone entitled to grant them;
• catalog text, images, and artwork that do not infringe others’ rights and do not contain unlawful content;
• member accounts: disable people who leave, and grant permissions that match the role;
• passwords, authenticators, and API keys, including not placing live keys in a public repository or an uncontrolled chat;
• exporting, before the contract ends, the data the customer needs to keep.

An open-platform key stands for the tenant’s permission to call the API. A leaked key is permission for someone else to operate shops, catalogs, or orders within that key’s scope.

• Use a separate key per system, and grant only what that system needs;
• Rotate a key when staff change or when a leak is suspected;
• We keep call logs to authenticate, investigate security issues, and locate faults. They are not used to profile anyone for an unrelated purpose.

Endpoint scope, authentication, and examples follow the open-platform documentation and the contract. If a document and this policy differ, the contract governs security duties and disposal, and the documentation governs how the API behaves.

We may update this policy when the product, subprocessors, the law, or our processing changes. The new text is published on this page, and the effective date and version at the top are updated. If a change materially increases a customer’s security duties or changes how data is disposed of, we will say so by a notice on this website, in the product, or by email, as appropriate.

Email us if you need a separate data-processing clause, or help with a security incident. WeChat is for sales conversations.

• Operator: Quanzhou Shenlan Engine Network Technology Co., Ltd.
• Address: Room 707, Building 2, Xingyuehui Xingyuecheng, No. 216 Jinqi Road, Fengze District, Quanzhou, Fujian
• Email: 80505883@qq.com
• Phone: 15375837555
• Companion document: Privacy policy