Brillnet Landing Page Processor List
Last updated: 2026-10-12
Version: 1.2
Scope: brillnet-app.com as a landing page only
1. Scope
This list covers providers that may process data in connection with the Brillnet landing page, contact forms, newsletter or product-update subscriptions, security, and technical website operation.
It does not cover Brillnet's application environments, customer tenants, application user accounts, payments, or data processed under separate B2B agreements. Those areas require separate contractual or implementation documents.
2. Providers
| Provider | Role | Data categories | Use condition |
|---|---|---|---|
| Cloudflare, Inc. | CDN, website security, abuse prevention and form Worker runtime | IP address, HTTP headers, technical request data, security signals, error metadata | website and form infrastructure |
| Resend / Plus Five Five, Inc. | delivery of form messages, newsletters, product updates and Brillnet-owned contact-list handling | first name, last name, e-mail address, company name, message content, subscription source, consent or unsubscribe status, technical delivery metadata | when the user submits a form or subscribes to Brillnet communication |
| Accounting, legal or administrative providers | contracts, billing and legal obligations | contact, contractual and billing data | only where a contact leads to contract handling, billing or legal obligations |
3. Transfers outside the European Economic Area
Technical and email providers may process specified data outside the EEA, including Resend / Plus Five Five, Inc. Transfers are qualified by recipient, data and purpose under GDPR Chapter V. We use the applicable adequacy decision, including DPF only for a covered recipient and scope, or Standard Contractual Clauses with the required assessment and supplementary measures. A DPA governs Article 28 duties; the transfer also requires an applicable Chapter V basis. Details of the basis and safeguards are available through this Policy’s contact.
4. Deliberately excluded items
The Brillnet landing page should not list services that are not used by the page itself, in particular:
- payment processors, unless the form actually handles payments,
- application login systems,
- customer application databases,
- tenant operational tools,
- marketing systems other than Resend for forms and Brillnet-owned contact lists.
If any of those services is actually added to the landing page, this list should be updated before deployment.