International Transfer Terms
Version dated November 15, 2026
These terms apply only when an accepted Warpix order form names them, with their version date, as its required transfer document. They complete the transfer mechanism that Section 9 of the Data Processing Addendum (the “DPA”) calls for. Terms that these terms do not define have the meanings given in the DPA, and a Section or Schedule means that Section or Schedule of the DPA unless it says otherwise.
Standard Contractual Clauses, UK Addendum, and Swiss changes
Where Data Protection Laws require a transfer mechanism for Customer Personal Data that Customer transfers to Provider under the Agreement, the parties agree to:
- the standard contractual clauses annexed to European Commission Implementing Decision (EU) 2021/914 of June 4, 2021 (the “EU SCCs”), Module Two (controller to processor), completed as set out in Part 1 and Annexes I to III below, with the changes in Part 3 for transfers governed by the Swiss Federal Act on Data Protection; and
- for transfers subject to UK data protection law, the International Data Transfer Addendum to the EU SCCs issued by the UK Information Commissioner (version B1.0) (the “UK Addendum”), completed as set out in Part 2 below.
The parties accept the EU SCCs and the UK Addendum, with these selections, by accepting an order form that names these terms. They are incorporated into the Agreement by reference from the order form's effective date. If they conflict with the rest of the Agreement, the EU SCCs and the UK Addendum prevail.
Part 1: EU SCC selections
- Module
- Module Two (controller to processor) only. Customer is the data exporter and Provider is the data importer.
- Clause 7 (docking clause)
- Included.
- Clause 8.8 (onward transfers)
- Customer instructs Provider to send Customer Personal Data to the services that Customer connects to the Service, such as Slack or Linear, as described in Annex I.B. This is Customer's documented instruction under Clauses 8.1 and 8.8. Each such service processes the data for Customer under Customer's own agreement with it. It is not a subprocessor of Provider under Clause 9 and is not listed in Annex III. Where sending data to such a service is an onward transfer, it is made under Clause 8.8(ii), because the service ensures appropriate safeguards under Article 46 or 47 of Regulation (EU) 2016/679 for that processing through its agreement with Customer, or under Clause 8.8(i) where an adequacy decision covers the transfer. By connecting a service, Customer confirms that it has such an agreement with it. Provider sends a connected service only the data that Customer's settings and its users' actions call for.
- Clause 9(a) (use of subprocessors)
- Option 2, general written authorization. Provider will inform Customer in writing of any intended addition or replacement of a subprocessor at least 14 calendar days in advance, the notice period in Section 8. The authorized subprocessors are in Annex III.
- Clause 11(a) (redress)
- The optional language is not used.
- Clause 13(a) (supervision)
- The competent supervisory authority is set out in Annex I.C.
- Clause 17 (governing law)
- Option 1: the EU SCCs are governed by the law of Ireland.
- Clause 18(b) (choice of forum and jurisdiction)
- The courts of Ireland.
Annex I.A: List of parties
- Data exporter
- Customer, the legal entity named in the order form, at the jurisdiction and address given there. Contact: the privacy or security contact and the legal notice email given in the order form. Activities relevant to the transfer: using the Service under the Agreement. Role: controller. Signature and date: Customer's signature or recorded electronic acceptance of the order form, on the date given there.
- Data importer
- Provider, the Warpix entity named in the order form, at the address given there. Contact: Provider's legal notice email given in the order form. Activities relevant to the transfer: providing the Service to Customer under the Agreement. Role: processor. Signature and date: Provider's signature or recorded electronic acceptance of the order form, on the date given there.
Annex I.B: Description of the transfer
- Data subjects
- As in Schedule 1: Customer's teammates who use the Service (administrators and workspace members); Customer's end users who give feedback, vote, or comment through the widget, including end users Customer identifies to the Service; Customer's customer contacts and customer-account representatives; and people Customer names in feedback or support records, including the authors of Slack messages that Customer's users send to the Service.
- Personal data
- As in Schedule 1: names, business email addresses, and stable external identifiers; organization and role information; account and contact attributes that Customer sends, such as plan, lifecycle and payment state, revenue and currency metadata, and tags; feedback, comments, votes, user actions, and internal notes; import and audit metadata; IP address, browser, and request information; identity-assertion metadata; security events; if Customer connects Slack, Slack workspace, channel, and user names and IDs, Slack message text, links to Slack messages, and replies sent to Slack threads; and, if Customer connects Linear, the Linear workspace's name, ID, and web address, and the ID, key, title, link, team, and state of Linear issues that Customer's users link or look up, or that Linear reports as changed or removed in the connected Linear workspace.
- Sensitive data
- None. Customer will not provide the prohibited sensitive data listed in Section 6 of the SaaS Terms unless the parties first amend the Agreement with appropriate safeguards (Section 3).
- Frequency
- Continuous or occasional, depending on Customer's use of the Service and its support requests.
- Nature of the processing
- As in Schedule 1: receiving, validating, hosting, structuring, searching, displaying, associating, deduplicating, aggregating, importing, exporting, backing up, securing, troubleshooting, and deleting Customer Personal Data, and sending it to services Customer connects, such as Slack and Linear, as Customer's settings and users direct.
- Purpose
- To provide, secure, and support the Service for Customer under Customer's instructions: account-aware product-feedback collection, organization, and analysis, roadmap and release continuity, and founder-assisted support.
- Retention
- For the term of the Agreement, then for the export, deletion, backup-expiry, and narrowly permitted retention periods in Section 10. Backups expire through the 14-day rotation.
- Transfers to subprocessors
- The subprocessors in Annex III process Customer Personal Data for the purposes, and in the locations, on the Subprocessors page, for as long as Provider processes it for Customer.
- Disclosures to services Customer connects
- If Customer connects Slack, Provider sends Slack the data described in Schedule 1 under “Services Customer connects”: posts in the channels that Customer's workspace admins pick, what the person using Send to Warpix is shown, and the thread replies that Customer's users send. The recipient is the Slack company that is Customer's processor under Customer's agreement with Slack. These disclosures are made on Customer's instruction under Clause 8.8 (Part 1). Messages that Provider has posted stay in Customer's Slack workspace under Customer's Slack settings, and Customer manages them there. In a channel shared with another organization (Slack Connect), that organization's members can see the posts, and Provider's updates there carry no comment text, no comment author's name and no account context. Updates posted before a channel became shared stay in its history, where that organization's members can read them. If Customer connects Linear, Provider sends Linear the data described in Schedule 1 under “Services Customer connects”: the issues that Customer's users ask Provider to create, the words or issue keys they enter to find an issue, and the card that Provider places on each linked issue. The recipient is Linear Orbit, Inc., in the United States, which processes the data for Customer under Customer's agreement with Linear. These disclosures are also made on Customer's instruction under Clause 8.8 (Part 1). Provider never edits a Linear issue after creating it; it only adds, updates, and removes its own cards.
Annex I.C: Competent supervisory authority
Where Customer is not established in an EU Member State but falls within Article 3(2) of Regulation (EU) 2016/679 and has appointed a representative under Article 27(1), the competent supervisory authority is the supervisory authority of the Member State where that representative is established. Where Customer is not established in an EU Member State but falls within Article 3(2) of Regulation (EU) 2016/679 without having to appoint a representative under Article 27(2), it is the supervisory authority of one of the Member States where the data subjects whose personal data is transferred, in relation to the offering of goods or services to them or the monitoring of their behavior, are located: the one where most of them are located, unless Customer names another of those Member States in writing. Where Customer is established in an EU Member State, it is the supervisory authority responsible for Customer's compliance with Regulation (EU) 2016/679 for the transfer. For transfers under the UK Addendum, it is the Information Commission, which took over the functions of the UK Information Commissioner on September 30, 2026.
Annex II: Technical and organizational measures
Provider maintains the measures in Schedule 2, under Section 5. In brief:
- TLS for public service traffic and controlled server ingress.
- ZITADEL authentication with short-lived tokens, and server-side tenant, workspace, membership, and role checks.
- Workspace-scoped queries and database constraints that reduce cross-tenant access risk.
- Widget safeguards: opaque board identifiers, exact origin allowlists, short-lived hashed sessions, one-time signed identity assertions, and replay protection.
- Least-privilege runtime accounts, secret files readable only by root or, for the secrets the API reads itself, only by the API's own service account (mode 0600), privacy-aware logging, bounded inputs, rate limits, and request timeouts.
- Integration credentials, such as Slack bot tokens and Linear access and refresh tokens, encrypted with AES-256-GCM and deleted on disconnection or once Provider learns that they are no longer accepted; requests from Slack accepted only with a valid Slack signature, and updates from Linear only with a valid Linear signature and a recent send time.
- Version-controlled and tested changes, dependency and source scanning, health checks, and rollback procedures.
- Weekly local database backups on a 14-day rotation, with integrity checks and a documented restore procedure.
- Founder-limited production access, confidentiality duties, and incident handling.
Schedule 2 also lists what the Service does not currently include. Provider assists Customer with data-subject requests as described in Section 7, and binds its subprocessors to data-protection obligations as described in Section 8.
Annex III: List of subprocessors
Customer authorizes the subprocessors on the Subprocessors page (Schedule 3), which gives each one's purpose, data, processing location, and provider information. At the date of this version, the core-service subprocessors are RackNerd (server infrastructure in the United States), Cloudflare (DNS and static delivery), and Google Workspace (support and service email). Changes follow Section 8 and the notice period in Part 1. Services that Customer connects to the Service, such as Slack or Linear, are not subprocessors (Part 1, Clause 8.8) and are not listed here.
Part 2: UK International Data Transfer Addendum
For transfers subject to UK data protection law, the UK Addendum is completed as follows.
- Table 1: Parties
- Start date: the order form's effective date. Exporter: Customer. Importer: Provider. Their details and key contacts are in Annex I.A. The parties accept the UK Addendum as described at the start of these terms.
- Table 2: Selected SCCs, Modules and Selected Clauses
- The Approved EU SCCs, including the Appendix Information, with only Module Two and the selections in Part 1 brought into effect: Clause 7 included; Clause 9(a) Option 2, with 14 days' notice; Clause 11 optional language not used; and the Clause 8.8 instruction in Part 1.
- Table 3: Appendix Information
- Annex 1A (List of Parties): Annex I.A above. Annex 1B (Description of Transfer): Annex I.B above. Annex II (Technical and organisational measures): Annex II above. Annex III (List of Sub processors): Annex III above.
- Table 4: Ending this Addendum when the Approved Addendum changes
- Neither party may end the UK Addendum under its Section 19.
Part 2 of the UK Addendum is the Mandatory Clauses of the Approved Addendum, being template Addendum B1.0 issued by the Information Commissioner and laid before Parliament under section 119A of the Data Protection Act 2018 on February 2, 2022, as revised under Section 18 of those Mandatory Clauses.
Part 3: Transfers from Switzerland
Where the transfer is governed by the Swiss Federal Act on Data Protection (FADP), the EU SCCs apply with these changes: references to Regulation (EU) 2016/679 mean the FADP; the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority under Clause 13; “Member State” does not prevent data subjects in Switzerland from suing where they habitually reside (Clause 18(c)); Clauses 17 and 18 otherwise remain as selected.