Privacy Policy
This policy describes how Hangzhou Qiwang Technology Co., Ltd. collects, uses, stores, protects, shares and deletes personal data in connection with Qiwang AdPilot, our Amazon advertising automation service.
Controller: Hangzhou Qiwang Technology Co., Ltd., registered address Room 628, Building 5, Xixi Shouzuo, Jiangcun Subdistrict, Xihu District, Hangzhou, Zhejiang, China, unified social credit code 91330105MA2GK0QXXD, is the data controller for the personal data described in this policy.
Contact: For any privacy question, write to support@qiwangkj.com. For security or vulnerability reports, write to secure@qiwangkj.com.
1. Scope
This policy applies to the Qiwang AdPilot service, the qiwangkj.com website, and the business relationship between us and the sellers who use the service. Where a customer account is used by us as a processor on behalf of the seller, we process that data only on documented instructions from the seller.
This policy does not cover the Amazon services themselves. Amazon is an independent controller of the data held in your Amazon account, and Amazon's own privacy notice governs that data. We are not a party to, and we do not amend, the agreement you have with Amazon.
2. Data we collect
2.1 Data collected through your authorisation
When you authorise the service against your Amazon advertising accounts through the official Amazon authorisation flow, we are granted permission to read and, where you enable managed execution, to modify advertising resources in those accounts. The data this makes available to us is limited to the following categories.
| Category | Specific fields read | Customer personal data |
|---|---|---|
| Advertising entities | Campaign, ad group, ad, keyword, target and portfolio identifiers and configuration | No |
| Advertising performance | Impressions, clicks, spend, sales, orders, attributed conversions, cost per click, average order value, ACOS, ROAS | No |
| Search terms | Customer search query text that a shopper entered and that matched your advertised product | No. Search terms do not contain buyer identity |
| Account identifiers | Amazon profile ID, marketplace ID, advertiser account ID, account name, currency, timezone | No |
| Change history | Every change the service applies, including previous value, new value, triggering rule, timestamp and API response | No |
2.2 Data collected directly from you
- Contact details: Name, business email address, phone number, company name and role, collected when you submit the contact form or correspond with us by email.
- Account and billing records: The name, email address and business entity of each user of the service, the plan they are assigned to, and the invoice and payment status associated with that plan.
- Service telemetry: Feature usage events such as which recommendation categories were opened and whether a proposal was approved, together with timestamps and an account reference. Telemetry does not contain buyer personal data.
- Technical data: IP address, user agent, browser type and request logs collected when you use the website or log in to the service.
2.3 Data we deliberately do not collect
The service is designed so that certain categories of personal data are never reachable through our integration. We do not request, and our authorisation scope is not used to read, any of the following.
- Buyer names, delivery addresses, postal codes, phone numbers or email addresses
- Order-level personally identifiable information of any kind
- Your Amazon account password, two-factor authentication codes or security answers
- Payment card numbers or bank account details belonging to you or to your buyers
- Data belonging to your employees or other personnel
2.4 Data we do not ask you to provide
You are never asked to provide the personal data listed above. If you choose to send additional business information to us for analysis purposes, for example margin or procurement cost figures, that information is treated as confidential business data under the same protections described in this policy and is deleted on the same schedule as the other service data.
3. How we use the data
We use collected data only for the purposes below. We do not sell personal data, and we do not use advertising data for any purpose other than delivering the service to the account it belongs to.
- To deliver the service: Analyse advertising performance, generate recommendations, apply changes you have approved, and produce reports for you.
- To operate and secure the service: Maintain the service, enforce your guardrails, prevent abuse, and detect unauthorised access.
- To support you: Respond to support requests at support@qiwangkj.com, including diagnosing issues with an authorisation or an applied change.
- To comply with legal obligations: Meet applicable tax, accounting, and regulatory record keeping requirements.
- To improve the service: Use aggregated and de-identified telemetry to understand which recommendation categories are useful. Telemetry is not used to build advertising audiences, and it is never combined with buyer personal data: we do not request a Restricted Data Token, so the interface does not hand us buyer identity fields.
We do not use automated decision making that produces legal or similarly significant effects for individuals. The service operates on advertising entities, not on people.
Legal bases. Advertising data within the scope of your authorisation is processed because it is necessary to perform the contract: we cannot provide the service to you without processing it. Technical support and security logs are processed on the basis of our legitimate interest in operating the service safely and diagnosing faults. Tax and accounting records are processed to meet a legal obligation. Anything else is processed on the basis of your consent, which you may withdraw at any time; withdrawal does not affect processing carried out before the withdrawal.
Applicable law: We comply with every law that applies to this business, including data privacy and data protection laws, such as the Cybersecurity Law of the People's Republic of China and the Personal Information Protection Law of the People's Republic of China. Where one of those laws applies to a specific situation (for example the GDPR requirements that come with serving sellers in the European Union), we follow that law.
4. How we store the data
- Location: Service databases are hosted in data centres located in mainland China, and backups are stored in the same region. Advertising performance data read through the Amazon Ads API is transferred from Amazon to our servers in that region for processing.
- Encryption: Data in transit is protected with TLS 1.2 or later. Data at rest is encrypted using AES-256 or an equivalent industry standard. Amazon API credentials are stored in a dedicated secrets store, never in application configuration files, source code, logs or URLs.
- Access control: Access to customer data is restricted on a need-to-know basis and granted per team member by role. Access is reviewed when a team member changes role or leaves the company. Every access to customer data is logged.
- Separation: Data belonging to different customers is held in separate logical partitions. A customer cannot access data belonging to another customer, and the service does not use one customer's data to train or tune a model used for another customer.
- Token handling: Authorisation tokens are held in an encrypted secrets store. Tokens are never written to client-side code, never included in log output, and never passed in a URL or query parameter.
5. How we protect the data
We apply the following technical and organisational measures. Each measure is described so that a reviewer can assess whether it addresses a specific risk.
| Measure | How it is implemented |
|---|---|
| Least privilege | Each service role is granted only the permissions required for its function. Read-only analyst roles cannot trigger changes. Write-capable roles cannot alter permissions, billing or customer contact data. |
| Approval and guardrails | Automated changes are bounded by limits you configure: maximum percentage change per adjustment, maximum daily spend, and target ACOS. Changes outside those bounds are blocked before the API call is made. |
| Reversibility | The previous value of every changed entity is recorded before the change is applied, so that an incorrect change can be identified and reversed. |
| Audit logging | Every applied change is recorded with the account, the rule that triggered it, the previous and new values, the timestamp, the acting user and the API result. Audit records are tamper-evident and cannot be edited by service operators. |
| Credential rotation | Application credentials are rotated on a scheduled cycle before expiry, with a controlled overlap window so that no live request fails during rotation. |
| Rate limiting and backoff | Outbound API calls are throttled and retried with exponential backoff, which limits the blast radius of a malfunctioning rule and reduces the risk of duplicate or partial changes. |
| Idempotency | Each scheduled action carries a unique identifier so that a repeated trigger cannot produce a duplicate change. |
| Segregated duties | Personnel with production access to customer data are not the same people who administer billing. Access reviews are performed at least quarterly. |
| Incident response | We maintain a documented incident response procedure covering detection, containment, investigation, notification to affected customers, and remediation, with a defined severity classification and escalation path. |
| Personnel | Staff with access to customer data are bound by confidentiality obligations in their employment terms and are required to complete data protection training. |
6. How we share the data
We do not sell personal data. We share data only in the following situations, and only to the extent necessary.
- Infrastructure processors: We use vetted cloud infrastructure providers to host the service. These providers act as subprocessors and process data solely on our documented instructions, under contractual confidentiality and security obligations. The current categories are: cloud hosting and storage, email delivery, and error monitoring. A current list of subprocessors is available on request at support@qiwangkj.com.
- Amazon: The advertising data originates with Amazon and is returned to Amazon when we apply changes. Your authorisation and the resulting API calls are governed by your agreement with Amazon and by the Amazon Ads API terms.
- Professional advisers and authorities: We may disclose data to professional advisers, auditors, regulators or courts where required by law or necessary to establish, exercise or defend legal claims. In those cases we will disclose only what is required.
- Corporate transaction: If we are involved in a merger, acquisition or sale of assets, we will give you advance notice and require the successor to honour this policy.
We do not share your advertising data with other sellers, do not sell audience data, and do not provide advertising data to third parties for their own advertising purposes.
7. How the data is deleted
Authorisation validity and renewal: These come from two different interfaces and should not be treated as one rule. Under the Amazon Ads API, a third-party application must obtain your consent again every 365 days. Under the Selling Partner API, Amazon baselines access keys every 90 days and deletes any key that has not made a successful call in that period, which means it has to be re-applied for.
So we handle the two differently. Before the 365 days are up, we remind you through the contact details you have given us. Reauthorising keeps the service running and no configuration needs to be redone. If an authorisation is never renewed, it lapses, we stop API access, and the data is then deleted on the schedule below. Revocation and expiry are different things: revocation is something you do, expiry happens on its own, and both are handled on the same timetable.
- On revocation: When you revoke authorisation in the Amazon Ads console, we stop all API access within 24 hours. Raw advertising performance data is deleted within 30 days of revocation.
- On termination: When a service agreement ends, advertising performance data and credentials are deleted within 30 days. Audit records are deleted within 24 months, except where retention is required by law.
- When Amazon requires deletion: On notice from Amazon requiring deletion, the affected data is permanently and securely deleted within 30 days, including any live online instances.
- Your right to export and erasure: You can export your audit log and configuration at any time while the service is active. You can request erasure of remaining personal data by writing to support@qiwangkj.com. We will respond within 30 days. We may retain a record where retention is required by law, and we will tell you when that applies.
- Backups: Data in encrypted backups is overwritten on a rolling cycle within 90 days. Backups are never used for any purpose other than disaster recovery.
8. Your rights
Subject to the laws that apply to you, you may have the right to access, correct, delete, restrict or object to the processing of your personal data, and the right to data portability. Because the data we hold on your behalf is advertising performance data that originates from your own Amazon accounts, most of these rights can also be exercised directly in the Amazon Ads console, where you remain the owner of that data.
To exercise any right, contact us at support@qiwangkj.com or use the contact page. We will verify your identity and the accounts you are asking about before acting on the request. If you are a seller that has authorised a service provider other than us, that provider is the party that holds your advertising data on your behalf, and requests concerning that data should be directed to them.
9. International transfers
Our primary service infrastructure is located in mainland China. Where personal data is accessed from, or transferred to, a location outside mainland China, we rely on an appropriate legal mechanism for the transfer and we apply supplementary measures where they are needed. Advertising data read through the Amazon Ads API is transferred from Amazon into our servers in mainland China in order to be processed for you.
10. Children
The service is a business tool intended for businesses and is not directed at children. We do not knowingly collect personal data from anyone under the age of 16.
11. Security disclosure
If we discover a breach of our own personal data, we will notify the affected customers without undue delay and in any case within the timeframe required by applicable law.
If an incident involves Amazon data, we handle it under Amazon's data protection requirements: we report it to Amazon within 24 hours of becoming aware of it, and unless Amazon asks us in writing, we do not notify regulators or customers on their behalf, nor do we describe Amazon's handling decisions publicly. Our customers own the data in their Amazon accounts and can exercise their rights over it directly in the Amazon Ads console or through Amazon's own channels.
Our security overview page describes our reporting channel for customers to raise a concern.
12. Changes to this policy
We update this policy when our practices change. The revision date is shown at the end of this page. For material changes we will notify customers by email before the change takes effect. Continuing to use the service after the effective date constitutes acceptance of the revised policy.
13. Contact us
If you have any question about this policy or about our handling of your data, contact:
The controller for the data described in this policy is the company named above, Hangzhou Qiwang Technology Co., Ltd. We have not appointed a separate data protection officer. Privacy matters are handled directly by the company's management: contact support@qiwangkj.com and we will pass the matter to the responsible person.
14. Cookies and local storage
This site uses no advertising cookies and loads no third-party analytics or ad network scripts. It loads no external scripts, fonts or images.
One value is stored in your browser: the interface language you chose, under the key qw_lang, so that your next visit opens the same language directly. It holds no personal data and is never sent to our servers, and you can remove it by clearing your browser data. Apart from that, this site sets no cookies and uses no localStorage, sessionStorage or other client-side storage to identify you.
Last updated: 22 October 2026. Version 1.0.
Our relationship with Amazon: Hangzhou Qiwang Technology Co., Ltd. is an independent software company. We are not affiliated with, endorsed by, or acting on behalf of Amazon or any of its subsidiaries, and we are not certified by Amazon. References to Amazon services identify the platform our software connects to. Your agreement with Amazon governs your use of Amazon services, and this site does not modify it.