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
Privacy and breach contact: privacy@brillnet-app.com
Website: wm-admin.pl
Version: 2026-10-12-beta.2
This is an informational translation. The Polish version is binding.
1. Current state
The WM Administrator landing page does not use external analytics, advertising, pixels or session recording. The application uses only mechanisms necessary for sign-in, sessions, form protection and security. It does not store tenant data in localStorage, IndexedDB or the Cache API.
2. Categories
| Category | Provider | Purpose | Typical duration |
|---|---|---|---|
WM Administrator session, name/prefix wm-admin | Brillnet / Cloudflare | maintaining a signed-in session, security and sign-out | session or configured session duration |
| sign-in and registration protection | Cloudflare Turnstile | distinguishing legitimate requests from automated abuse | according to Cloudflare documentation; only at a protected form |
| language or accessibility preference, if saved by the User | Brillnet | retaining an explicitly selected preference | until the preference or local setting is deleted |
| Stripe | Stripe | secure Checkout, fraud prevention and payment | only after proceeding to Stripe; according to Stripe's policy |
| authorisation of the optional calendar integration | only after starting authorisation; according to Google's policy |
External providers may change exact technical cookie names and lifetimes. Before every production release, Brillnet performs automated and manual browser storage audits; the result must match this table.
3. Basis and consent
Mechanisms necessary for transmission, security, session maintenance and delivery of the requested Service operate without separate consent to the extent permitted by Article 399 of the Polish Electronic Communications Law. Analytics, personalisation or marketing mechanisms, if added, will only start after voluntary consent.
4. Control
The User can delete cookies in browser settings. Blocking necessary cookies may prevent sign-in or secure operations. Withdrawing future consent for optional purposes will be as easy as giving it.
5. No hidden tracking
We do not use advertising fingerprinting, cross-site identifiers or session replay. The server-side security log is not a cookie, but is subject to the minimisation and retention described in the Privacy Policy.
> Contact details and domains in this presentation were updated on 2026-09-08. The original document and previous acceptances remain unchanged.