Privacy Policy

2. Information collected (Collected)

Users provide names, company names, contact details, email addresses, contract and billing information, and inquiry content when contacting us or contracting. The SaaS collects OAuth authorization information, activity records, authentication events and transient IP processing. We obtain Amazon data through SP-API after each seller authorizes access. We do not collect Amazon login passwords.

The SaaS processes full IPs transiently in transit and memory for abuse detection, discarding them at request end and within 15 minutes. Retained Amazon-data system logs exclude full IPs and other PII, except documented legal requirements specifying law, fields and expiry. Static-site delivery logs are a separate class.

Information obtained from Amazon

• Orders and sales: Order identifiers, creation dates, SKUs/ASINs, item quantities and sales totals by product. Operations and fields are reviewed; Japan postal codes are discarded after receipt without storage.
• Amazon Fulfillment: FBA available, reserved, inbound and unfulfillable inventory; inbound shipment identifiers, quantities and status; GET_FBA_MYI_ALL_INVENTORY_DATA inventory reports.
• Finance and Accounting: Transaction, fee, refund, deposit and settlement amounts, transaction dates, and GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2 settlement reports.
• Product Listing: SKUs/ASINs, product names and attributes, listing status and errors, quantities and the seller’s own listing prices.
• Selling Partner Insights: We display Japan marketplace participation from Sellers API getMarketplaceParticipations and account status (accountStatuses), order defect rate (orderDefectRate) and late shipment rate (lateShipmentRate) from the Seller Performance Report (GET_V2_SELLER_PERFORMANCE_REPORT). Metrics are limited to non-restricted aggregates and reporting periods returned for the authorized Japanese store; unavailable metrics are not displayed. We do not obtain buyer-level or free-text feedback reports or traffic reports requiring Brand Analytics.

The initial release requests no restricted roles and does not obtain restricted buyer PII such as names, street addresses, emails and phone numbers. In Japan, Orders API can still return postal codes without restricted roles; DPP classifies postal codes as PII. Orders v2026-01-01 searchOrders/getOrder use basic datasets without includedData; BUYER, RECIPIENT and PAYMENT are not requested. FULFILLMENT is also not requested; individual order shipping and fulfillment status is outside the display scope. FBA inbound shipment status comes from the separately listed Fulfillment Inbound API. Postal codes and other unneeded non-restricted location fields are discarded in memory before logs or storage. Unexpected restricted fields stop processing. FBA/FBM responses, free text and field combinations are reviewed before enablement. Seller identity and telemetry PII require applicable safeguards before enablement.

Amazon: Orders PII / Amazon: DPP

Role definitions: https://developer-docs.amazon.com/sp-api/docs/roles-in-the-selling-partner-api

Type-to-role mappings: https://developer-docs.amazon/sp-api/docs/role-mappings-for-types

Japanese order field rules: https://developer-docs.amazon/sp-api/docs/access-orders-pii

3. Purposes of use (Used)

• Names, contacts and contract information: registration, identity verification, contract administration, inquiries, support and important notices.
• Billing/payment information: invoicing, payment confirmation and legally required records.
• Authorization information and Amazon data: the authorizing seller’s order, listing, inventory and inbound management, financial reconciliation and store performance display.
• Activity, authentication and access logs: abuse prevention, troubleshooting, security monitoring and quality improvements to this service.

We explain purposes before directly collecting personal information through the relevant screen or notice. Changes beyond reasonably related purposes require prior consent unless a legal exception applies. Amazon data is used only as needed to serve the authorizing seller, never for data sales, advertising, external AI training or analysis/disclosure for other customers. Store comparisons are limited to authorized data within the same subscription.

Purposes of use: https://www.ppc.go.jp/personalinfo/legal/guidelines_tsusoku/

Amazon data use: https://sellercentral.amazon.com/solution-provider/policy?policyType=AUP&locale=en_US

4. Storage (Stored)

Cloud storage and provider countries: 日本 / Japan. Processing countries, including staff and suppliers, and safeguards addressing foreign environments: Japan. Access is limited to managed Japan-based staff and suppliers. We assess the legal system and protect data through contracts, access controls and annual reviews. Amazon data is attributed to its seller, tenant and source, separated and encrypted in access-controlled databases, object storage and backups. Authorization tokens are never stored on the public website or in browsers.

Retention is defined by data class. For Amazon operational data, we apply the shortest of the published ceiling of 90 days, the class-specific ceiling, purpose expiry and applicable deletion deadline. Superseded snapshots have a 30-day ceiling, reviewed business history a 12-month class ceiling, temporary data 24 hours and backups seven days, all subject to that shorter rule. The 30-day deletion deadline following the earliest applicable trigger takes precedence. Credentials, sanitized security logs and legal records are separately classified; that does not permit longer storage of raw business data or PII.

Tokens are retained only while authorization is valid and the service needs them. Personal and contract record terms: Inquiries are kept for at most one year after resolution; contract and billing records for at most seven years after termination. Unnecessary information is deleted sooner. Statutory retention identifies the law, fields and deadline and is separately controlled. The same deadlines apply to backups. Static-site logs are described below.

Source attribution and storage: https://sellercentral.amazon.com/solution-provider/policy?policyType=DPP&locale=en_US

5. Security measures (Protected)

The following are mandatory measures under our security policy.

• Organizational: designated accountable owner and Incident Management Point of Contact (IMPOC), handling rules, periodic access reviews, incident response and supplier oversight.
• Personnel: annual training, confidentiality obligations and access limited to staff with business need.
• Physical: managed devices/media, loss prevention, storage encryption on every handling device, screen lock within 15 minutes of inactivity, and secure disposal.
• Technical: WAF on public ingress, TLS 1.2 or later, AES-256 or approved equivalent encryption of data, backups and credentials at rest, KMS key management, MFA for all users, lockout for at least 30 minutes after no more than 10 consecutive login failures, monitoring, vulnerability assessments and penetration tests including APIs.
• Foreign environments: review of processing-country systems and safeguards through contracts and ongoing checks.

See our Security Policy. We explain specific measures on inquiry through the privacy contact to the extent that disclosure does not compromise security.

Security measures: https://www.ppc.go.jp/personalinfo/legal/guidelines_tsusoku/

Policy update effective 2026-08-25: https://developer.amazonservices.com/policy-update-for-sp-api

6. Sharing, outsourcing and foreign processing (Shared)

We do not conduct joint use. Personal data is not provided to third parties without prior consent unless a legal exception applies. We perform required verification and keep records of disclosures. Hosting, maintenance and payments may be outsourced within necessary purposes, with contracts, limited access and periodic assessment. Supplier names, countries, data and purposes: GMO Internet, Inc. (Japan): provision of the servers (Onamae.com VPS) for this site and the service. Data is processed and stored on servers in Japan. GMO Internet, Inc. (Japan): email service for receiving inquiries and requests, including sender names, contact details, message bodies and attachments, received and stored through its email service.

For email inquiries and requests sent to us, we receive and store sender names, contact details, message bodies and attachments through the email service of GMO Internet, Inc., and use them to respond and verify identity. Retention and deletion follow the personal-information terms above; we also delete the emails held in that service. Please do not include Amazon or Yahoo! Shopping purchaser information in messages or attachments.

Common exceptions for statutory retention or foreign disclosure and outsourcing do not apply to Yahoo! Shopping purchaser information. Subscriber contract and billing records and public static-site delivery logs are separate data classes; their rules do not authorize purchaser-information retention. All production-data processing and access, including credentials, by employees and contractors is limited to Japan. We do not disclose or outsource production data outside Japan or allow access from outside Japan.

Sharing and outsourcing: https://www.ppc.go.jp/personalinfo/legal/guidelines_tsusoku/

Foreign third-party disclosures: https://www.ppc.go.jp/personalinfo/legal/guidelines_offshore/

Foreign cloud environments: https://www.ppc.go.jp/all_faq_index/faq1-q10-25/

7. Deletion and revocation (Deleted)

You may revoke app authorization at any time through Seller Central’s Apps and Services. Collection, access and synchronization stop on revocation. We securely delete data within 30 days of the earliest deletion trigger, including revocation, contract termination, Amazon’s request, loss of entitlement or data becoming unnecessary. Any shorter applicable deadline takes precedence.

Deletion includes authorization tokens, production data, replicas, caches, queues, exports, supplier copies, snapshots and backups. Deletion and revocation records are reapplied during backup restoration to prevent reuse of deleted information. We record completion and provide certification if Amazon requests it. Legally required records are separately retained after documenting the law, fields and deadline, with access limited to the legal purpose, and deleted after that period. Subscription cancellation and authorization revocation require separate steps.

Deletion: https://sellercentral.amazon.com/solution-provider/policy?policyType=DPP&locale=en_US

Revocation: https://developer-docs.amazon.com/sp-api/docs/revoke-authorizations