Scraping Prohibition
Effective Date: October 15, 2026 Version: 1.0 Applies to: All Developers, partners, and other persons who collect or seek to collect Platform data.
Article 1: Introduction and Scope
1.1 This document states a categorical prohibition: Platform data shall be collected only through the API under the Developer Agreement, and automated access to the Site is permitted only as the Company authorizes in writing. This document controls every question of unauthorized collection and unauthorized access in the event of a conflict with the Developer Agreement.
1.2 If a provision of this document conflicts with the Terms of Use, this document controls for its subject. Policies and help pages explain this document; they do not amend it.
Article 2: Definitions
2.1 In this document, terms defined in the Developer Agreement have the same meaning, and Circumvention: evasion of a rate limit under the API Rate Limits and Quotas, of an intake or access gate, of an address block, of a bot defence, or of authentication; defeat of a crawler instruction for bulk collection; use of a proxy network, a rotating client identifier, or a concealment tool to disguise automated traffic; discovery or use of an undocumented or internal interface to bypass the published API; an attempt to obtain a credential by repeated trial or to take over a session; or sharing of one Seller session among multiple addresses, devices, or operators as a pool.
Collection: obtaining, copying, storing, or indexing data. The violation is complete on Collection by a prohibited method, whether or not the data is later used.
Scraping: automated collection of Platform content or data by any means other than the documented API. Scraping includes collection by a bot or crawler, by a browser operated without a human directing each view, by parsing of page structure, by capture and text extraction from a rendered page, by harvesting of a feed presented for human reading, by systematic submission of search queries to enumerate product addresses, and by replay of recorded session traffic as an automated client.
Article 3: The Prohibition
3.1 All programmatic access to Platform data shall occur through the API under the licence in the Developer Agreement, at the limits in the API Rate Limits and Quotas. No other programmatic path is licensed. An internal data service of the Company is not a developer interface, and a credential for internal or service use in a Developer's possession is a breach by possession, in accordance with the Developer Agreement.
3.2 Scraping of the storefront, the Seller portal, the administration console, or any Platform surface is prohibited, regardless of the person performing it. The prohibition includes a Seller scraping the Seller's own storefront through the Seller's own session: the API is the auditable path for a Seller's data, and a session-driven collector is treated as abuse.
3.3 Data obtained by Scraping shall not be used, even if the same data is available through the API. The Data Use, Retention and Deletion deletion duties apply to the copy so obtained in accordance with Article 6.
3.4 Possession or distribution of a tool whose primary purpose is Circumvention against the Platform: including a session-pooling kit, a storefront collector offered for the Platform, and a proxy-rotation configuration prepared for the Platform: is prohibited and is itself a violation of this document.
Article 4: Sessions and Authentication
4.1 The following are Circumvention: (a) operating one Seller's session from infrastructure in multiple locations as a pool; (b) giving a live session credential to a third party who was not authenticated; (c) keeping a session alive after the Seller's logout or after the end of the Seller's relationship, for the purpose of continued polling; and (d) signing in as a Seller from a data-centre address range for the purpose of bulk reads.
4.2 An authentication failure is a direction to stop. Re-authentication through the normal sign-in procedure is the permitted response. Retry with rotated addresses, parallel sessions, or replayed tokens to defeat the failure is Circumvention.
Article 5: Crawlers and Limited Permissions
5.1 A general web crawler, including a search engine crawler, may access only what the Platform's crawler instructions permit. Those instructions are the complete statement of crawler permission; access beyond them is Scraping.
5.2 Crawler permission is not a data licence. Content indexed by a search engine remains the property of the Company or the owner concerned. Bulk extraction of catalog data through crawling: including a price, an inventory state, or a supplier signal: is Scraping even where the page fetch itself was permitted.
5.3 The only permissions under this article are: (a) search-engine indexing under clause 5.1, for the purpose of returning a person to the Platform; and (b) transient storage by an intermediary, such as a delivery network or a corporate proxy, in the ordinary course of delivering a page to the person who requested it. No permission arises under this document for: training a model on Platform content; building a competing or derivative catalog; monitoring a price or availability at scale; or research that stores the data. A person who requires catalog data for research or another purpose shall apply as a Developer and use the API. Any other automated access to the Site requires the Company's prior written authorization, which the Company may grant, condition, or refuse in its discretion.
5.4 Automation that operates the Platform interface on behalf of a person for that person's own viewing: including an assistive technology and a screen reader: is not Scraping. The test is whether the automation collects data at scale for storage, replication, or redistribution, as distinct from presenting a page to the person using it.
Article 6: Consequences and Tainted Data
6.1 Data obtained in violation of this document shall be deleted within seven (7) days of notice from the Company, with written certification of deletion delivered in the form the Data Use, Retention and Deletion requires. Continued use of such data after notice is a separate violation, and each day of continued use is a separate violation for enforcement purposes.
6.2 The Company reserves every right and remedy at law for unauthorized access and for misappropriation of catalog data, in addition to the measures in Article 9.
6.3 A Developer that requires a higher ceiling for a legitimate integration shall request a Tier change under the API Access Tiers or a limit increase under the API Rate Limits and Quotas, and shall not multiply sessions or addresses to obtain the capacity without approval.
Article 7: Liability
7.1 Exclusion of certain damages. To the fullest extent permitted by law, neither party is liable to the other for indirect, incidental, special, punitive, or consequential damages, or for lost profits, lost revenue, or loss of goodwill, arising out of or relating to this document, even if the party has been advised of the possibility of those damages.
7.2 Cap. To the fullest extent permitted by law, the Company's total liability arising out of or relating to this document shall not exceed the greater of (a) the amounts the Developer paid to the Company under this document in the twelve months before the event giving rise to the claim, or (b) one hundred dollars ($100).
7.3 Carve-outs. This article does not limit (a) a party's indemnification obligations under this document; (b) liability for fraud or willful misconduct; (c) amounts the Developer owes for Orders, fees, chargebacks, or refunds under this document; or (d) liability that cannot be limited under applicable law.
7.4 Essential purpose. The parties agree that this article allocates risk between them, that it is an essential part of the basis of their bargain, and that it applies even if a limited remedy fails of its essential purpose.
Article 8: Indemnification
8.1 Duty. The Developer shall indemnify, defend, and hold harmless the Company and its members, managers, employees, and agents from and against every claim, demand, action, loss, liability, judgment, settlement, cost, and expense (including reasonable attorneys' fees) arising out of or relating to: (a) the Developer's breach of this document, including Scraping and Circumvention by the Developer or by a tool the Developer operates; (b) the Developer's Applications and content; (c) the Developer's violation of any law or of the rights of any person; and (d) taxes for which the Developer is responsible under this document.
8.2 Procedure. The Company shall give prompt written notice of a claim under this article. The Developer shall control the defense with counsel reasonably acceptable to the Company. The Company may participate in the defense at its own expense. The Developer shall not settle a claim in a manner that imposes any obligation or restriction on the Company, or that does not release the Company fully, without the Company's prior written consent.
8.3 Survival. This article survives the termination of this document.
Article 9: Enforcement and Appeals
9.1 Investigation. The Company may investigate any suspected violation of this document. The Developer shall cooperate with an investigation and shall produce the records this document requires the Developer to keep. The Company does not publish the signals by which Scraping is detected; the categories are traffic shape inconsistent with human use, identity signals inconsistent with a genuine browser or a declared client, and control-evasion signals, including resumption of traffic from new infrastructure shortly after a block. A Developer whose legitimate integration is flagged shall contact the Company at support@aapawz.com, identify the Application and its function, and describe the traffic pattern. A flagged integration that rotates infrastructure to avoid the flag commits Circumvention as a separate violation.
9.2 Notice. If the Company determines that the Developer has violated this document, the Company shall give written notice stating the provision violated and the facts relied on, except where notice would compromise an investigation of fraud, a safety risk, or a legal obligation.
9.3 Opportunity to cure. No cure period applies to Scraping, to Circumvention, to distribution of a tool described in clause 3.4, to fraud, or to a violation that by its nature cannot be cured. For any other violation capable of cure, the Developer has ten (10) business days from notice to cure it and to confirm the cure in writing.
9.4 Measures. If a violation is established, the Company may, proportionate to the violation and without a cure period where clause 9.3 so provides: (a) revoke every session and Credential of the Developer; (b) block associated infrastructure; (c) require deletion and certification under clause 6.1; (d) suspend or terminate the Account and bar the entity and its principals from re-registration; (e) terminate this document and the Developer Agreement for the Developer concerned; and (f) exercise any other right or remedy available under this document or at law. Procedure is further governed by the Partner Suspension, Termination and Appeals.
9.5 Appeal. The Developer may appeal a measure under this article by written notice to legal@aapawz.com within thirty (30) days of the measure, stating the grounds and attaching the records relied on. The appeal is decided by a person who did not make the original decision. The Company's decision on appeal is final. A measure remains in effect during an appeal unless the Company directs otherwise in writing.
9.6 No waiver by delay. The Company's delay in acting on a violation is not a waiver of the violation or of any later violation of the same kind.
Article 10: Term and Termination
10.1 Term. This document takes effect on the Effective Date stated in the caption for a Developer that holds developer access, and on first access for any other person, and continues until terminated under this article. Termination does not end the deletion duty in clause 6.1 for data obtained before termination.
10.2 Termination by the Company. The Company may terminate this document as it applies to a Developer on thirty (30) days' written notice for any reason, and immediately on written notice if the Developer materially breaches this document, engages in fraud, or becomes ineligible to participate.
10.3 Termination by the Developer. The Developer may terminate this document as it applies to the Developer on thirty (30) days' written notice to support@aapawz.com, provided the Developer has no investigation outstanding and holds no data obtained in violation of this document.
10.4 Effect of termination. On termination: (a) the permissions in clause 5.3, to the extent held by the Developer, end; (b) obligations that arose before termination survive until satisfied; and (c) the Company shall pay amounts owed, less amounts the Company may set off under this document, within thirty (30) days, except amounts held in connection with an open investigation or dispute.
10.5 Survival. The Definitions, Liability, Indemnification, Enforcement and Appeals (for measures taken before termination), Dispute Resolution, and General Provisions articles survive termination, together with clause 6.1.
Article 11: Dispute Resolution
11.1 Any dispute arising out of or relating to this document, or to the relationship it governs, is governed by the Dispute Resolution Policy, which is incorporated into this document by reference.
Article 12: General Provisions
12.1 Amendments. The Company may amend this document by posting the amended document in the Document Center and giving notice to the Developer at the email address in the Account. An amendment that materially increases the Developer's fees or obligations takes effect thirty (30) days after notice; other amendments take effect on posting. Continued use of the Platform after the effective date of an amendment is acceptance of it. If the Developer does not accept an amendment, the Developer's remedy is to terminate under Article 10 before the amendment takes effect.
12.2 Notices. Legal notices under this document shall be sent to legal@aapawz.com. Operational notices, including a contact under clause 9.1, and all other communications shall be sent to support@aapawz.com. A notice to the Company is effective when the Company acknowledges receipt or, for email, one business day after sending, whichever is earlier. Notices to the Developer are effective when sent to the email address in the Account or posted to the Account's notice facility in the portal, whichever occurs first. The Developer shall keep the email address in the Account current. DMCA notices are given as provided in the DMCA and Copyright Policy, to the designated agent at legal@aapawz.com.
12.3 Governing law. This document is governed by the laws of the State of Tennessee, without regard to its conflict-of-laws rules. Subject to the Dispute Resolution Policy, any proceeding arising out of this document shall be brought in the state or federal courts located in Shelby County, Tennessee, and the parties consent to personal jurisdiction there.
12.4 Severability. If any provision of this document is held unenforceable, the provision shall be enforced to the fullest extent permitted, and the remaining provisions continue in full effect.
12.5 Entire agreement. This document, together with the documents it incorporates by reference, is the entire agreement between the Company and the Developer for the subject it governs and supersedes every prior or contemporaneous statement, communication, or agreement on that subject, whether written or oral.
12.6 Assignment. The Developer shall not assign this document or any right or obligation under it without the Company's prior written consent, and an assignment without consent is void. The Company may assign this document to an affiliate or in connection with a sale of all or part of its business, on notice to the Developer.
12.7 Waiver. A waiver of any provision of this document is effective only in writing and only for the instance stated. No waiver is a waiver of any other provision or instance.
12.8 Interpretation. Headings are for convenience only. "Including" means "including without limitation." This document shall not be construed against a party on the ground that the party prepared it. The English-language text controls over any translation.