LegalData processing

Data Processing Agreement

Last updated November 4, 2026

1. Parties and Scope

This Data Processing Agreement (“DPA”) forms part of the Terms of Service between APUS DATA Mateusz Jerzyk, VAT ID PL5140344860, ul. Olsztyńska 42a/8, 51-423 Wrocław, Poland (“Processor”, “we”, “Affinsy”) and you, the customer (“Controller”, “you”), collectively the “Parties”.

This DPA applies to the processing of personal data that you import or make available to us through the Affinsy platform (affinsy.com), by CSV upload, webhook, the API or the Shopify app, for the purpose of generating e-commerce analytics: Market Basket Analysis, RFM customer segmentation and the audiences built from them.

This DPA is entered into in accordance with Article 28 of the General Data Protection Regulation (EU) 2016/679 (“GDPR”).

2. Definitions

  • “Personal Data” means any information relating to an identified or identifiable natural person, as defined in Article 4(1) of the GDPR.
  • “Processing” means any operation performed on Personal Data, as defined in Article 4(2) of the GDPR.
  • “Sub-processor” means any third party engaged by the Processor to process Personal Data on behalf of the Controller.
  • “Data Subject” means an identified or identifiable natural person whose Personal Data is processed.
  • “Transaction Data” means the e-commerce data you import into Affinsy, which may include order IDs, customer identifiers, product names and IDs, prices, quantities and dates.

3. Subject Matter and Details of Processing

Purpose of processingTo provide e-commerce analytics: Market Basket Analysis, RFM customer segmentation, audiences built from them, and the AI chat assistant that answers questions about those analyses.
Nature of processingCollection (import), storage, deduplication (matching on order ID and product), aggregation, statistical analysis, and the generation of analyses and audiences. Data is retained until you delete it.
Categories of Data SubjectsYour e-commerce customers whose orders are included in the Transaction Data. This may include end consumers and business customers.
Types of Personal DataCustomer identifiers (customer IDs, or email addresses where you use them as identifiers), order IDs, product names and IDs, transaction amounts, quantities and order dates. No special categories of data (Article 9 GDPR) are processed.
Duration of processingFor the duration of the service agreement. Transaction Data persists until you delete it or close your account. Deleted data is permanently removed within 30 days.

4. Obligations of the Processor

The Processor shall:

  • Process Personal Data only on documented instructions from the Controller, including with regard to transfers of Personal Data to a third country, unless required to do so by Union or Member State law. Using the Service, including connecting an AI assistant through the MCP connector or the API, constitutes such an instruction.
  • Ensure that persons authorized to process Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
  • Implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk, including encryption of data in transit and at rest, access controls and regular security assessments.
  • Not engage another processor (Sub-processor) without prior specific or general written authorization of the Controller. In the case of general written authorization, the Processor shall inform the Controller of any intended changes concerning the addition or replacement of Sub-processors, giving the Controller the opportunity to object.
  • Assist the Controller in ensuring compliance with obligations related to security of processing, notification of personal data breaches, data protection impact assessments and prior consultations (Articles 32 to 36 GDPR).
  • At the choice of the Controller, delete or return all Personal Data to the Controller after the end of the provision of services, and delete existing copies unless Union or Member State law requires storage.
  • Make available to the Controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 GDPR and allow for and contribute to audits, including inspections, conducted by the Controller or another auditor mandated by the Controller.

5. Technical and Organizational Measures

The Processor implements the following security measures:

  • Encryption in transit: all data is transmitted over HTTPS/TLS. Communication with third-party services uses encrypted channels.
  • Encryption at rest: data stored in Google BigQuery, Google Cloud Storage and MongoDB Atlas is encrypted at rest with provider-managed keys. Shopify store access tokens are additionally encrypted with AES-256-GCM.
  • Access control: multi-tenant data isolation by tenant identifier. OAuth 2.0 with PKCE for API and MCP access, with a consent screen per connected application. Session-based authentication for the web application.
  • Token security: OAuth tokens and API keys are stored as SHA-256 hashes, never in plain text. Access tokens expire after 1 hour and refresh tokens after 30 days.
  • Password security: passwords on shared analyses are hashed with bcrypt (10 rounds).
  • Data isolation: each customer’s Transaction Data is isolated by tenant ID in BigQuery (tables clustered by tenant) and by account in MongoDB.
  • Infrastructure: the application runs on Vercel with automatic security updates. The application database runs on MongoDB Atlas with automated backups. The data warehouse and the analysis engine run on Google Cloud Platform.
  • AI processing: the chat assistant receives aggregated analysis results, product names and rule statistics. It does not receive customer identifiers; audience customer lists are exported from the analysis page, not through the assistant.

6. Sub-processors

The Controller provides general authorization for the Processor to engage the following Sub-processors. The Processor shall notify the Controller of any changes to this list at least 14 days in advance.

Sub-processorPurposeLocation
Google Cloud Platform (BigQuery, Cloud Storage, Cloud Run)Data warehousing, file storage, analysis computationEU (BigQuery EU multi-region)
Google Generative AI (Gemini)AI chat assistant and generated insights, on aggregated analysis results onlyEU / US
MongoDB AtlasApplication database (accounts, analyses, audiences, metadata)United States
Vercel Inc.Application hosting, serverless compute and file storageUnited States (global edge network)
Stripe Inc.Payment processingUS / EU
Resend Inc.Transactional email deliveryUnited States
Shopify, Inc. is not a Sub-processor: when you install the Shopify app, Shopify is the source of your Transaction Data, and the AI assistant or application you connect through the MCP connector or the API is your own processor, engaged on your instruction.

All Sub-processors are bound by contractual obligations to maintain the confidentiality and security of Personal Data and to process it only for the specified purposes. Where Sub-processors are located outside the EEA, appropriate safeguards are in place, including Standard Contractual Clauses (SCCs) as approved by the European Commission.

7. International Data Transfers

Your Transaction Data is stored in the European Union (Google BigQuery, EU multi-region). Account records, analysis results and audiences are stored with MongoDB Atlas in the United States, and the application runs on Vercel’s global network. Where Personal Data is transferred outside the EEA, the transfer is protected by:

  • European Commission adequacy decisions, where applicable.
  • Standard Contractual Clauses (SCCs) adopted by the European Commission.
  • The EU-US Data Privacy Framework, for certified US organizations.

8. Data Subject Rights

The Processor shall assist the Controller in fulfilling its obligation to respond to requests from Data Subjects exercising their rights under Chapter III of the GDPR (access, rectification, erasure, restriction, portability, objection). If a Data Subject contacts the Processor directly, the Processor shall promptly redirect the request to the Controller. For stores connected through the Shopify app, Shopify forwards customer data requests and erasure requests to the Processor, which answers them within 30 days.

9. Data Deletion and Return

You may delete your data at any time through:

  • Clear data on a workspace’s Data page, which removes all imported Transaction Data, files and import records of that workspace.
  • Delete workspace on the same page, which removes the workspace with its data and analyses.
  • Purge all data on the Account page, which erases every workspace in the account.
  • Analysis deletion: an analysis deleted from the dashboard is removed at once. Analyses removed with a workspace, a space or a purge are retained for 30 days and then permanently removed.
  • Account closure: on request to hello@affinsy.com, all your data (account information, Transaction Data, analyses, audiences and associated files) is permanently deleted within 30 days.

Import jobs that are started but not completed are deleted automatically after 1 hour.

10. Data Breach Notification

The Processor shall notify the Controller without undue delay after becoming aware of a personal data breach. The notification shall include:

  • A description of the nature of the breach, including the categories and approximate number of Data Subjects and Personal Data records concerned.
  • The likely consequences of the breach.
  • The measures taken or proposed to address the breach, including measures to mitigate its possible adverse effects.

The Processor shall cooperate with the Controller and take reasonable steps to assist in the investigation, mitigation and remediation of the breach.

11. Audit Rights

The Controller has the right to conduct audits, including inspections, to verify the Processor’s compliance with this DPA. The Processor shall make available all information necessary to demonstrate compliance and contribute to such audits. Audits shall be conducted with reasonable advance notice and during normal business hours, minimizing disruption to the Processor’s operations.

12. Liability and Indemnification

Each party’s liability under this DPA is subject to the limitations and exclusions set forth in the Terms of Service. The Processor shall be liable for damage caused by processing only where it has not complied with obligations of the GDPR specifically directed to processors or where it has acted outside or contrary to lawful instructions of the Controller.

13. Term and Termination

This DPA shall remain in effect for the duration of the Processor’s processing of Personal Data on behalf of the Controller. Upon termination of the service agreement, the Processor shall, at the Controller’s choice, delete or return all Personal Data and delete existing copies within 30 days, unless applicable law requires further storage.

14. Governing Law

This DPA shall be governed by and construed in accordance with the laws of Poland, without regard to its conflict of laws principles. Any disputes arising under this DPA shall be subject to the exclusive jurisdiction of the courts of Wrocław, Poland.

15. Contact

For questions about this DPA or to exercise any rights, contact:

APUS DATA Mateusz Jerzyk

Data Protection Officer: Mateusz Jerzyk

Email: hello@affinsy.com

Address: ul. Olsztyńska 42a/8, 51-423 Wrocław, Poland

VAT ID: PL5140344860