Last updated: May 26, 2026
Effective: May 26, 2026
This Data Processing Addendum (“DPA”) forms part of the Zapstra Terms of Service, any applicable order form, statement of work, Shopify app installation, subscription, service agreement, or other written agreement governing Customer’s use of Zapstra Services (collectively, the “Agreement”).
This DPA applies when Zapstra LLC (“Zapstra,” “we,” “us,” or “our”) Processes Customer Personal Data on behalf of a customer, merchant, business, or organization (“Customer,” “you,” or “your”) in connection with the Services.
By using the Services, installing a Zapstra app, approving Shopify app permissions, accepting an Order Form, or otherwise agreeing to the Agreement, Customer agrees to this DPA.
This DPA applies only to Zapstra’s Processing of Customer Personal Data on behalf of Customer in connection with the Services.
This DPA supplements the Agreement. If there is a conflict between this DPA and the Agreement regarding Processing of Customer Personal Data, this DPA controls only for that conflict. If there is a conflict between this DPA and the Standard Contractual Clauses, the Standard Contractual Clauses control for the applicable restricted transfer.
Except as expressly modified by this DPA, the Agreement remains in full force and effect.
This DPA does not apply to information that Zapstra Processes as an independent controller or business for its own purposes, including account administration, billing, business operations, security monitoring, legal compliance, fraud prevention, analytics, marketing, product administration, or communications, except where Applicable Data Protection Laws require otherwise. Zapstra’s Processing of such information is described in Zapstra’s Privacy Policy.
For purposes of this DPA:
“Agreement” means the Zapstra Terms of Service, any applicable Order Form, statement of work, Shopify app installation, subscription, service agreement, beta terms, design partner terms, or other written agreement governing use of the Services.
“Applicable Data Protection Laws” means all privacy, data protection, data security, breach notification, consumer privacy, and similar laws applicable to Zapstra’s Processing of Customer Personal Data under the Agreement, including where applicable the GDPR, UK GDPR, Swiss FADP, CCPA, and other U.S. State Privacy Laws.
“CCPA” means the California Consumer Privacy Act, as amended by the California Privacy Rights Act, and its implementing regulations.
“Controller,” “Processor,” “Data Subject,” “Personal Data,” “Personal Data Breach,” “Process,” “Processing,” and “Supervisory Authority” have the meanings given to them under the GDPR or other Applicable Data Protection Laws.
“Customer Data” means data, content, files, records, Shopify store data, product data, inventory data, order data, fulfillment data, supplier data, customer data, support data, logs, screenshots, exports, or other information submitted to, uploaded to, transmitted through, or made available to Zapstra by or on behalf of Customer.
“Customer Personal Data” means Customer Data that constitutes Personal Data and that Zapstra Processes on behalf of Customer as a Processor, service provider, contractor, or similar role under Applicable Data Protection Laws.
“Customer Organization” means the Zapstra organization, workspace, account, billing account, or administrative grouping under which Customer may operate one or more Shops, users, apps, modules, or Services.
“De-Identified Data” means data that does not identify and cannot reasonably be used to identify Customer, a Shop, a Data Subject, household, device, or individual, taking into account reasonably available means.
“Documented Instructions” means Customer’s instructions to Zapstra for Processing Customer Personal Data, including the Agreement, this DPA, Order Forms, app configurations, Shopify permissions, API calls, support requests, product settings, written instructions from authorized users, and Customer’s use of the Services.
“GDPR” means Regulation (EU) 2016/679.
“Order Form” means any online checkout, Shopify billing approval, invoice, quote, statement of work, subscription selection, email confirmation, or other written agreement identifying paid Services, scope, fees, or commercial terms.
“Restricted Transfer” means a transfer of Personal Data from the European Economic Area, United Kingdom, or Switzerland to a country or recipient that does not provide an adequate level of protection under Applicable Data Protection Laws.
“Security Incident” means a breach of Zapstra’s security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data Processed by Zapstra. Security Incident does not include unsuccessful attempts or activities that do not compromise Customer Personal Data, such as unsuccessful login attempts, pings, port scans, denial-of-service attacks, or similar events.
“Services” means Zapstra’s websites, software, Shopify apps, APIs, integrations, automations, beta products, early-access products, support, consulting, custom-development services, design partner programs, documentation, and related offerings.
“Shop” means a Shopify store, Shopify shop, storefront, merchant account, or other store-level account connected to or Processed through the Services.
“Standard Contractual Clauses” or “SCCs” means the standard contractual clauses adopted by the European Commission under Commission Implementing Decision (EU) 2021/914, as updated, amended, replaced, or superseded from time to time.
“Subprocessor” means a third party engaged by Zapstra to Process Customer Personal Data on behalf of Customer in connection with the Services.
“UK Addendum” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner’s Office, as updated, amended, replaced, or superseded from time to time.
“UK GDPR” means the GDPR as incorporated into the laws of the United Kingdom.
“U.S. State Privacy Laws” means U.S. state privacy laws applicable to Processing under this DPA, including where applicable the CCPA, Colorado Privacy Act, Connecticut Data Privacy Act, Virginia Consumer Data Protection Act, Utah Consumer Privacy Act, Texas Data Privacy and Security Act, Oregon Consumer Privacy Act, and similar state consumer privacy laws.
For Customer Personal Data Processed by Zapstra on behalf of Customer, Customer is the Controller, business, or equivalent entity under Applicable Data Protection Laws, and Zapstra is the Processor, service provider, contractor, or equivalent entity.
If Customer is itself acting as a Processor on behalf of a third-party Controller, Customer represents and warrants that Customer has authority to appoint Zapstra as a Subprocessor and to provide Documented Instructions to Zapstra.
Customer is responsible for:
Zapstra will Process Customer Personal Data only as described in this DPA, the Agreement, and Customer’s Documented Instructions, unless required otherwise by applicable law. If Zapstra is required by law to Process Customer Personal Data other than according to Customer’s Documented Instructions, Zapstra will inform Customer before such Processing unless legally prohibited from doing so.
The subject matter, duration, nature, purpose, categories of Personal Data, and categories of Data Subjects are described in Schedule 1 — Details of Processing.
Customer acknowledges that the specific categories of Customer Personal Data Processed by Zapstra depend on:
Customer instructs Zapstra to Process Customer Personal Data as necessary to:
Zapstra may refuse or suspend Processing instructions that Zapstra reasonably believes violate applicable law, third-party platform requirements, security obligations, or the Agreement.
Zapstra will ensure that personnel authorized to Process Customer Personal Data are subject to confidentiality obligations or are otherwise bound by professional or contractual obligations of confidentiality.
Zapstra will limit access to Customer Personal Data to personnel and Subprocessors who need access for purposes authorized by this DPA and the Agreement.
Zapstra will maintain reasonable technical and organizational measures designed to protect Customer Personal Data from unauthorized access, disclosure, alteration, and destruction, as further described in Schedule 2 — Technical and Organizational Security Measures.
Customer acknowledges that security measures may evolve over time. Zapstra may update or modify its security measures provided that such updates or modifications do not materially reduce the overall level of protection for Customer Personal Data.
Customer is responsible for securing its own accounts, devices, Shopify permissions, third-party integrations, API keys, credentials, exports, local copies of data, and user access.
Customer provides general authorization for Zapstra to engage Subprocessors to Process Customer Personal Data in connection with the Services.
Zapstra’s current Subprocessors and relevant customer-directed platforms are listed in Schedule 3 — Subprocessors and Third-Party Processing.
Zapstra will enter into written agreements with Subprocessors that impose data protection obligations materially similar to those imposed on Zapstra under this DPA, to the extent applicable to the nature of the services provided by the Subprocessor.
Zapstra remains responsible for Subprocessors’ performance of their data protection obligations to the extent required by Applicable Data Protection Laws.
Zapstra may add, replace, or remove Subprocessors from time to time. Where reasonably practicable, Zapstra will provide at least 30 days’ advance notice before authorizing a new Subprocessor to Process Customer Personal Data, either by email, account notice, in-app notice, website notice, subprocessor page, or other reasonable method.
If urgent replacement or addition of a Subprocessor is necessary for security, availability, compliance, continuity, legal, platform, or operational reasons, Zapstra may provide notice as soon as reasonably practicable.
Customer may object to a new Subprocessor on reasonable data protection grounds by providing written notice within 15 days after Zapstra’s notice. The objection must explain the specific data protection concern. Zapstra will use commercially reasonable efforts to address the concern.
If Zapstra cannot reasonably address Customer’s objection, Customer may terminate only the affected Services, subject to the Agreement. Customer is not entitled to a refund, credit, or penalty waiver unless expressly required by the Agreement or applicable law.
The Services may connect with Shopify or other third-party platforms selected, authorized, or used by Customer.
Customer acknowledges that Shopify and other Customer-directed platforms may process Customer Personal Data under their own terms, policies, and agreements with Customer. Such platforms are not Subprocessors of Zapstra solely because Customer connects them to the Services, unless Zapstra separately engages them to Process Customer Personal Data on Zapstra’s behalf.
Zapstra is not responsible for third-party platforms’ privacy, security, availability, processing, policies, API changes, platform requirements, or acts or omissions.
Zapstra will, taking into account the nature of the Processing and to the extent Customer cannot reasonably fulfill the request without Zapstra’s assistance, provide reasonable assistance to Customer in responding to requests from Data Subjects to exercise rights under Applicable Data Protection Laws.
If Zapstra receives a Data Subject request relating to Customer Personal Data, Zapstra may refer the request to Customer unless Zapstra is legally required to respond directly.
Customer is responsible for verifying the identity and authority of the requester and for determining whether and how to respond to a Data Subject request.
Zapstra may charge reasonable fees for assistance with Data Subject requests that are excessive, repetitive, technically complex, outside standard functionality, or not required by Applicable Data Protection Laws.
Where required for Shopify apps, Zapstra may receive and respond to Shopify privacy and compliance webhooks, including customers/data_request, customers/redact, and shop/redact.
Customer acknowledges that Zapstra’s data model may support multiple Services, apps, modules, and Shops under a shared Customer Organization.
Zapstra will treat Shopify shop/redact requests as Shop-scoped redaction instructions unless applicable law, Shopify requirements, Customer’s written instructions, or the Agreement require broader deletion.
Customer Data for a Shop will be deleted, redacted, or de-identified within 30 days after Zapstra receives Shopify’s valid shop/redact webhook for that Shop, except to the extent retention is permitted or required under this DPA, the Agreement, applicable law, security obligations, audit obligations, backup practices, fraud-prevention obligations, dispute-resolution needs, or compliance requirements.
Where Customer operates multiple Shops under a single Customer Organization, deletion or redaction will be performed per Shop. A redaction request for one Shop does not require Zapstra to delete, redact, or disable Customer Data for other active Shops, apps, modules, Services, or Customer Organization records unless required by applicable law or Customer’s valid written instruction.
Zapstra may delete or de-identify Customer Organization-level records when there are no remaining active Shops, apps, modules, Services, billing obligations, legal retention requirements, security retention requirements, support obligations, or other legitimate retention needs associated with that Customer Organization.
Upon termination of the Agreement, expiration of the applicable Services, valid written deletion request, or receipt of a valid platform deletion instruction, Zapstra will delete, redact, return, or de-identify Customer Personal Data in accordance with this DPA, the Agreement, Customer’s Documented Instructions, and applicable law.
Unless otherwise required by applicable law or the Agreement, Zapstra will delete or de-identify Customer Personal Data within 30 days after the applicable deletion trigger, subject to the retention exceptions in this Section.
Zapstra may retain Customer Personal Data to the extent necessary for:
Backup, audit, and security copies may be retained for up to 90 days, or longer where required by law, legal hold, security investigation, dispute, or compliance obligation, and will be deleted or overwritten in the ordinary course.
Zapstra may retain Aggregated Data and De-Identified Data indefinitely.
Zapstra will notify Customer without undue delay and, where feasible, within 72 hours after confirming a Personal Data Breach affecting Customer Personal Data.
Zapstra’s notice will include information reasonably available to Zapstra, which may include:
Zapstra may provide information in phases as it becomes available.
Zapstra’s notice of or response to a Security Incident is not an admission of fault, liability, or violation of law.
Customer is responsible for determining whether a Security Incident requires notification to Data Subjects, Supervisory Authorities, regulators, customers, merchants, Shopify, or other third parties, except where Zapstra has a direct legal obligation.
Taking into account the nature of Processing and the information available to Zapstra, Zapstra will provide reasonable assistance to Customer, to the extent required by Applicable Data Protection Laws and where Customer cannot reasonably fulfill the obligation without Zapstra’s assistance, with:
Zapstra may charge reasonable fees for assistance that is excessive, repetitive, outside standard functionality, requires custom engineering, requires legal analysis specific to Customer, or is not required by Applicable Data Protection Laws.
Zapstra will make available information reasonably necessary to demonstrate compliance with this DPA, subject to confidentiality, security, and operational restrictions.
Zapstra may satisfy audit obligations by providing documentation, written responses, security summaries, subprocessor information, compliance questionnaires, policies, technical descriptions, or third-party reports if available.
Customer may request such information no more than once per calendar year unless a Security Incident affecting Customer Personal Data or a legally binding request requires additional review.
Onsite audits, penetration tests, source code reviews, vulnerability scans, infrastructure access, employee interviews, or inspections of Zapstra systems are not permitted unless legally required or separately agreed in writing.
If an onsite audit is legally required or separately agreed:
Customer authorizes Zapstra and its Subprocessors to Process Customer Personal Data in the United States and other countries where Zapstra or its Subprocessors operate, subject to this DPA and Applicable Data Protection Laws.
For Restricted Transfers from the European Economic Area, United Kingdom, or Switzerland, the terms in Schedule 4 — International Data Transfers apply.
Where the Standard Contractual Clauses apply, the parties agree that:
For Customer Personal Data subject to U.S. State Privacy Laws, the terms in Schedule 5 — U.S. State Privacy Addendum apply.
Without limiting Schedule 5, Zapstra will not sell or share Customer Personal Data, retain, use, or disclose Customer Personal Data outside the business purposes described in the Agreement and this DPA, or combine Customer Personal Data with personal information from other sources except as permitted by Applicable Data Protection Laws.
Customer acknowledges that Zapstra may use AI-assisted tools and AI-related Subprocessors to provide, support, troubleshoot, analyze, parse, summarize, develop, test, secure, or improve the Services.
Zapstra will not intentionally use Customer Personal Data to train general-purpose AI models unless Customer has provided separate authorization or Zapstra has provided additional notice where required by Applicable Data Protection Laws.
Zapstra will use reasonable measures to limit Customer Personal Data submitted to AI-assisted tools to what is reasonably necessary for the applicable Service, support request, document parsing, troubleshooting activity, product function, or Customer instruction.
Customer should not submit unnecessary sensitive personal information, payment card numbers, health information, government identifiers, authentication credentials, or other unnecessary confidential information through support channels, prompts, uploads, forms, documents, or integrations.
AI-assisted Subprocessors that Process Customer Personal Data are listed in Schedule 3 where applicable.
Customer agrees not to submit sensitive personal data, special categories of personal data, protected health information, government identifiers, full payment card numbers, authentication credentials, children’s data, biometric data, or other highly sensitive information to the Services unless:
Zapstra does not intentionally store full payment card numbers. Payment card processing, where applicable, is handled by third-party payment processors.
Zapstra may create, use, retain, disclose, and commercialize Aggregated Data and De-Identified Data for analytics, benchmarking, product development, operations, security, research, reporting, and business purposes.
Zapstra will not attempt to re-identify De-Identified Data except as permitted by Applicable Data Protection Laws, including for testing whether de-identification measures are effective.
Customer represents and warrants that:
Each party’s liability arising out of or relating to this DPA is subject to the exclusions and limitations of liability in the Agreement.
This DPA does not create any separate or additional liability cap, indemnity, warranty, representation, remedy, or cause of action except as expressly stated.
Nothing in this DPA limits liability to the extent such limitation is prohibited by Applicable Data Protection Laws.
This DPA remains in effect for as long as Zapstra Processes Customer Personal Data on behalf of Customer.
Sections that by their nature should survive termination will survive, including provisions relating to deletion, confidentiality, security, audits, international transfers, liability, and U.S. State Privacy Laws.
Zapstra may update this DPA from time to time.
If Zapstra makes material changes, Zapstra may provide notice by posting the updated DPA, emailing Customer, providing in-app notice, updating a legal page, or using another reasonable method.
Continued use of the Services after the effective date of an updated DPA constitutes acceptance of the updated DPA, except where Applicable Data Protection Laws require a different process.
Questions about this DPA may be sent to:
Zapstra Processes Customer Personal Data to provide the Services, including Shopify apps, ecommerce operations software, inventory tools, purchasing tools, supplier workflows, purchase order tools, product and catalog workflows, APIs, webhooks, automations, analytics, support, custom services, beta products, early-access products, and design partner programs.
Zapstra Processes Customer Personal Data for the duration of the Agreement and for any additional period permitted or required by this DPA, the Agreement, applicable law, Shopify platform requirements, backup retention, security obligations, fraud-prevention needs, audit obligations, dispute-resolution needs, or compliance obligations.
Processing may include collection, receipt, access, hosting, storage, retrieval, organization, structuring, consultation, analysis, parsing, transformation, transmission, synchronization, disclosure to Subprocessors, restriction, redaction, deletion, de-identification, aggregation, and other Processing necessary to provide the Services.
Zapstra Processes Customer Personal Data for purposes including:
Depending on the Services used, Customer Personal Data may relate to:
Depending on the Services used, Customer Personal Data may include:
The Services are not designed to intentionally Process sensitive personal data, special categories of personal data, protected health information, biometric data, government identifiers, full payment card numbers, or children’s data unless expressly agreed or necessary for a specific Service.
Customer should not submit such data unless permitted by the Agreement and Applicable Data Protection Laws.
Processing may occur continuously, periodically, on demand, in real time, or as triggered by Customer’s use of the Services, Shopify webhooks, API calls, scheduled jobs, support requests, integrations, or Customer instructions.
Customer Personal Data is retained as described in the Agreement, this DPA, the Privacy Policy, and Customer’s settings.
Shop-scoped deletion and redaction are handled as described in Section 11 of this DPA and Schedule 6.
Backup, audit, security, fraud-prevention, compliance, and legal records may be retained as described in Section 12.
Aggregated Data and De-Identified Data may be retained indefinitely.
Zapstra maintains reasonable technical and organizational measures designed to protect Customer Personal Data. Measures may include the controls listed below, as applicable to the Services, infrastructure, data type, and risk.
Zapstra does not represent that it currently maintains SOC 2 certification, ISO 27001 certification, a 24/7 monitored security operations center, a formal recurring penetration-testing program, fixed RPO/RTO commitments, or enterprise-level disaster recovery unless separately stated in writing.
Zapstra may use the following Subprocessors and customer-directed platforms to provide, support, secure, analyze, or improve the Services.
This schedule is intended to be broad enough to cover current and future Zapstra Services using the same categories of infrastructure and subprocessors.
| Provider | Purpose | Data Processed | Location / Region |
|---|---|---|---|
| Google Cloud Platform | Application hosting, eventing, storage, build/deployment, tasks, secrets, KMS, monitoring, logging, infrastructure | Customer Data and Customer Personal Data as needed to provide the Services | U.S., EU, Australia, and other configured regions |
| Google Firestore | Operational database and canonical data store | Customer Data and Customer Personal Data | U.S., EU, Australia, and other configured regions |
| Google BigQuery | Analytics, canonical event logs, operational analytics, reporting, diagnostics | Customer Data and Customer Personal Data, depending on Service configuration | U.S., EU, Australia, and other configured regions |
| Google Firebase | Authentication, hosting, functions, website and app infrastructure | Account credentials, authentication data, website telemetry, app data | Primarily U.S. or configured Google regions |
| Google Cloud Document AI | Purchase order and document parsing | Uploaded documents, supplier information, PO details, line items, prices, and related document content | U.S. or configured Google regions |
| Google Cloud Vision API | OCR fallback and image/document analysis | Uploaded documents, images, supplier information, PO details, line items, and related document content | U.S. or configured Google regions |
| OpenAI | AI-assisted document parsing, support-ticket analysis, workflow assistance, product copy assistance where enabled, and other AI-assisted Service functionality | Supplier PO documents, support ticket text, shop/order metadata, product copy, and other Customer-submitted content as needed for the applicable Service | U.S. or regions made available by provider |
| Stripe | Payment processing, billing, checkout, subscription, invoice, and payment-related services | Billing contact information, payer information, payment metadata; Zapstra does not intentionally store full payment card numbers | U.S. and other Stripe processing locations |
| SendGrid / Twilio SendGrid | Transactional email, service email, support email, marketing email where enabled | Merchant email addresses, support correspondence, transactional email metadata | U.S. and other provider locations |
| Shippo | Carrier tracking lookups and shipping-related functionality | Tracking numbers, carrier metadata, shipping metadata | U.S. and other provider locations |
| Frankfurter / ECB-backed FX service | Foreign exchange rate lookups | Generally no Customer Personal Data; public FX rate requests | EU |
| Shopify | Customer-directed source platform, Admin API, webhooks, billing, app permissions, app installation, order/product/customer/inventory/fulfillment data flows | Shopify store, merchant, customer, order, product, inventory, fulfillment, billing, and app data depending on approved scopes and Customer configuration | Shopify-controlled locations |
For Restricted Transfers of Customer Personal Data from the European Economic Area to Zapstra in a country that does not provide an adequate level of protection under Applicable Data Protection Laws, the Standard Contractual Clauses are incorporated by reference and apply as follows:
For Restricted Transfers of Customer Personal Data from the United Kingdom, the UK Addendum is incorporated by reference and applies to the Standard Contractual Clauses as modified by this Schedule.
The parties agree that:
For Restricted Transfers of Customer Personal Data from Switzerland, the Standard Contractual Clauses apply with the following modifications:
Zapstra will implement reasonable safeguards designed to protect Customer Personal Data in connection with Restricted Transfers.
Customer acknowledges that Customer is responsible for determining whether its use of the Services complies with transfer requirements applicable to Customer, taking into account the Services selected, Customer’s configuration, Customer’s location, Data Subject locations, Subprocessors, and Customer’s own legal obligations.
This Schedule applies to Customer Personal Data subject to U.S. State Privacy Laws.
Customer is the business, controller, or equivalent entity.
Zapstra is the service provider, contractor, processor, or equivalent entity with respect to Customer Personal Data Processed on behalf of Customer.
Zapstra will Process Customer Personal Data only for the business purposes described in the Agreement, this DPA, Customer’s Documented Instructions, and as otherwise permitted by U.S. State Privacy Laws.
Permitted purposes include:
Zapstra will not:
Zapstra will provide the same level of privacy protection required of service providers, contractors, or processors under applicable U.S. State Privacy Laws.
Zapstra will notify Customer if Zapstra determines it can no longer meet its obligations under this Schedule.
Customer may take reasonable and appropriate steps to help ensure Zapstra uses Customer Personal Data consistently with Customer’s obligations under U.S. State Privacy Laws, including through the audit and compliance mechanisms described in this DPA.
Zapstra may engage Subprocessors as described in this DPA.
Zapstra will require Subprocessors to comply with obligations materially similar to those imposed on Zapstra under this Schedule to the extent applicable to their Processing of Customer Personal Data.
Zapstra will provide reasonable assistance to Customer in responding to consumer privacy requests as described in Section 10 of this DPA.
Customer is responsible for verifying requests and determining whether and how to respond.
If Zapstra creates or receives De-Identified Data, Zapstra will:
This Schedule applies where Customer uses Zapstra Services with Shopify.
Zapstra may receive and process Shopify privacy compliance webhooks, including:
customers/data_request;customers/redact; andshop/redact.Zapstra will use reasonable efforts to respond to valid Shopify privacy compliance webhooks in accordance with Shopify requirements, the Agreement, this DPA, and applicable law.
For customers/data_request webhooks, Zapstra may generate or provide responsive records relating to the relevant customer, order, Shop, or Customer Organization, depending on available data and applicable scope.
Customer remains responsible for determining how to respond to Data Subjects unless Shopify or applicable law requires otherwise.
For customers/redact webhooks, Zapstra will redact, delete, or de-identify relevant customer-level Personal Data from applicable records where required by Shopify requirements, applicable law, and available identifiers.
Customer acknowledges that some records may be retained in redacted, de-identified, aggregated, audit, backup, security, fraud-prevention, or legally required form.
For shop/redact webhooks, Zapstra will delete, redact, or de-identify Customer Data for the relevant Shop within 30 days after receipt of a valid webhook, subject to retention exceptions described in the DPA.
Where Zapstra maintains a shared canonical base that supports multiple Shops, apps, modules, or Services under a Customer Organization, redaction is scoped to the relevant Shop.
A shop/redact webhook for one Shop does not require deletion of:
Zapstra may perform Customer Organization-level deletion or de-identification when:
If Customer reinstalls an app, reconnects a Shop, reactivates a Service, or creates a new Customer Organization after deletion or redaction, Zapstra may treat the reinstallation, reconnection, or reactivation as a new authorization to Process Customer Data for the applicable Shop or Services.