JIMI
Security and data

How we handle Amazon data

AmzForge is a business tool for advertising and seller operations. It does not need personal data about Amazon buyers, and it does not ask for it. This page states what is collected, how it is protected, how long it is kept, and how it is deleted.

Applies to AmzForge and to the advertising service operated by GUANGDONG JIMI INTELLIGENT TECHNOLOGY CO., LIMITED.

What we do not request

No buyer personal data. No client passwords.

Advertising and seller operations data does not require identifying individual Amazon customers, so we do not request access to it.

By design

No buyer personal data

AmzForge does not request buyer names, shipping addresses, email addresses, phone numbers or payment details. Advertising reporting and seller business reporting do not expose them, and the platform is not built to receive them.

By design

No access to the client's Amazon password

Authorisation happens through Login with Amazon. AmzForge receives a token issued by Amazon; it never receives, stores or asks for the client's Amazon credentials.

By design

No scraping of Seller Central or the ads console

Data is read through Amazon's official advertising and selling partner APIs. The platform does not automate the browser interface of either console.

What is collected

Business data about the account, not about shoppers.

AuthorisationToken issued by Login with Amazon for the account that granted consent, the marketplace identifier, and the advertiser profile identifier Amazon assigns to that account.
Advertising dataCampaign, ad group, keyword and targeting configuration; impressions, clicks, cost, attributed sales and units; search terms; placement breakdowns; budget and bid settings.
Seller operations dataListing and catalogue attributes, inventory and fulfilment status, pricing, and settlement reports, for accounts that grant the corresponding scope.
Account and user recordsThe name and work email of the client contact and of the JIMI specialists assigned to the account, roles, and the audit record of their actions in the platform.

How it is protected

Controls that are in place now.

Encryption in transit and at rest

All API traffic uses TLS. OAuth refresh tokens are stored encrypted rather than in plain text, and access tokens are held only in memory with short expiry.

Per-account isolation

Each authorising account's data is stored and queried separately, keyed to its own account record. Access by one client organisation does not expose another's data.

Role-based access control

Every user operates under a defined role. Permissions are granted by function, and read access is separated from any change capability.

Human approval before any change

The platform prepares recommendations. Applied changes require an authorised specialist's approval, and each change records who approved it, when, and why.

Audit logging

Authentication events, data access and changes are logged with user, timestamp and object. Logs are retained for audit and are not edited.

Limited internal access

Access to client accounts is limited to the specialists assigned to that client. Staff access is authenticated and audited; shared credentials are not used.

Retention and deletion

How long data is kept, and how it goes away.

While the engagement is active

Advertising and seller data is retained for the duration of the engagement so historical reporting and benchmarking remain available.

After authorisation is revoked

When a client revokes the authorisation, or the engagement ends, the platform stops retrieving data for that account. Tokens for the revoked account are destroyed.

Deletion on request

A client may request deletion of their account data by writing to it@jimiyoupin.com from the contact address on the agreement. We confirm the request, delete the account's stored data, and confirm completion in writing.

Deletion timeline

Deletion is completed within 30 days of a verified request, including backups within the next backup cycle. Records that must be kept for accounting or legal reasons are limited to invoice and contract records, and are not advertising data.

Sharing and sub-processors

Who else touches the data.

We do not sell dataAccount and advertising data is never sold, rented or traded, and is not used to train third-party models.
AmazonData is retrieved from Amazon's APIs. Nothing is written back to a client account without a JIMI specialist's approval.
Infrastructure providersServers and storage used to operate AmzForge are provided by contracted hosting and cloud providers, bound to confidentiality and used only to host the platform.
Service providersEmail and business tooling providers used to communicate with clients and to issue invoices. They do not receive advertising data.
Legal disclosureData may be disclosed where required by applicable law, limited to what is legally required, and the client is notified unless prohibited.

Responsible entity

Who is accountable for the data.

GUANGDONG JIMI INTELLIGENT TECHNOLOGY CO., LIMITED

Room 2410, Qijiang No. 1, No. 1 Zhongshan 2nd Road, Shiqi District, Zhongshan City, Guangdong Province, China

Unified social credit code 91442000MA5116KG7H - it@jimiyoupin.com