# Subprocessors and data recipients

**Service Provider / Operator:** Brillnet Piotr Adamski, ul. Henryka Sienkiewicza 73/6, 90-057 Łódź, Polska, NIP 7321779060, REGON 101551294

**Service contact:** [kontakt@wm-admin.pl](mailto:kontakt@wm-admin.pl)

**Privacy and breach contact:** [privacy@brillnet-app.com](mailto:privacy@brillnet-app.com)

**Website:** [wm-admin.pl](https://wm-admin.pl/?lang=en)

**Version:** 2026-10-12-beta.2

This is an informational translation. The Polish version is binding.

## 1. How to read this list

The list distinguishes Brillnet's subprocessors for Customer Data from providers serving data for which Brillnet is controller, and services chosen directly by the Customer. “Conditional” means the entity receives data only when a particular feature is enabled or a fallback path is used.

## 2. Customer Data subprocessors

| Entity | Service and purpose | Scope | Location / transfer | Status |
|---|---|---|---|---|
| **Cloudflare, Inc. and relevant group entities** | Workers, D1, R2, Durable Objects, Queues, Workflows, Containers, Turnstile, Secrets Store and observability | application data, files, technical metadata, session and security identifiers | persistent data configured with EU jurisdiction; stateless execution and limited metadata may occur globally; Data Privacy Framework (DPF)/standard contractual clauses (SCC) under Cloudflare's DPA | ongoing |
| **Resend, Inc.** | fallback email sending when the primary Cloudflare Email Service is unavailable or insufficient | recipient address, minimal transactional template and delivery metadata; no tenant documents or content; open/click tracking disabled | global processing under Resend's DPA and subprocessor list | conditional |

Cloudflare Email Service is part of the Cloudflare platform and is covered by the Cloudflare entry. Current terms: [Cloudflare DPA](https://www.cloudflare.com/cloudflare-customer-dpa/) and [Cloudflare subprocessor list](https://www.cloudflare.com/gdpr/subprocessors/). Resend: [DPA](https://resend.com/legal/dpa) and [subprocessor list](https://resend.com/legal/subprocessors/).

## 3. Recipients and providers in other roles

| Entity | Role | Scope | When |
|---|---|---|---|
| **Stripe group** | Brillnet's processor or an independent controller, depending on the data and payment operation; not a default subprocessor of tenant content | payer, organisation, plan, amount, subscription and transaction status; no Community documents or full card details held by WM Administrator | Checkout, Billing, Connect and payments |
| **Google LLC / Google Workspace** | provider chosen by the Customer; role depends on the Customer's agreement with Google | events and participants selected for synchronisation | only after enabling Google Calendar |
| **banks and payment operators** | generally independent controllers | payment instruction or statement data selected by the Customer | only for a configured integration |
| **KSeF and public authorities** | independent controllers acting under law | invoice, declaration or case data sent by an authorised User | only after sending is approved |
| **Brillnet's legal and tax advisers and auditors** | recipients bound by confidentiality | minimum scope needed for defending claims, compliance or audit | exceptionally, when needed |

Stripe: [DPA](https://stripe.com/legal/dpa), [Service Providers](https://stripe.com/legal/service-providers) and [Privacy Center](https://stripe.com/legal/privacy-center).

## 4. Minimisation rules

1. Resident registers, documents, cases, votes and unit balances are not sent to Stripe.
2. Fallback email contains no tenant attachments or form content. If a message requires sensitive data, the User receives a secure link to the application requiring authentication.
3. Google, KSeF and banking integrations are disabled by default and activated by the Customer's authorised administrator.
4. Provider tokens are protected as secrets and scope-limited.

## 5. Changes

A planned change to a Customer Data subprocessor is communicated at least 14 days in advance to the organisation administrator's address and in the application. The notice includes name, purpose, scope, location and date. Objections are handled according to the DPA. Provider lists last verified on **25 July 2026**.

## Scope of backup periods

D1/R2 windows concern application infrastructure. They are not universal retention statements for every email-provider or other recipient copy. Sending data, own billing and security require separate role, purpose, retention and basis mapping. Deletion requests are assessed accordingly; a supplier term alone does not replace a legal basis or customer instruction.


> Contact details and domains in this presentation were updated on 2026-09-08. The original document and previous acceptances remain unchanged.