01这份政策管什么What this policy covers
本政策由泉州市深蓝引擎网络科技有限公司制定,说明我们如何保护客户交由深蓝引擎处理的业务数据。产品内的数据保护政策入口指向本页。
《隐私政策》说明个人信息的告知、目的和权利。本政策说明业务数据的归属、安全措施、分包、事件响应,以及保存和删除。两份文件一起阅读。个人信息权利事项以《隐私政策》为准;安全义务和数据处置若合同另有约定,以合同为准。
Amazon 数据还受适用的 Amazon 协议与政策约束;合同不能降低这些要求。
本政策不覆盖我们员工人事数据。那类数据不向客户公开说明。
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.
Amazon data is also subject to the applicable Amazon agreements and policies; a customer contract cannot reduce those requirements.
This policy does not cover our employees’ personnel records. Those records are not described to customers.
02数据归属与角色Ownership and roles
客户保留其业务数据上的权利和利益。我们不因提供系统而取得客户的商品资料、订单、图片、店铺授权或生产文件的所有权。
我们为交付多租户 SaaS、按需生产和开放平台而处理这些数据。处理目的限于:提供您选用的功能、保障安全、履行合同和法定义务,以及在您提出支持请求时排查问题。
其中属于个人信息的部分,客户是个人信息处理者,我们按客户指示受托处理。告知义务和合法依据由客户承担,详见《隐私政策》的委托处理。
Amazon 数据使用范围
本次申请的 Amazon SP-API 角色包括 Shop Direct、商品信息、定价、FBA、买家沟通、评价请求、销售伙伴洞察、财务与会计、库存和订单、可持续认证、Amazon Shipping、AWD 及 Brand Analytics;另申请直接向消费者配送、税务发票和税务汇缴三项受限角色。功能计划在权限获批、卖家授权且完成开发和验证后开放;尚未发布的功能目前不可用。
按已授权功能,Amazon 数据可能包括商品及 A+ 内容、价格、库存、订单、履约和 FBA/AWD 货件、财务报告、买卖双方消息、评价请求、可持续认证资料、应用关联标识、Brand Analytics 汇总报告,以及连接所需的账号/站点标识和凭证。受限直接配送和税务功能可能处理 Amazon 返回的买家姓名、配送地址、电话、订单标识及适用的发票/税务字段;只在卖家授权和具体履约、开票或税务处理所必需的范围内处理。
Amazon 数据仅用于向授权卖家交付本网站描述的服务,按租户隔离。不出售或转授权数据,不跨卖家共享或建立汇总商业数据库,不用于广告定向或买家画像,也不用于与授权服务无关的业务。数据用途遵守 Amazon Acceptable Use Policy(包括 4.4、4.5 条)和卖家授权范围。
我们不发布或分享 Amazon 自身业务洞察,也不将这些洞察用于自身业务。客户授权取得的数据不用于我们的自营店铺、关联企业或孵化团队经营。Amazon 官方汇总报告仅在该报告允许的用途和授权范围内向对应卖家展示。
Amazon 信息须单独存储,或通过平台来源、租户及卖家授权等标识保持来源可识别;相关报告、缓存和导出副本也须可追溯,以便按授权范围控制访问和处理删除请求。
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.
Amazon data use
This application requests the Shop Direct, Product Information, Pricing, FBA, Buyer-Seller Messaging, Request a Review, Selling Partner Insights, Financial Accounting, Inventory and Order Tracking, Sustainability Certifications, Amazon Shipping, AWD, and Brand Analytics roles, plus the restricted Direct-to-Consumer Shipping, Tax Invoicing, and Tax Remittance roles. Features are planned for release after role approval, seller authorization, and development and validation; features not yet released are not currently available.
Depending on the authorized feature, Amazon Information may include catalog and A+ content, prices, inventory, orders, fulfillment and FBA/AWD shipments, financial reports, buyer-seller messages, review requests, sustainability documents, application-link identifiers, aggregate Brand Analytics reports, and account/marketplace identifiers and credentials needed for the connection. The restricted shipping and tax functions may process buyer names, delivery addresses, phone numbers, order identifiers, and applicable invoice or tax fields returned by Amazon, only as necessary for seller-authorized fulfillment, invoicing, or tax processing.
Amazon data is used only to deliver the services described on this website to the authorizing seller, isolated by tenant. We do not sell or sublicense the data, share it across sellers, create a shared commercial database, use it for ad targeting or buyer profiling, or use it for unrelated business purposes. Uses follow the Amazon Acceptable Use Policy, including sections 4.4 and 4.5, and the seller’s authorization.
We do not publish or share insights about Amazon’s business or use those insights for our own business purposes. Data obtained under a customer’s authorization is not used to operate our own shops, affiliates, or incubated teams. Official aggregate Amazon reports are shown only to the corresponding seller within the report’s permitted use and authorization.
Amazon Information must be stored separately or remain identifiable by source, tenant, and seller authorization. Related reports, caches, and exported copies must remain traceable for access control and deletion requests.
03数据范围Data in scope
实际保存哪些数据,取决于客户开通的功能和日常操作。下表是系统可能处理的类别,不是每一家客户都会产生全部类别。
| 类别 | 典型内容 | 谁决定用途 |
|---|---|---|
| 租户与账号 | 企业资料、成员、角色、权限 | 客户配置;我们为交付账号服务而处理 |
| 店铺 | 店铺标识、授权凭证、启停状态 | 客户授权连接后,按客户操作 |
| 商品与刊登 | 标题、图片、SKU、类目、属性、刊登任务 | 客户 |
| 订单与履约 | 订单、收件信息、面单、运单、异常记录 | 客户指示履约时 |
| 按需生产 | 设计文件、生产任务、供应商协同和账单数据 | 客户发起的生产流程 |
| 仓储 | 三方仓商品、库存、入库和出库记录 | 按项目开通的范围 |
| 开放平台 | 接口密钥、调用记录 | 客户创建密钥并发起调用 |
| Amazon Brand Analytics | 经授权获取的报告、站点、ASIN、指标、更新时间和导出记录 | 客户授权连接,按分析功能配置 |
| Amazon 店铺运营 | 商品与 A+、价格、库存、订单、FBA/AWD 货件、财务报告、消息、评价请求、认证资料和应用关联标识 | 卖家授权连接并选择具体功能 |
| Amazon 买家配送与税务(受限功能) | 接口返回的买家姓名、地址、电话、订单标识及适用的发票/税务字段 | 仅按卖家指示配送、开票或完成法定税务处理 |
| 运维日志 | IP、时间、错误和关键操作记录 | 我们为安全和排障而生成 |
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.
| Category | Typical contents | Who decides the purpose |
|---|---|---|
| Tenant and account | Organization profile, members, roles, permissions | The customer configures it; we process it to provide accounts |
| Shops | Shop identifiers, authorization credentials, enabled state | After the customer connects a shop, according to their actions |
| Catalog and listing | Titles, images, SKUs, categories, attributes, listing jobs | The customer |
| Orders and fulfillment | Orders, recipient details, labels, tracking, exception records | When the customer instructs fulfillment |
| On-demand production | Artwork, production jobs, supplier coordination, and billing data | The production flow the customer starts |
| Warehouse | Third-party warehouse products, stock, inbound and outbound records | The scope opened for that project |
| Open platform | API keys and call records | The customer creates keys and makes calls |
| Amazon Brand Analytics | Authorized reports, marketplace, ASIN, metrics, freshness, and export records | The customer authorizes the connection and configures analytics |
| Amazon seller operations | Catalog and A+ content, prices, inventory, orders, FBA/AWD shipments, financial reports, messages, review requests, certifications, and application-link identifiers | The seller authorizes the connection and selects specific features |
| Amazon buyer delivery and tax (restricted features) | Buyer name, address, phone, order identifiers, and applicable invoice/tax fields returned by the API | Only seller-directed shipping, invoicing, or legally required tax processing |
| Operations logs | IP address, time, errors, and records of sensitive actions | Generated by us for security and troubleshooting |
04保护原则Principles
- 只为约定的目的处理,不为与服务无关的广告使用客户业务数据;
- 按租户区分。不把一个客户的业务数据提供给另一个客户;
- 只授予完成工作所需的最小权限;
- 不出售客户业务数据;
- 不将客户业务数据用于训练对外提供的通用模型。
- 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.
05组织措施Organizational measures
- 只有因工作需要被授权的人员才能访问生产环境中的客户数据;
- 接触客户数据的人员负有保密义务;
- 岗位变化时调整权限,人员离职后收回权限;
- 不把客户数据下载到不受控的个人环境,用于与支持或安全排查无关的用途。
- 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.
06技术措施Technical measures
我们按处理活动的风险采取技术措施。本政策不表示我们已经取得某一项特定的安全认证。认证状态如有变化,以单独向客户提供的说明为准。
- 网站和系统访问使用 HTTPS / TLS;
- 店铺授权凭证和开放平台密钥采取访问控制,限制可以接触明文的人员范围;
- 租户之间做逻辑隔离,避免一个租户的操作读写另一个租户的业务数据;
- 对关键管理操作保留日志,用于安全排查和故障定位;
- 在提供服务所必需的范围内做备份,用于故障恢复;备份须遵守适用的数据保存和删除期限。
Amazon 信息的安全控制
以下安全控制已部署于处理相关数据的生产环境,并保留配置或测试记录。Amazon 模块目前尚未上线;启用前会按正式上线流程再次核验适用系统、权限和数据处理范围。本政策不表示我们已经取得特定安全认证。
- 生产网络采用分层防护。数据库和文件服务器不直接暴露于公网,置于私有网络或受控子网;公网入口由防火墙、安全组、WAF、端口与来源 IP 允许列表保护,并实施网络分段及 IDS/IPS 或等效检测和防护。管理员通过 VPN 或零信任网关及堡垒机访问,使用 MFA 和短时凭证;管理操作留有审计记录。开发、测试和生产环境相互隔离。
- 传输使用 TLS 1.2 或以上等安全协议。员工仅使用已登记并由公司管理的设备访问生产数据;终端启用 EDR、Windows Defender 恶意软件防护、磁盘加密、系统补丁和自动锁屏,员工不能自行禁用或卸载防护。防护支持时自动更新,否则至少每月更新;不活动最长 15 分钟锁屏。USB 存储默认禁用,获批的例外仅限加密的公司设备;个人电脑、手机和平板不得直接访问生产环境,开发人员不得直接连接生产数据库。
- 使用唯一企业账号、MFA 和基于职责、组织及店铺范围的最小权限控制,默认拒绝未经授权的访问;仅向经授权且确有业务需要的员工开放 Amazon 信息。买家姓名、地址、电话和邮箱等字段仅在卖家授权的履约(含与订单配送相关的售后)或法律允许的税务处理所必需时显示,并优先脱敏。权限申请经业务和安全负责人审批,访问、导出和变更均留有审计记录;至少每季度复核人员及服务账号权限。员工转岗或离职时立即停用或撤销账号与权限;连续登录失败触发限制、锁定和安全找回流程,授权人员至少每年完成安全和数据保护培训。
- 所有处理 Amazon 信息的系统统一执行密码策略:员工和管理员密码至少 14 位,包含大小写字母、数字和特殊字符,不得使用用户名、公司名、店铺名、个人信息或重复最近 10 次密码,不得共享。高权限账号至少每 90 天轮换一次;普通账号按风险策略定期更新。系统启用 MFA、失败次数限制和安全找回;员工离职或转岗时停用账号。服务账号禁止交互式登录。LWA/OAuth 令牌、SP-API 凭证、数据库密码和第三方密钥加密存入受控密钥库或云 KMS/HSM,按类型设置有效期并定期轮换、可审计撤销;不得硬编码或写入日志。
- 静态数据使用 AES-256-GCM 加密;买家姓名、地址、电话、邮箱和税务资料等敏感字段另行采用字段级加密。数据密钥通过 RSA-2048 或 ECC 封装,由独立云 KMS/HSM 管理;密钥生成、存储、访问、轮换、吊销和恢复均受权限控制并留有审计记录,应用不得硬编码或导出密钥。备份、归档及临时文件同样加密。
- 通过企业终端管理、EDR、DLP 和 SIEM 监控设备连接、文件下载、复制、打印、登录和异常数据传输。检测到未登记设备或异常操作时,向安全负责人及值班人员告警,并隔离终端、撤销会话和保留审计证据。未授权 Amazon 信息不得复制到个人设备、个人云盘、即时通信工具或未经批准的移动介质。
- 维护个人信息处理记录和季度资产清单;所有应用及基础设施变更经过测试、验证和审批,并限制可以执行这些操作的人员。代码和依赖项在每次发布前进行漏洞扫描;处理 Amazon 信息的网络、服务器、数据库和应用至少每 30 天扫描一次,重大变更后追加扫描。渗透测试至少每 365 天进行一次。
测试环境与 Amazon 买家个人信息
开发、测试和演示环境默认不使用真实 Amazon 买家个人信息,优先使用合成数据、匿名化数据或不可逆脱敏数据;生产数据不得直接复制到测试环境。只有在 Amazon 规则和适用法律允许、接口联调确有必要并取得业务及安全负责人书面批准时,才可使用最少必要的真实字段,并须设置明确期限,采取加密、令牌化或脱敏等保护措施。测试与生产环境隔离,使用独立账号、数据库和权限,启用 MFA,并加密传输和存储。日志、错误信息、截图及测试报告不得记录可读的买家姓名、地址、电话、邮箱或令牌。测试结束后立即删除临时数据及副本,并保留访问和删除审计记录。
日志、监控与调查
我们使用服务器日志平台和 SIEM 集中采集 Web/API 网关、身份认证、LWA 授权、数据库、对象存储、后台任务、终端和管理操作日志。日志记录同步时间、操作主体、权限变更、令牌使用事件、数据访问或导出、API 调用、成功或失败结果和异常行为,并限制访问、加密传输和保存,防止未经授权的修改或删除。日志不记录买家个人信息、密码、令牌值、密钥或完整请求/响应正文;必要的事件标识采用掩码或哈希,并避免识别买家,仅因法律要求的记录另行受控保存。监控异常登录、越权访问、批量下载、异常地点或时段访问、重复未授权调用、请求或读取量突增、终端接入和可疑数据外传,并通过安全平台、邮件、短信或企业微信向安全负责人及值班人员告警。
- 安全日志和审计日志至少保留 12 个月,并至少每 14 天复核一次;日志访问和导出均需授权并留痕;
- 调查安全事件时,我们保留相关日志、时间线、影响范围、处置决定和修复证据,完成根因分析和复盘后关闭事件。
漏洞管理
对数据库、API、服务器、依赖组件和终端进行定期漏洞扫描;代码和依赖项在每次发布前扫描,处理 Amazon 信息的系统至少每 30 天扫描一次,并在重大变更后追加扫描。渗透测试至少每 365 天进行一次,并在每次发布前及重大变更后开展。发现项纳入统一台账,记录来源、受影响资产、涉及的数据类型、严重级别、责任人、发现时间、整改期限、状态和证据。Critical 和 High 问题优先隔离并立即采取遏制措施;Critical 在发现后 7 个日历日内、High 在 30 个日历日内完成修复。Medium 和 Low 问题纳入版本计划。安全负责人定期检查进度和逾期事项;修复后由安全人员或独立测试人员复测,确认补丁、配置和权限生效后关闭工单。无法按期修复时,须先采取临时缓解措施并完成风险评估和书面批准;批准不延长 Critical 或 High 的修复期限。我们保留扫描和渗透测试报告、复测结果、变更记录,分析重复问题并改进安全控制。
| 严重级别 | 目标修复时限 | 处置要求 |
|---|---|---|
| Critical / 严重 | 发现后 7 个日历日内 | 立即评估并采取隔离、缓解或紧急修复措施 |
| High / 高 | 发现后 30 个日历日内 | 指定负责人、跟踪进度并完成复测 |
| Medium / 中 | 发现后 60 个日历日内 | 纳入版本计划并在发布前验证 |
| Low / 低 | 发现后 90 个日历日内 | 在风险可接受时随常规维护修复 |
我们将代码安全纳入完整的软件开发生命周期:开发阶段进行安全需求评审、代码审查和分支保护,并使用静态代码分析(SAST)、依赖与开源组件扫描(SCA)、敏感信息扫描、动态测试(DAST)及 API 安全测试。涉及 Amazon 信息的高风险漏洞必须在上线前修复或阻断发布。所有问题进入漏洞台账,记录影响、级别、责任人、整改期限、方案和验证证据,并按风险等级处置。运行期通过日志监控、入侵检测、依赖更新和定期扫描发现问题;发现后先评估影响,必要时隔离服务、关闭接口、撤销密钥或启用临时防护。修复后由安全人员复测并确认无残留风险;无法立即修复的问题须制定补偿控制并完成风险评估和书面批准。重大事件按响应计划调查、通知和复盘。
加密备份与恢复
生产环境位于腾讯云广州,数据库、对象存储和日志在腾讯云上海地域进行加密异地备份和归档。备份采用 AES-256 信封加密,生产与备份密钥分离,由独立云 KMS 管理,并使用最小权限、TLS 传输、不可变版本保留和逻辑隔离控制。备份保留与删除安排遵守本政策的 Amazon 专门规则,不以版本保护或滚动周期延长适用删除期限。
发生故障后,先隔离故障环境并校验备份完整性及访问权限,再依次恢复数据库、对象文件、配置和任务队列。完成数据一致性检查后切换流量,记录恢复过程和审计证据。目标恢复时间(RTO)不超过 2 小时,目标恢复点(RPO)不超过 15 分钟;我们定期执行恢复演练并根据结果改进。这些是恢复目标,不是每次故障的无条件服务承诺。
个人信息侧的保存期限,见《隐私政策》的保存期限。
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 support service operation and recovery and must follow applicable retention and deletion deadlines.
Security controls for Amazon Information
The following security controls are deployed in the production environment handling the relevant data, with configuration or test records maintained. The Amazon module has not launched. Before it is enabled, we verify the applicable systems, permissions, and data-processing scope through the release process. This policy does not claim a particular security certification.
- Production uses layered network protection. Databases and file servers are not directly exposed to the public internet and reside in private networks or controlled subnets. Firewalls, security groups, a WAF, port restrictions, source-IP allowlists, network segmentation, and IDS/IPS or equivalent detection and protection secure the network. Administrators use a VPN or zero-trust gateway and a bastion host with MFA and short-lived credentials; administrative actions are audited. Development, test, and production environments are isolated.
- Transfers use TLS 1.2 or higher or other secure protocols. Employees access production data only from enrolled, company-managed devices. Endpoints use EDR, Windows Defender malware protection, disk encryption, system patches, and automatic screen locking. Employees cannot disable or uninstall protection. Protection updates automatically where supported, otherwise at least monthly, and screens lock after no more than 15 minutes of inactivity. USB storage is disabled by default; approved exceptions use encrypted company devices. Personal computers, phones, and tablets cannot directly access production, and developers cannot directly connect to production databases.
- Unique company accounts, MFA, and least-privilege controls are scoped by job duties, organization, and shop, with access denied by default. Amazon Information is available only to authorized employees with a business need. Buyer names, addresses, phone numbers, and emails are shown only when necessary for seller-authorized fulfillment, including delivery-related after-sales support, or legally permitted tax processing, and are masked where possible. Business and security owners approve access requests; access, exports, and changes are audited. Personnel and service-account permissions are reviewed at least quarterly. Access is revoked immediately when an employee changes roles or leaves. Accounts lock after no more than 10 consecutive failed sign-ins, and authorized personnel complete security and data-protection training at least annually.
- All systems processing Amazon Information use a consistent password policy. Employee and administrator passwords contain at least 14 characters, including upper- and lower-case letters, numbers, and special characters; they must not contain a username, company name, shop name, personal information, or any of the last 10 passwords, and must not be shared. Privileged accounts rotate at least every 90 days; ordinary accounts are updated periodically under a risk-based policy. MFA, failed-sign-in limits, and secure account recovery are enabled. Accounts are disabled when personnel leave or change roles. Service accounts cannot sign in interactively. LWA/OAuth tokens, SP-API credentials, database passwords, and third-party service keys are encrypted in a controlled vault or cloud KMS/HSM, assigned type-specific expiration, periodically rotated, and revocably audited; they are never hardcoded or written to logs.
- Data at rest is encrypted using AES-256-GCM. Sensitive fields, including buyer names, addresses, phone numbers, emails, and tax information, also use field-level encryption. Data keys are wrapped using RSA-2048 or ECC and managed by an independent cloud KMS/HSM. Key generation, storage, access, rotation, revocation, and recovery are access-controlled and audited. Applications cannot hardcode or export keys. Backups, archives, and temporary files are also encrypted.
- Enterprise endpoint management, EDR, DLP, and SIEM monitor device connections, file downloads, copying, printing, sign-ins, and unusual data transfers. Detection of an unregistered device or suspicious activity alerts the security owner and on-duty personnel; affected endpoints are isolated, sessions revoked, and audit evidence preserved. Amazon Information must not be copied to personal devices, personal cloud drives, messaging tools, or unapproved removable media.
- We maintain records of personal-information processing and a quarterly asset inventory. System changes are tested, verified, and approved, and permissions to perform these duties are restricted. Code and dependencies are scanned before every release. Networks, servers, databases, and applications that handle Amazon Information are scanned at least every 30 days and after significant changes. Penetration tests are performed at least every 365 days.
Test environments and Amazon buyer PII
Development, test, and demonstration environments do not use real Amazon buyer PII by default. We prefer synthetic, anonymized, or irreversibly de-identified data, and do not directly copy production data into test environments. Real fields may be used only when Amazon rules and applicable law permit, interface testing makes them necessary, and business and security owners provide written approval. Only the minimum necessary fields may be used, for a defined period and with encryption, tokenization, or de-identification safeguards. Test and production environments are isolated, with separate accounts, databases, and permissions, MFA, and encryption in transit and at rest. Logs, errors, screenshots, and test reports must not contain readable buyer names, addresses, phone numbers, email addresses, or tokens. Temporary data and copies are deleted immediately after testing, with access and deletion audit records retained.
Logging, monitoring, and investigation
We use a server logging platform and SIEM to centrally collect logs from Web/API gateways, authentication, LWA authorization, databases, object storage, background jobs, endpoints, and administrative actions. Logs record synchronized timestamps, actors, permission changes, token-use events, data access or exports, API calls, success or failure, and anomalous activity. Access is restricted, transfers are encrypted, and logs are protected from unauthorized alteration or deletion. Logs exclude buyer PII, passwords, token values, keys, and full request/response bodies. Necessary event identifiers are masked or hashed without identifying buyers; legally required records are controlled separately. Monitoring detects unusual sign-ins, excessive access, bulk downloads, unusual location or time, repeated unauthorized calls, unexpected request rates or retrieval volumes, unregistered devices, and suspicious data exfiltration. Alerts reach the security owner and on-duty personnel through security platforms, email, SMS, or WeCom.
- Security and audit logs are retained for at least 12 months and reviewed at least every 14 days. Log access and export require authorization and leave an audit trail;
- For an incident investigation we preserve relevant logs, the timeline, affected scope, decisions, and remediation evidence, then complete root-cause analysis and a post-incident review.
Vulnerability management
We regularly scan databases, APIs, servers, dependencies, and endpoints for vulnerabilities. Code and dependencies are scanned before every release; systems handling Amazon Information are scanned at least every 30 days and after significant changes. Penetration tests are performed at least every 365 days, before each release, and after significant changes. Findings enter a central register with their source, affected assets, Amazon Information types, severity, owner, discovery date, remediation deadline, status, and evidence. Critical and High issues are prioritized for immediate isolation and containment; Critical findings are fully remediated within 7 calendar days and High findings within 30 calendar days. Medium and Low issues enter the release plan. The security owner checks progress and overdue items. Security personnel or independent testers retest fixes and close tickets after verifying patches, configurations, and permissions. Issues that cannot be fixed on time require interim mitigation, a risk assessment, and written approval; approval does not extend Critical or High deadlines. We retain scan and penetration-test reports, retest results, and change records, analyze recurring issues, and improve security controls.
| Severity | Target | Required action |
|---|---|---|
| Critical | Within 7 calendar days of discovery | Assess immediately and isolate, mitigate, or apply an emergency fix |
| High | Within 30 calendar days of discovery | Assign an owner, track progress, and verify the fix |
| Medium | Within 60 calendar days of discovery | Put the fix in the release plan and verify before release |
| Low | Within 90 calendar days of discovery | Address through routine maintenance where risk is acceptable |
We integrate security throughout the software-development lifecycle. Development uses security requirements reviews, code review, branch protection, static application security testing (SAST), software-composition analysis (SCA), secrets scanning, dynamic application security testing (DAST), and API security testing. High-risk vulnerabilities involving Amazon Information must be fixed before launch or block release. All findings enter the vulnerability register with impact, severity, owner, due date, remediation plan, and verification evidence. Runtime monitoring, intrusion detection, dependency updates, and regular scans identify further issues. We assess impact promptly and, where needed, isolate services, disable interfaces, revoke keys, or apply temporary controls. Security personnel retest fixes and confirm no residual risk; issues that cannot be fixed immediately require compensating controls, a risk assessment, and written approval. Major incidents are investigated, reported, and reviewed under the incident-response plan.
Encrypted backups and recovery
Production is in Tencent Cloud Guangzhou. Databases, object storage, and logs are backed up and archived in the geographically separate Tencent Cloud Shanghai region. Backups use AES-256 envelope encryption with separate production and backup keys managed by an independent cloud KMS, least-privilege access, TLS transfers, immutable version retention, and logical isolation. Backup retention and deletion follow the Amazon-specific rules in this policy; version protection and rolling cycles do not extend applicable deletion deadlines.
After a failure, we isolate the affected environment, verify backup integrity and access permissions, and restore databases, object files, configuration, and task queues in order. Traffic is switched after consistency checks, with recovery steps and audit evidence recorded. Target recovery time objective (RTO) is no more than 2 hours and target recovery point objective (RPO) is no more than 15 minutes. Regular recovery exercises inform improvements. These are recovery objectives, not unconditional service guarantees for every incident.
Retention of personal information is in retention in the Privacy policy.
07访问、权限与支持Access, permissions, and support
客户管理员负责分配本租户内的角色。系统按账号权限执行操作。离职或换岗的成员,应由客户及时停用或调整。
我们的支持人员只在两种情况下进入客户租户中的业务数据:客户提出了支持请求,或者为处理已经发生的安全事件所必需。查看范围限于解决问题所需的数据。
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.
08分包与第三方平台Subprocessors and platforms
我们可能使用基础设施、通信和安全方面的服务商来运行系统。服务商只能按我们的指示处理数据;获得 Amazon 数据访问前须开展安全尽职调查,并至少每年复评,执行不低于适用 Amazon 要求的安全标准。您可以发送邮件至 privacy@podboss.cn,索取当前实际服务商的名称、处理目的、数据范围、处理地区及保存与删除安排。
当前云基础设施服务商为腾讯云(Tencent Cloud)。生产环境位于中国大陆广州;异地加密备份存放在腾讯云上海地域,采用独立密钥、访问控制和传输加密。备份版本在配置保留期限内启用防篡改保护,并按 Amazon 数据删除和法定保存要求及时清除到期副本。恢复流程按数据库、对象文件、配置及任务队列顺序执行;目标 RTO 不超过 2 小时,目标 RPO 不超过 15 分钟,并定期开展恢复演练和改进。云服务仅按委托范围处理运行所需信息。
您连接店铺之后,商品、订单、履约和经授权的 Brand Analytics 数据会按您的操作与相应平台交换。这些平台是您选择的交易渠道,不是我们的分包方。现有渠道包括 Mercado Libre、SHEIN、TikTok Shop、Temu、Shopee、Ozon 和 Shopify;Amazon 功能在权限获批、开发测试完成并经卖家授权后启用。是否传输、传输哪些字段,取决于该平台的接口和您的配置。
已经同步到第三方平台的数据,需要您在该平台另行处理。我们删除深蓝引擎中的副本,不会自动删除平台侧的副本。
Infrastructure, communications, and security providers may help run the service and may process data only on our instruction. Providers require security due diligence before access to Amazon data and reassessment at least annually, with standards no less protective than applicable Amazon requirements. Email privacy@podboss.cn for current provider names, processing purposes, data scope, processing regions, and retention and deletion arrangements.
Our current cloud provider is Tencent Cloud. Production is in Guangzhou, mainland China, with geographically separated encrypted backups in Tencent Cloud's Shanghai region. Backups use separate keys, access controls, and encryption in transit. Versions are protected against tampering during their configured retention period, and expired copies are cleared in accordance with Amazon deletion deadlines and legal retention duties. The recovery runbook restores databases, object files, configuration, and task queues in order. Target RTO is no more than 2 hours and target RPO no more than 15 minutes; recovery exercises are performed regularly and used for improvement. Tencent Cloud processes information only within the scope of our instructions.
After you connect a shop, catalog, order, fulfillment, and authorized Brand Analytics data is exchanged with that platform according to your actions. Those platforms are sales channels you choose. They are not our subprocessors. Existing channels include Mercado Libre, SHEIN, TikTok Shop, Temu, Shopee, Ozon, and Shopify. Amazon features are enabled only after role approval, completed development and testing, and seller authorization. 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.
09跨境传输Cross-border transfer
我们的经营主体位于中华人民共和国。客户为经营境外店铺而发起刊登、拉单、发货或生产协同时,相关业务数据会传输到客户选择的境外平台及其服务商。我们不为无关目的出售或对外提供客户业务数据。
Amazon 商品、订单、履约、买家及税务数据和品牌报告的同步,以及云存储、日志和备份,可能涉及 Amazon 服务区域与实际部署地区之间的数据传输。实际接收方、地区、数据范围与控制须如实说明,并满足适用的授权、具体报告条款和跨境数据保护要求;卖家授权不替代法定义务。
个人信息的跨境告知,见《隐私政策》的跨境提供。如果我们基于自身业务需要向境外提供个人信息,会依法履行相应程序。
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, related business data is sent to the overseas platform and providers the customer selected. We do not sell or disclose customer business data for unrelated purposes.
Synchronization of Amazon catalog, order, fulfillment, buyer and tax data, and brand reports, cloud storage, logs, and backups may transfer data between Amazon service regions and actual deployment locations. Recipients, locations, data scope, and safeguards must be accurately disclosed and meet applicable authorization, report-specific terms, and cross-border data-protection requirements. Seller authorization does not replace legal obligations.
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.
10安全事件Security incidents
数据库被入侵、未授权访问、数据泄露,或其他可能导致客户数据泄露、毁损或丢失的事件,均进入事件响应流程。我们会:
- 识别并遏制:记录发现时间,保存不可篡改日志和必要快照,停用受影响账号及会话,阻断异常访问、隔离受影响数据/服务器/网络区域,并撤销或轮换泄露的 LWA/OAuth 令牌、API 密钥、加密密钥和数据库密码;
- 核实受影响的租户、数据类别和可能的影响;
- 在法律要求时向主管部门报告;
- 及时通知受影响的客户,说明事件性质、涉及的数据类别、可能的影响、已经采取和将要采取的措施,以及建议客户采取的步骤;
- 修复根因、从验证过的备份恢复并检查完整性,持续观察异常;保留时间线、复测与恢复证据,复盘后关闭事件。
如需向我们报告漏洞、数据泄露或其他安全问题,请联系 security@podboss.cn。安全负责人负责事件分级、证据保存、内部升级与对外通报。Amazon 初报不等待完整调查或根因确认:已知情况先报,未知事项标明待核实,随后持续更新。响应计划须至少每 6 个月复核并演练一次,并在重大基础设施、系统或控制变更后重新复核和验证。
Amazon SP-API 事件管理联系人(IMPOC)为李胜军,邮箱 lishengjun1@podboss.cn。
风险管理流程须至少每年由高级管理层审查,记录威胁与漏洞、可能性、影响、处置责任和整改。事件证据须记录采集时间、完整性校验、经手与移交及访问情况,维护证据保管链,并按适用要求向 Amazon 提供调查及整改记录。
如果事件涉及 Amazon SP-API 或 Amazon Selling Partner 数据,我们会在发现安全事件后 24 小时内通过 security@amazon.com 通知 Amazon,并在后续更新影响范围、已采取的遏制措施和修复进度。
如果风险来自客户侧的密码、验证器或 API 密钥泄露,客户应立即重置。我们在知悉后协助处置,但不能代替客户保管其自己的凭证。
Database compromise, unauthorized access, data leakage, and other events that may expose, damage, or lose customer data enter the incident response process. We will:
- identify and contain: record detection time, preserve tamper-resistant logs and necessary snapshots, disable affected accounts and sessions, block abnormal access, isolate affected data, servers, and network segments, and revoke or rotate compromised LWA/OAuth tokens, API keys, encryption keys, and database passwords;
- determine the tenants, data categories, and likely impact;
- report to the competent authority when the law requires it;
- 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;
- eradicate the root cause, restore from verified backups and check integrity, monitor for recurrence, and retain the timeline, retest, and recovery evidence for a post-incident review before closure.
To report a vulnerability, data leak, or other security issue to us, contact security@podboss.cn. The security owner coordinates classification, evidence preservation, internal escalation, and external notification. The initial report to Amazon does not wait for a complete investigation or root-cause confirmation: known facts are reported first, unknowns are identified, and updates follow. The incident response plan must be reviewed and exercised at least every six months and reviewed and verified again after material infrastructure, system, or control changes.
The Amazon SP-API incident management point of contact (IMPOC) is Li Shengjun at lishengjun1@podboss.cn.
Senior management must review the risk-management process at least annually, documenting threats, vulnerabilities, likelihood, impact, treatment owners, and remediation. Incident evidence requires collection times, integrity checks, custody transfers, and access records to maintain a chain of custody. Investigation and remediation records are provided to Amazon as applicable.
If an incident involves Amazon SP-API or Amazon Selling Partner data, we notify Amazon within 24 hours after detecting the Security Incident at security@amazon.com, and provide updates on scope, containment, and remediation.
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.
11保存、返还与删除Retention, return, and deletion
服务期间,我们保存交付功能所必需的业务数据。客户可以在服务期内通过系统已经提供的功能取得其有权访问的数据;系统暂时没有对应导出功能的,可以向 support@podboss.cn 提出书面请求。
除下述 Amazon 专门规则适用的数据外,合同终止后,客户应在约定或合理期限内自行导出需要留存的数据。期限届满后,我们删除或匿名化该租户内的一般业务数据,但下列情形除外:
- 法律要求继续保存;
- 为尚未了结的争议或安全调查必须保留,保留范围限于该事项。
一般业务备份按适用期限随滚动周期清除,不作为继续使用数据的理由;Amazon 数据的副本遵守下述专门规则。已经同步到电商平台的数据,请在对应平台处理。
Amazon 数据的保存与安全删除
Amazon 信息只在授权目的严格必要的范围和期限内保存。收到 Amazon 删除通知、卖家撤销授权或终止访问、我们不再有权处理,或相关服务参与资格终止/到期等适用事件发生时,以最早触发为准,立即停止不再获准的同步与使用,并最迟在 30 天内永久、安全删除相应信息,包括报告、缓存、导出文件、临时文件及所有在线或可联网副本。在线备份不得以滚动周期为由推迟该期限;其他介质按适用政策受限保存和安全处置。
删除采用 NIST 800-88 等适用标准的安全处置方式,需要时向 Amazon 提供删除证明。仅在法律要求时,按必要字段、目的和期限隔离保留相关记录;合同、一般争议或内部调查不构成继续保存全部 Amazon 数据的例外,也不以匿名化替代要求的安全删除。
本次另申请直接向消费者配送、税务发票和税务汇缴受限角色。若相关功能获批并开放,买家 PII 仅在订单履约、计算/汇缴税款、制作税务发票或其他法定义务所必需的范围处理;通常不得超过订单交付后 30 天。超过 30 天仅限法律明确要求,并只保留满足该法律所必需的数据、用途和期限。受托服务商和税务接收方仅可按授权或法律要求获得必要字段。
适用的安全审计记录与业务报告分开管理,仅保留安全调查所需的最小事件信息;不以日志保存为由保留报告正文、买家 PII 或凭证。上述 Amazon 专门规则优先于本政策及《隐私政策》中的通用保存期限。
安全日志和审计日志至少保存 12 个月,保存期间可供安全调查检索;超过期限后删除或去标识化,正在进行的安全调查或法律要求可以在必要范围内延长。
个人信息的具体期限,见《隐私政策》的保存期限。
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 support@podboss.cn.
Except for data subject to the Amazon-specific rules below, after the contract ends a customer should export what they need within the agreed period, or a reasonable period if none was agreed. We then delete or anonymize general 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.
General business backups age out within applicable deadlines and are not a reason to keep using data. Copies of Amazon data follow the specific rules below. Data already synced to a marketplace must be handled on that marketplace.
Amazon retention and secure deletion
Amazon Information is retained only to the extent and for as long as strictly necessary for its authorized purpose. Following the earliest applicable event—an Amazon deletion notice, seller revocation or termination of access, loss of our authority to process, or termination or expiration of participation in the Services—we stop synchronization and use that is no longer authorized and permanently and securely delete the relevant Information within 30 days. This includes reports, caches, exports, temporary files, and all live or network-accessible copies. Online backups cannot use a rolling cycle to extend this deadline; other media require restricted retention and secure disposal under applicable policy.
Deletion follows applicable sanitization standards such as NIST 800-88, with written destruction certification to Amazon when requested. Legally required records are isolated and limited to the necessary fields, purpose, and period. A contract, general dispute, or internal investigation does not justify keeping all Amazon data. Anonymization does not replace required secure deletion.
This application also requests the restricted Direct-to-Consumer Shipping, Tax Invoicing, and Tax Remittance roles. If approved and released, buyer PII is processed only as necessary to fulfill orders, calculate/remit taxes, produce tax invoices, or meet another legal duty; it is generally retained no longer than 30 days after order delivery. Retention beyond 30 days is limited to what the law requires, and only for the legally required data, purpose, and period. Processors and tax recipients receive only fields needed under the seller’s authorization or applicable law.
Applicable security audit records are managed separately from business reports and retain only the minimum event information needed for security investigation. Log retention does not justify keeping report bodies, buyer PII, or credentials. These Amazon-specific rules take precedence over general periods in this policy and the Privacy policy.
Security and audit logs are retained for at least 12 months and remain retrievable for security investigations. They are deleted or de-identified after that, unless an active security investigation or law requires a necessary extension.
Specific periods for personal information are in retention in the Privacy policy.
12客户侧责任What the customer handles
系统只能按进入系统的数据和客户的配置工作。下列事项由客户负责:
- 决定处理买家、收件人等个人信息的合法依据,并向个人履行告知义务;
- 保证店铺授权来自有权授权的人;
- 保证商品内容、图片和设计文件不侵犯他人权利,不含违法信息;
- 管理子账号,及时停用离职人员,按岗位分配权限;
- 保管密码、验证器和 API 密钥,不把明文密钥写入公开仓库或不受控的聊天记录;
- 在合同终止前完成自己需要留存的数据导出。
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.
13开放平台与凭证Open platform and credentials
开放平台密钥代表租户的调用权限。密钥泄露,等同于授权他人按该密钥的权限操作店铺、商品或订单。
- 为不同系统使用各自的密钥,只授予该系统需要的权限;
- 人员变动或怀疑泄露时,立即轮换密钥;
- 我们会记录调用日志,用于鉴权、安全排查和故障定位,不用于与服务无关的画像。
接口范围、鉴权方式和示例,以开放平台文档和合同为准。文档与本政策不一致时,安全义务和数据处置以合同为准,接口行为以文档为准。
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.
14政策更新与联系Changes and contact
我们可能因功能、分包、法律或处理方式变化更新本政策。更新后的文本公布在本页,并修改页首的生效日期和版本号。如果变更会实质加重客户的安全责任或改变数据处置方式,我们会通过网站公告、产品内通知或邮件等合理方式提示。
数据处理条款、隐私或删除请求请联系隐私邮箱;服务支持及数据导出请联系支持邮箱;漏洞及安全事件请联系安全邮箱。微信只用于商务沟通。
- 运营者:泉州市深蓝引擎网络科技有限公司
- 地址:福建省泉州市丰泽区金崎路216号星月荟星悦城2号楼707室
- 隐私、删除与数据处理条款:privacy@podboss.cn
- 客户支持与数据导出:support@podboss.cn
- Amazon SP-API 事件管理联系人(IMPOC):李胜军,lishengjun1@podboss.cn
- 漏洞与安全事件:security@podboss.cn
- 电话:15375837555
- 配套文件:隐私政策
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.
Use the privacy address for data-processing terms, privacy, or deletion requests; the support address for service assistance and data exports; and the security address for vulnerabilities or incidents. 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
- Privacy, deletion, and data-processing terms: privacy@podboss.cn
- Customer support and data exports: support@podboss.cn
- Amazon SP-API incident management point of contact (IMPOC): Li Shengjun, lishengjun1@podboss.cn
- Vulnerabilities and security incidents: security@podboss.cn
- Phone: 15375837555
- Companion document: Privacy policy