Privacy Policy

Effective: 30 August 2026 / Last updated: 5 October 2026

Revolts ("we", "us") provides Revolts Analytics (the "Service"), a selling operations and analytics tool for Amazon sellers. This policy describes how we handle information in connection with the Service. It is published publicly and can be read without logging in.

1. Operator

2. Scope

This policy applies to information handled in connection with the Service and this website. Information handling on external sites reached from this site, including Amazon services, is governed by the policies of their respective providers.

3. Information we collect

3-1. Information provided when you contact us

When you make an enquiry, you may provide your name or trade name, company name, email address, and information contained in your message.

3-2. Information retrieved through the Amazon APIs

The Service retrieves the information below through the Amazon Selling Partner API (SP-API) and the Amazon Ads API, only for seller accounts whose owner has explicitly approved the connection of our application on the Amazon authorization (OAuth) screen. We do not retrieve information from accounts that have not granted authorization, and we do not scrape or otherwise collect information from Amazon websites.

Information Source Purpose
Order and sales data (order date and time, quantity, amount, currency, ASIN / SKU, order status) SP-API Aggregating sales and units, comparing periods, reconciling with advertising results
Product data (ASIN, SKU, title, listing price, category) SP-API Aggregation and display per product; identifying products for price updates
Pricing data (our own listing price, fee estimates) SP-API Calculating floor and ceiling prices; comparing before and after an update
Inventory data (FBA inventory quantity, fulfillable quantity) SP-API Identifying stock-outs and excess inventory; deciding inventory updates; advertising continuation decisions
FBA inbound shipment data (shipment plans, shipped units, received units, status) SP-API Reconciling expected and received inbound units; inventory planning
FBA outbound shipment data (ship date, units shipped, ASIN / SKU, fulfillment channel) SP-API Aggregating sales on a ship-date basis; decrementing inventory
Traffic data (sessions, page views, unit session percentage) SP-API Understanding traffic and conversion
Fee and settlement data (referral fees, FBA fees, refunds, monetary items in settlement reports) SP-API Profitability analysis
Advertising performance (impressions, clicks, spend, attributed sales, campaign settings) Amazon Ads API Calculating ROAS and TACoS, before/after comparison, detecting declining efficiency
Connection identifiers and credentials (seller ID, marketplace ID, access token, refresh token) Amazon (LWA) Maintaining the API connection to the authorized account

3-3. Information we update (write) through the Amazon APIs

For an authorized seller account, and according to rules the seller sets, we update only the two fields below. We never write any other field.

Field updated Destination Rules and limits
Listing price SP-API Follows the rules the seller sets per product. Always within the floor and ceiling prices the seller has set. Applies only to products the seller has explicitly designated
Inventory quantity SP-API Based on the seller's own inventory data. Stops sales when out of stock and resumes on restock. Applies only to products the seller has explicitly designated

Each update is recorded with the time, the product, the values before and after, and the rule applied, and the seller can review this history. We do not create new listings, delete listings, change product information such as titles, images or descriptions, or change advertising bids, budgets or campaigns. Sellers can change their settings or stop updates at any time.

4. We do not collect buyer PII

The Service does not retrieve, store or use personally identifiable information about buyers. Specifically, we do not request buyer names, shipping or billing addresses, phone numbers, email addresses (including buyer-anonymized addresses), payment information, or free-text fields written by buyers such as gift messages.

Our analysis uses only aggregable fields: amounts, quantities, timestamps and product identifiers. Where an API response or report contains buyer information fields, those fields are not stored and are discarded during processing. We never use information to identify an individual buyer, to contact buyers, or to provide buyer information to third parties.

5. Purpose of use

  1. To provide analysis, reports and screens to the seller who granted the authorization
  2. To update the listing prices and inventory quantities of that account according to rules the seller sets
  3. To verify operation, investigate and resolve incidents, and improve functionality and accuracy
  4. To respond to enquiries and matters relating to use of the Service
  5. To respond to requirements under applicable law or from public authorities

We do not use information beyond these purposes. Information retrieved through the Amazon APIs is not used for any purpose other than providing the Service to the owner of the seller account it came from.

6. Disclosure to third parties

We do not disclose information retrieved through the Amazon APIs, or information provided in enquiries, to third parties without prior consent, except:

  1. where required by law;
  2. where necessary to protect the life, body or property of a person and consent is difficult to obtain; or
  3. where Amazon makes a legitimate request under its policies or agreements.

We do not sell, lease or trade information, and we do not provide it to third parties for advertising or marketing purposes. We do not combine data belonging to multiple users and disclose it in a form that identifies an individual seller.

7. Subprocessors

We use cloud service providers for storage and processing. Before use, we confirm that appropriate technical and organisational safeguards are in place and that information will be handled to a standard equivalent to this policy. Subprocessors are not permitted to use the information beyond the purpose of the engagement.

8. International transfers

Depending on the configuration of the cloud services used, data may be stored in data centres outside Japan. In that case, encryption and access controls continue to apply. If you need to confirm the storage region, please contact us.

9. Security measures

10. Retention and deletion

Data is retained only for as long as the analysis requires. On termination of use, revocation of authorization, or a deletion request, we delete retained data and credentials within 30 days as a rule. Records that we are legally required to keep are deleted after the required period. Confirmation of deletion is provided on request.

11. Revoking authorization

You can revoke our application at any time from Manage Your Apps in Seller Central, and likewise from the Amazon Ads settings for advertising data. Once revoked, we stop retrieving new data from that account. If you also want data already retrieved to be deleted, please contact us.

12. Cookies and access logs

This website does not require a login and does not set cookies or tracking tools that identify or track visitors for advertising purposes. Our hosting provider may retain technical records such as access timestamps and IP addresses for a limited period for security and incident response. Where you use the analytics screens of the Service, cookies necessary to maintain a signed-in session may be used.

13. Compliance with Amazon policies

In using the Amazon Selling Partner API and the Amazon Ads API, we comply with the Amazon Data Protection Policy, the Acceptable Use Policy and the applicable developer terms. Where those policies conflict with this policy, the Amazon policies prevail.

14. Access, correction and deletion requests

To request access to, correction of, addition to, deletion of, or suspension of use of information we hold, please contact us. We will verify your identity and respond in accordance with applicable law.

15. Changes to this policy

We may revise this policy in response to changes in law, changes to Amazon policies, or changes to the Service. Revisions are published on this page together with the updated date. Users of the Service are notified separately of material changes.

16. Contact

See our Terms of Service for conditions of use, and the home page for what the Service does.