Data Processing Agreement

Version: 1.9
Effective Date: November 13, 2026

This Data Processing Agreement (“DPA”) forms part of and is incorporated into the PartnerPortal.io Terms of Service between PartnerPortal LLC (“Processor”) and the customer entity using the Services (“Controller” or “Customer”) (together with the Terms of Service and Privacy Policy, the “Agreement”).

This DPA is intended to satisfy the requirements of applicable data protection laws, including the EU General Data Protection Regulation (EU) 2016/679 (“GDPR”), UK GDPR, applicable U.S. privacy laws including the California Consumer Privacy Act (“CCPA/CPRA”), and the Australian Privacy Act 1988 (Cth), including the Australian Privacy Principles (“APPs”), where applicable.

1. Scope and Processing Instructions

Processor shall process Personal Data only:

  • on documented instructions from Customer;
  • as necessary to provide the Services; or
  • as required by applicable law.

Customer is responsible for determining the lawful basis and purposes for processing Personal Data.

Customer acknowledges that, where it connects third-party systems or enables integrations within the Services, including customer relationship management, accounting, billing, or payment systems, Processor may process Personal Data transmitted from or through such systems in order to provide the Services in accordance with Customer’s configuration and instructions.

2. Roles of the Parties

  • Customer acts as the Data Controller.
  • Processor acts as the Data Processor (or “Service Provider” under CCPA/CPRA where applicable).

Processor does not sell or share Personal Data for its own commercial purposes.

3. Description of Processing

Processor processes Personal Data solely to provide and support the PartnerPortal.io platform, including:

  • hosting partner portals
  • authentication and account management
  • integrations and workflow processing
  • analytics, monitoring, and security
  • onboarding, support, and troubleshooting
  • receiving, processing, and displaying data from third-party systems connected by Customer
  • revenue attribution, commission-related reporting, transaction visibility, reconciliation, and related support functionality where enabled by Customer

Data Subjects

  • Customer administrators and users
  • partners and affiliates invited by Customer
  • employees or representatives of Customer or its partners
  • Customer’s prospects, leads, customers, buyers, payers, or other business contacts whose Personal Data is transmitted to Processor through Customer’s use of the Services or connected third-party systems

Categories of Personal Data

  • names and contact information
  • account and profile data
  • portal activity and usage data
  • integration-related data
  • support communications
  • third-party system data transmitted by or on behalf of Customer through connected integrations
  • payment or billing-related data, including transaction metadata, customer billing or contact email, transaction amounts, currency, timestamps, refund status, and external identifiers such as customer IDs, charge IDs, refund IDs, invoice IDs, subscription IDs, or connected account identifiers
  • internal service linkage data, including company, lead, partner, or transaction associations, to the extent such data relates to identified or identifiable individuals

The Services are not designed or intended for the processing of special categories of personal data, sensitive personal information, health information, student or educational records, or other specially regulated categories of data, and Processor does not intentionally process such data. Customer is responsible for not submitting such data to the Services except where expressly agreed by Processor in writing.

Duration

Processing continues during the subscription term and thereafter only as required for backup retention or legal obligations.

To the extent Customer enables integrations that create persistent reporting, audit, reconciliation, or transaction-history records within the Services, Processor may retain such records for the duration necessary to provide the Services, maintain those functions, comply with legal obligations, and satisfy standard backup retention practices, unless and until deletion is requested by Customer and is available under the applicable Service functionality.

4. Confidentiality and Security

Processor shall:

  • ensure persons authorized to process Personal Data are bound by confidentiality obligations;
  • implement appropriate technical and organizational security measures designed to protect Personal Data against unauthorized access, loss, or disclosure;
  • maintain security practices appropriate to the risk and nature of the Services.

Additional security documentation may be available via:

https://security.partnerportal.io/

5. Assistance with Data Subject Rights and Compliance

Processor shall assist Customer, taking into account the nature of processing, by:

  • helping respond to data subject requests (access, deletion, correction, portability, etc.);
  • assisting with data protection impact assessments and regulatory inquiries where reasonably requested;
  • providing such assistance in a timely manner so Customer can meet applicable legal deadlines.

6. Personal Data Breach Notification

Processor shall notify Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer’s Personal Data, and in any event, where reasonably feasible, within seventy-two (72) hours of becoming aware.

Such notification shall include the information reasonably available to Processor that is necessary for Customer to meet its applicable reporting obligations.

7. Subprocessors

Customer authorizes Processor to engage subprocessors necessary to provide the Services.

Current subprocessors include:

  • Amazon Web Services (AWS) — infrastructure hosting
  • MongoDB Atlas — database hosting
  • Stripe — billing and payments
  • HubSpot — CRM and communications
  • Google (Workspace) — productivity and email
  • Okta (Auth0) — identity and access management
  • Cloudflare — DNS, content delivery, edge security, and bot protection
  • Weglot — translation of portal content and email text, where Customer enables translation

Processor shall:

  • impose data protection obligations on subprocessors equivalent to those in this DPA, by written contract;
  • remain responsible to Customer for the performance of each subprocessor’s obligations;
  • maintain a current list of subprocessors on this page;
  • give Customer at least thirty (30) days’ prior written notice of any intended addition or replacement of a subprocessor, by email or in-app notice to Customer’s account administrators, and by updating the list on this page;
  • allow Customer to object to the change on legitimate data protection grounds within that notice period.

If the parties cannot resolve a good-faith objection, Customer may terminate the affected Services consistent with the Agreement.

8. International Transfers

Processor hosts the Services in the United States. Where Customer transfers Personal Data to Processor from the European Economic Area (EEA), the United Kingdom, or Switzerland, the transfer is governed by the safeguards in this Section 8, which apply automatically and require no separate signature.

8.1 EU Standard Contractual Clauses

For transfers of Personal Data subject to the GDPR, the parties enter into the standard contractual clauses for the transfer of personal data to third countries adopted by the European Commission in Implementing Decision (EU) 2021/914 of 4 June 2021 (the “SCCs”), available at https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj, which are incorporated into this DPA by reference as follows:

  • Module Two (transfer controller to processor) applies. Customer is the data exporter and Processor is the data importer.
  • Clause 7 (docking clause) does not apply.
  • Clause 9(a): Option 2 (general written authorisation) applies. The time period for prior notice of changes to subprocessors is thirty (30) days, given as described in Section 7.
  • Clause 11(a): the optional language does not apply.
  • Clause 13: the competent supervisory authority is the one identified in Annex I.C below.
  • Clause 17: Option 1 applies. The SCCs are governed by the law of Ireland.
  • Clause 18(b): disputes arising from the SCCs are resolved by the courts of Ireland.
  • Annexes I, II, and III of the SCCs are completed by Schedules 1, 2, and 3 of this DPA.

8.2 United Kingdom

For transfers of Personal Data subject to the UK GDPR, the parties enter into the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses (version B1.0) issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018 (the “UK Addendum”), which is incorporated into this DPA by reference. Its tables are completed as follows:

  • Table 1: the parties, their details, and their contacts are as set out in Schedule 1, Part A.
  • Table 2: the Addendum EU SCCs are the SCCs, with the selections described in Section 8.1.
  • Table 3: the Appendix Information is set out in Schedules 1, 2, and 3.
  • Table 4: neither party may end the UK Addendum as described in its Section 19.

8.3 Switzerland

For transfers of Personal Data subject to the Swiss Federal Act on Data Protection (“FADP”), the SCCs apply as described in Section 8.1, with the following changes: references to the GDPR include the FADP; the competent supervisory authority is the Swiss Federal Data Protection and Information Commissioner; and the term “Member State” is not to be interpreted so as to prevent data subjects in Switzerland from bringing claims in their place of habitual residence.

8.4 Order of Precedence

If there is a conflict between the SCCs (including as amended by the UK Addendum or Section 8.3) and the rest of this DPA or the Agreement, the SCCs prevail to the extent of the conflict.

8.5 Australia

Where Australian Privacy Law applies, Processor will handle Personal Data in accordance with the Australian Privacy Principles to the extent applicable to its processing, and will, taking into account the nature of the processing, provide Customer with reasonable assistance in meeting its obligations relating to the disclosure of personal information to overseas recipients.

9. Audit Rights

Processor shall make available reasonable information necessary to demonstrate compliance with this DPA.

If such information is insufficient for Customer’s legal obligations, Processor will allow reasonable audits or inspections by Customer or an independent auditor, subject to:

  • reasonable advance notice;
  • confidentiality obligations;
  • limitation to once annually unless required by law or following a security incident;
  • minimization of operational disruption.

10. Return or Deletion of Data

Upon termination of Services, Processor shall delete or return Personal Data at Customer’s request, unless retention is required by law or standard backup retention practices.

Customer acknowledges that certain data stored within the Services, including integration-derived records, reporting history, transaction history, audit logs, and backup copies, may be subject to technical, legal, operational, or records-retention limitations on immediate deletion. Where applicable, Processor may also provide Customer with product functionality to delete or reset certain categories of stored data during the subscription term.

11. Liability

The liability of each party arising under or in connection with this DPA shall be subject to, and included within, the limitations and exclusions of liability set forth in the Agreement, unless otherwise required by applicable law.

Nothing in this DPA expands either party’s liability beyond the limits established in the Agreement.

12. Term

This DPA remains effective for the duration of the Agreement.

Schedule 1 — Annex I of the SCCs

A. List of Parties

Data exporter

  • Name, address, and contact person: the Customer entity, address, and contact details given in Customer’s PartnerPortal.io account or, where one exists, in the signed agreement between the parties
  • Activities relevant to the data transferred: use of the Services to run Customer’s partner program
  • Role: controller
  • Signature and date: by accepting the Agreement or signing an agreement that incorporates this DPA, on the date of that acceptance or signature

Data importer

  • Name: PartnerPortal LLC
  • Address: 300 Center Drive Ste G, Superior, CO 80027, USA
  • Contact person: Erick Danzer, Chief Executive Officer, [email protected]
  • Activities relevant to the data transferred: providing the Services described in Section 3
  • Role: processor
  • Signature and date: by entering into the Agreement, on the date it takes effect

B. Description of Transfer

  • Categories of data subjects: as listed under “Data Subjects” in Section 3.
  • Categories of personal data: as listed under “Categories of Personal Data” in Section 3.
  • Sensitive data: none. The Services are not intended for special categories of personal data, as described in Section 3.
  • Frequency of the transfer: continuous, for as long as Customer uses the Services.
  • Nature of the processing: hosting, storage, retrieval, display, transmission to and from systems connected by Customer, and the other processing needed to provide the Services.
  • Purpose of the transfer and further processing: to provide, secure, and support the Services, as described in Section 3.
  • Retention period: for the subscription term and afterwards as described under “Duration” in Section 3 and in Section 10.
  • Location of processing: the United States. Processor’s application infrastructure and file storage run in Amazon Web Services (us-east-1, N. Virginia), and its database runs in MongoDB Atlas on AWS (us-east-1, N. Virginia).
  • Transfers to subprocessors: to the subprocessors listed in Section 7, for the purposes stated there and for the duration of the Agreement.

C. Competent Supervisory Authority

Where Customer is established in an EU Member State, the supervisory authority of that Member State. Where Customer is not established in the EU but has appointed a representative under Article 27(1) of the GDPR, the supervisory authority of the Member State in which that representative is established. Otherwise, the supervisory authority of the Member State in which the data subjects whose personal data is transferred are located.

Schedule 2 — Annex II of the SCCs: Technical and Organisational Measures

Processor maintains the following measures, described in more detail on its Security page:

  • Encryption: all data is encrypted in transit using TLS 1.2 or higher, and at rest using AES-256 in the database (MongoDB Atlas) and file storage (Amazon S3).
  • Identity and authentication: identity and passwords are managed by Auth0 (Okta). Processor does not store user passwords. Single sign-on and multi-factor authentication are supported.
  • Access control: role-based access control with configurable permissions and a deny-by-default policy. Every request is authenticated and checked against the user’s permissions.
  • Tenant isolation: each customer’s data is logically isolated, and every database query is scoped to the requesting customer by the application.
  • Logging and monitoring: authentication events, account and permission changes, API access, and infrastructure activity are logged. Production logs are retained for 12 months in append-only, access-controlled systems.
  • Availability and backups: continuous, encrypted backups with point-in-time recovery, stored separately from primary data.
  • Environment separation: production and non-production environments run on separate infrastructure, including separate cloud accounts, database clusters, and identity tenants. Production data is not copied into development or testing.
  • Threat protection: DDoS mitigation at the network edge, rate limiting and filtering at the API layer, brute-force and suspicious-login protection, and security headers on every response.
  • Change management: changes are made on separate branches, reviewed through merge requests, deployed first to staging, and released to production through a separate approved step.
  • Personnel: persons authorized to process Personal Data are bound by confidentiality obligations, and access is limited to what their role requires.
  • Incident response: personal data breaches are reported to Customer as described in Section 6.
  • Assistance to Customer: Processor helps Customer respond to data subject requests and meet its other obligations as described in Section 5.
  • Subprocessors: Processor imposes data protection obligations on subprocessors as described in Section 7.

Schedule 3 — Annex III of the SCCs: List of Subprocessors

Customer has authorized the subprocessors listed in Section 7, for the purposes stated there. Changes to that list are made as described in Section 7.

Choose a Path

Three ways to launch your partner program.

Launch a free portal

Launch in 60 seconds.
No credit card required.

Claim a custom portal

We'll set up a branded portal for you.
Delivered within 24 hours.

Schedule a demo

Schedule a call with our team.
See it live and get answers.