This “Spider AF Terms of Service” (including any individual terms and conditions, fee schedule, various policies, manuals, specification rules, FAQs, etc. that we provide for Spider AF, hereinafter referred to as the “Terms of Service”) defines the terms and conditions under which Spider Labs, Inc., a corporation organized under the laws of Japan (hereinafter referred to as “the Company”), provides Spider AF (defined below) to each User (defined below).
By clicking or checking an acceptance mechanism that refers to these Terms of Service, submitting an application form or order form that incorporates these Terms of Service, or accessing or using Spider AF after receiving notice that these Terms of Service apply, the User agrees to be bound by these Terms of Service. Each individual who accepts these Terms of Service on behalf of a User represents that he or she has authority to bind that User.
Please read these Terms of Service carefully before using Spider AF.
“Spider AF” is a generic term for the Anti-Ad Fraud Service (currently marketed as "Ad Fraud Protection"), the Anti-Resale Service (currently marketed as "Scalping Protection"), the Fake Lead Protection Service, the SiteScan Service, and other individual and ancillary services provided by us under the name “Spider AF” (or any successor name). References in the Usage Agreement, application forms and related documents to a service's marketed name refer to the corresponding service defined in this paragraph.
The services included in Spider AF may be added, deleted, or changed at any time at the Company's discretion in accordance with these Terms of Service.
The specific contents and specifications of, and points to be noted regarding, each individual and ancillary service shall be as set forth in the application form, specifications, manuals and other documents prescribed by the Company.
“User“ means a customer who has applied for the use of Spider AF by using the Application Form, the Spider AF purchase screen set up online by the Company or any other Spider AF application method determined by the Company (hereinafter collectively referred to as the ”Application Form").
The term “use” of Spider AF means accessing or using any part of the functions provided in Spider AF including, without limitation, using any part of the functions provided in Spider AF, viewing any information provided in Spider AF, providing information to us regarding Spider AF, or engaging in any other activities related to or through Spider AF. All activities related to or conducted through Spider AF constitute “use”.
The User shall prepare, install and maintain at its own responsibility and expense all infrastructure and facilities, including but not limited to servers, and installation and configuration of application tools, which are required for the use of Spider AF as specified by the Company. The Company shall not be liable for any damages incurred by the User or its customers in the event that the User violates such obligations, and the User hereby agrees to this in advance.
Spider AF is provided to the User on an “as is” and “as available” basis. To the maximum extent permitted by applicable law, the Company disclaims all express, implied, statutory and other warranties, representations, conditions and undertakings, including any implied warranties of merchantability, fitness for a particular purpose, title and non-infringement, and any warranty arising from course of dealing, usage or trade practice. Without limiting the foregoing, the Company does not warrant that Spider AF will be uninterrupted, error-free, secure, or free of harmful code, or that any detection, filtering, classification, integration, conversion, analysis or other result will be complete, accurate, reliable, or suitable for the User’s requirements. Nothing in this Article excludes a warranty or other obligation that cannot lawfully be excluded.
In the event of noncompliance with these Terms of Service, the Company may suffer irreparable damage. Therefore, in addition to monetary compensation and other remedies based on law, the User agrees in advance that the Company shall be entitled to specific performance or injunctive relief as remedy for breach or threatened breach of these Terms of Service without warranty, other security provision or grounds for damage.
Last Updated: November 19, 2026
THIS AGREEMENT IS MADE BETWEEN:
The User under the Usage Agreement, acting as a controller (hereinafter, the "Data Controller"), and
SPIDER LABS, INC., a corporation organized under the laws of Japan, with its principal office at Minamiaoyama ST Bldg. 4F, 7-10-3 Minamiaoyama, Minato-ku, Tokyo 107-0062, Japan, (hereinafter the "Data Processor") each a "party" and together the "parties".
The Parties hereby agree as follows:
In this Agreement:
The Data Processor and all its employees undertake to:
Data Processor is generally authorized to engage the Sub-processors identified in Schedule 2 and any replacement or additional Sub-processors appointed in accordance with this Section. Data Processor will maintain a current list identifying each Sub-processor, its processing function, relevant processing location and, where applicable, transfer mechanism. Data Processor will give Data Controller at least thirty (30) calendar days’ prior written notice before authorizing a new Sub-processor to process Personal Data. Where a replacement or additional Sub-processor is reasonably necessary to address an urgent security, availability or legal issue, Data Processor may engage it before expiration of the thirty (30) day notice period, provided that Data Processor gives Data Controller as much prior notice as reasonably practicable before the Sub-processor begins processing Personal Data. The remainder of the thirty (30) day objection period will continue to run from the date of that notice. Data Controller may object during that period only on reasonable data-protection grounds. The parties will work in good faith to resolve the objection. If they cannot resolve it, Data Processor may elect to use a commercially reasonable alternative, modify the affected processing, or permit Data Controller to terminate the affected Service without penalty. Data Processor will enter into a written agreement with each Sub-processor imposing data-protection obligations no less protective in substance than those applicable to Data Processor under this Agreement, and Data Processor remains responsible for the Sub-processor’s performance to the extent required by applicable law.
Sub-processor(s) will be considered a Data Processor for the purposes of this Agreement and equally obliged to comply with the obligations of Data Processor as set forth in this Agreement, as well as any instructions issued by the Data Controller as to the Processing of Personal Data.
Data Processor shall notify Data Controller without undue delay after becoming aware of a Personal Data breach affecting Personal Data processed under this Agreement and via the contact method designated by the Data Controller, together with all relevant information reasonably available to the Data Processor to document and report the incident.
The Data Processor shall not delay or withhold notification based on its assessment of whether the breach is likely to result in a risk to Data Subjects.
The following minimum information shall be provided, if available:
If information cannot be provided simultaneously, and to the extent that it is not, the information will be gradually provided without undue delay.
The Data Controller is responsible for determining whether notice to a supervisory authority, Data Subject, customer or other person is legally required, except to the extent the Data Processor has an independent notification obligation under applicable law.
Data Processor will not notify a supervisory authority or Data Subjects of a Personal Data breach affecting Data Controller’s Personal Data on Data Controller’s behalf unless Data Controller so requests in writing or Data Processor is independently required to do so by applicable law, in which case Data Processor will, where legally permitted, inform Data Controller before making the notification.
Upon expiry or termination of a Service, or if the Processing of Personal Data is no longer required for the purposes of the Services, Data Processor will, at Data Controller’s choice, securely delete or return the Personal Data and delete existing copies, in accordance with the retention periods set out in Schedule 1, except to the extent applicable law requires storage or the Personal Data is processed by Data Processor as an independent controller as described in Schedule 1. Data Controller may retrieve Personal Data through the export functions of the Service during the term of the Service; if Data Controller requests return of Personal Data, Data Processor will make it available in a commonly used electronic format to the extent reasonably practicable. Data Processor will confirm deletion in writing on request.
The Data Controller represents and warrants that they will:
Data Controller’s remedies, including those of its Affiliates, arising from any breach by Data Processor of the terms of this agreement will be subject to any aggregate limitation of liability already existing between the parties, as permitted by law.
This Agreement shall be governed by and construed in accordance with the laws of Japan, without regard to conflict-of-laws principles, and the Tokyo District Court shall have exclusive jurisdiction in the first instance over any dispute arising out of or relating to this Agreement. Nothing in this Section limits a Party’s right to seek temporary or injunctive relief in any court of competent jurisdiction.
Clauses and other headings in this Agreement are for convenience of reference only and shall not constitute a part of or otherwise affect the meaning or interpretation of this Agreement. Schedules to this Agreement shall form an integral part thereof.
Unless the context otherwise requires, in the Agreement:
This Agreement, including the Schedules attached hereto and any subsequent properly executed Processing Appendices agreed between the parties, constitutes the entire agreement between the parties pertaining to the subject matter hereof and supersedes all prior agreements, understandings, negotiations and discussions of the parties.
The provisions of this Agreement are severable. If any phrase, clause or provision is invalid or unenforceable in whole or in part, such invalidity or unenforceability shall affect only such phrase, clause or provision, and the rest of this Agreement shall remain in full force and effect.
Any notice or other communication contemplated by this Agreement shall be given in writing in accordance with Article 2 of the Terms of Service. Notices from the Data Controller to the Data Processor under this Agreement may be sent by email to dpo@spideraf.com or to such other address as the Data Processor may notify.
This Addendum forms part of the Usage Agreement between the User and Spider Labs, Inc., a corporation organized under the laws of Japan. In this Addendum, “Spider Labs” means Spider Labs, Inc.
This Appendix, including any relevant attachment, describes the types of Personal Data, and the purposes for which that Personal Data may be processed by the Data Processor.
The Data Controller is: the User under the Usage Agreement.
The Data Processor is: Spider Labs, Inc., a corporation organized under the laws of Japan, with its principal office at Minamiaoyama ST Bldg. 4F, 7-10-3 Minamiaoyama, Minato-ku, Tokyo 107-0062, Japan.
Special categories of data: The Services are not intended to process special categories of Personal Data within the meaning of Article 9 of the GDPR or Personal Data relating to criminal convictions and offences within the meaning of Article 10 of the GDPR. The Data Controller shall not intentionally provide such data unless expressly agreed in writing and subject to appropriate safeguards. The Data Processor does not represent that incidental special-category data can never appear in content submitted by or collected on behalf of the Data Controller.
| Service / activity | Nature and purpose | Personal data | Data subjects | Frequency, duration and location |
|---|---|---|---|---|
| Anti-Ad Fraud | Collect, transmit, host, analyze and score traffic and interaction data to detect invalid traffic, fraud, abuse and security events, produce reports, and support customer-directed exclusions. | IP address, user agent, device and browser data, advertising or device identifiers where enabled, browser-storage identifiers, including identifiers stored in localStorage or comparable technologies, session and request identifiers, URLs and referrers, timestamps, clickstream and interaction data, fraud signals, and customer configuration data. | Visitors and users of customer websites, applications, advertisements and digital properties. | Continuous or event-driven during the Usage Agreement. Personal data in operational and reporting databases is generally retained for 90 days. Copies maintained in backups may be retained for up to approximately six months before deletion or overwriting in accordance with Spider Labs’ backup cycles. These periods do not include raw event data processed by Spider Labs as an independent controller and retained in restricted archival storage as described in Spider Labs’ Privacy Policy. Processing locations and subprocessors are in Schedule 2. |
| Anti-Resale | Analyze transaction and order information to identify suspected fraudulent or unauthorized resale and provide alerts, reports and related service features. | Order and transaction identifiers, purchaser name, postal and delivery address, contact details, product and order details, payment or fulfillment status, device and network data, and fraud indicators. Spider Labs should not receive full payment-card data unless expressly agreed. | Purchasers, recipients, account holders, customer personnel and suspected resellers. | Event-driven during the Usage Agreement. Retained according to documented retention settings and Spider Labs’ retention schedule, then deleted or de-identified. General and APAC data is processed primarily in Japan. If the Service is expanded to the EEA, EEA data will be processed through the separate Frankfurt deployment and EU-region infrastructure described in Schedule 2. |
| Fake Lead Protection | Analyze lead-submission and interaction data to identify automated, fraudulent, duplicate or otherwise invalid leads. | Structured lead-submission fields, including name, email address, telephone number and postal address, together with IP address, device and browser data, timestamps, URLs, referrers, interaction data and fraud indicators. Free-text form content is not collected. | Website visitors, prospective customers, lead submitters and customer personnel. | Continuous or event-driven during the Usage Agreement. Personal data in operational and reporting databases is generally retained for 90 days. Copies maintained in backups may be retained for up to approximately six months before deletion or overwriting in accordance with Spider Labs’ backup cycles. These periods do not include raw event data processed by Spider Labs as an independent controller and retained in restricted archival storage as described in Spider Labs’ Privacy Policy. Except for deriving the non-identifying characteristics described in Article 10, Paragraph 5 of the Terms of Service, structured lead-submission fields that are maintained in the same archival environment remain processed solely on behalf of the User, are stored separately from technical signals, are used only to provide the Fake Lead Protection Service to the User (including the detection of duplicate or repeat submissions), are not used for the independent-controller purposes described in Spider Labs’ Privacy Policy, and are deleted separately at the User’s direction or upon termination in accordance with Annex I. The independent-controller archival retention periods described in Spider Labs’ Privacy Policy do not apply to those structured lead-submission fields. Processing locations and subprocessors are in Schedule 2. |
| SiteScan | Scan customer-designated websites and related resources to detect tags, scripts, configurations, security issues, policy issues or other conditions described in the applicable specifications. | URLs, domain and server information, HTML and script content, headers, network and device information, scan results and customer configuration data. Incidental personal data may appear in scanned content. | Website visitors, customer personnel and individuals whose information appears incidentally in scanned content. | Periodic or customer-initiated during the Usage Agreement. Retained according to documented retention settings and Spider Labs’ retention schedule, then deleted or de-identified. General and APAC data is processed primarily in Japan. EEA data is processed through the separate Frankfurt deployment and EU-region infrastructure described in Schedule 2, where applicable. |
| Account, support and billing processing performed on behalf of the customer, if applicable | Provision, administration and support of the services and customer-directed user accounts. | Business contact details, account identifiers, authentication data, support communications and billing-related information. | Customer personnel, authorized users and customer contacts. | Account and customer-contact information is retained for the duration of the customer relationship and thereafter until deletion is requested, subject to retention reasonably necessary for legal, tax, accounting, security, fraud-prevention and dispute-resolution purposes. System and infrastructure logs are retained for between 30 days and two years depending on the type of log and its purpose: operational server and application logs are rotated on shorter cycles, while security, integration and diagnostic logs may be retained for up to two years for security monitoring, troubleshooting and compliance purposes, subject to access restrictions. Administrative and audit-trail records are retained for as long as reasonably necessary for security, compliance and the establishment, exercise or defense of legal claims, subject to periodic review under Spider Labs’ retention schedule. This processing is performed primarily in Japan, subject to access by authorized subprocessors and personnel identified in Schedule 2. |
| Security, administration and audit trails | Maintain records of administrative actions, account changes, access, security events and material system activity for security monitoring, incident investigation, compliance, accountability and the establishment, exercise or defense of legal claims. | User and administrator identifiers, account and access information, timestamps, IP addresses, actions taken, configuration changes, security-event information and related audit metadata. | Customer personnel, authorized users, administrators and other individuals whose actions are recorded in the audit trail. | Collected when relevant administrative, account, access or security events occur. Administrative and audit-trail records are retained for as long as reasonably necessary for security, compliance and the establishment, exercise or defense of legal claims, subject to periodic review under Spider Labs’ retention schedule. Processing occurs in the applicable Japan or EEA service environment described in Schedule 2. |
Controller and independent-controller processing. This Schedule applies only when Spider Labs processes personal data on documented instructions from the customer. Processing for which Spider Labs independently determines the purposes and essential means, including the creation, maintenance and operation of shared fraud-intelligence databases, the provision of database-derived results and fraud-related identifiers to users or other authorized recipients, and any permitted cross-customer fraud intelligence or service-improvement processing, is outside this DPA and is governed by the Terms of Service, Spider Labs’ Privacy Policy and applicable law. For clarity, Spider Labs processes raw event data retained in restricted archival storage for fraud-model development, model back testing, cross-customer fraud intelligence, or security investigations as an independent controller where Spider Labs determines the purposes and essential means of that processing. Such independent-controller archival processing is not subject to this Schedule.
This Appendix forms part of, and is subject to, the Data Protection Agreement set out in Annex I, and takes effect as of the effective date of the Usage Agreement between the User and the Company.
Spider Labs operates a dual-region architecture. General and APAC data is processed primarily in Japan. EEA tracker data is primarily processed through a separate deployment in Frankfurt, Germany, and stored in EU-region infrastructure. The locations below identify the principal processing locations for each subprocessor.
| NAME OF SUB-PROCESSOR | REGISTERED BUSINESS ADDRESS | SERVICES AND PROCESSING FUNCTION | ACTUAL LOCATION OF THE PROCESSING |
|---|---|---|---|
| Amazon Web Services Japan G.K. | Tokyo, Japan (an affiliate of Amazon Web Services, Inc., 410 Terry Avenue North, Seattle, Washington 98109, United States) | Application hosting and infrastructure, including application servers, Amazon S3, Amazon RDS for PostgreSQL, self-hosted ClickHouse, Amazon CloudWatch, Amazon Route 53 for DNS, and Amazon CloudFront for static assets only. | Tokyo, Japan, ap-northeast-1, for general and APAC processing, and Frankfurt, Germany, eu-central-1, for EEA processing. Route 53 and CloudFront may involve globally distributed infrastructure for DNS and static-content delivery, subject to applicable transfer safeguards. |
| Google Cloud Japan G.K. | Tokyo, Japan (an affiliate of Google LLC) | Cloud Storage and BigQuery, including a separate EU dataset for EEA tracker data. | Japan, including asia-northeast1, for general and APAC processing, and the European Union for EEA tracker data. |
| Akamai Technologies International AG, providing Linode services | Zug, Switzerland (an affiliate of Akamai Technologies, Inc., 145 Broadway, Cambridge, Massachusetts 02142, United States) | Linode compute infrastructure used for the multi-node tracker-ingestion cluster. The cluster receives raw tracker traffic and forwards it to Google Cloud Storage. It is not used for persistent storage. | Tokyo, Japan; Frankfurt, Germany; Fremont, California, United States; and Singapore, corresponding to the regions actually configured in the Linode account. EEA tracker traffic is ingested through the Frankfurt region. All regions are ingestion-only, without persistent storage. |
| Functional Software, Inc., doing business as Sentry | 45 Fremont Street, 8th Floor, San Francisco, California 94105, United States | Error monitoring, diagnostics and troubleshooting. Sentry may receive end-user IP addresses, request content and related technical information. Spider Labs has enabled Sentry’s standard data-scrubbing controls to remove passwords, payment-card patterns and similar sensitive fields before storage. End-user IP addresses and request content may be retained for up to 90 days. | The United States and any other locations disclosed by Sentry for the applicable service configuration, subject to applicable transfer safeguards. |
| SPIDER LABS PORTUGAL, UNIPESSOAL LDA (an affiliate of Spider Labs, Inc.) | Avenida Duque de Loulé 22, 7.º, 1050-090 Lisboa, Portugal | EU representative services, customer support, engineering and service operations involving access to customer personal data | Lisbon, Portugal |
| Intercom R&D Unlimited Company | 124 St Stephen’s Green, Dublin 2, D02 N960, Ireland | Customer support messaging and help-center platform, including AI-assisted support responses. Intercom may receive customer personnel names, email addresses, account identifiers, support conversation content and related technical information. | United States, subject to applicable transfer safeguards. |
| Anthropic, PBC | 548 Market Street, PMB 90375, San Francisco, California 94104, United States | AI assistant (Claude, Team plan) used by Spider Labs staff for drafting, analysis and support work. Claude may receive customer personnel names, email addresses, support conversation content and related business information that staff include in prompts, subject to Spider Labs' AI use policy. Under Anthropic's commercial terms, inputs and outputs are not used to train Anthropic's models. | United States, subject to applicable transfer safeguards. |
| OpenAI OpCo, LLC | 1455 3rd Street, San Francisco, California 94158, United States | AI assistant (ChatGPT, Business plan) used by Spider Labs staff for drafting, analysis and support work. ChatGPT may receive customer personnel names, email addresses, support conversation content and related business information that staff include in prompts, subject to Spider Labs' AI use policy. Under OpenAI's business terms, inputs and outputs are not used to train OpenAI's models. | United States, subject to applicable transfer safeguards. |
| Google Asia Pacific Pte. Ltd. | 70 Pasir Panjang Road, #03-71, Mapletree Business City, Singapore 117371 | Google Workspace (Enterprise Standard), including Gemini, used by Spider Labs staff for email, documents and AI-assisted drafting and analysis. Workspace may receive customer personnel names, email addresses, support conversation content and related business information that staff store in Workspace or include in prompts, subject to Spider Labs' AI use policy. Under the Google Workspace terms, customer data is not used to train Google's generative AI models. | Google data centers globally, including the United States, subject to applicable transfer safeguards. |