PirxStream Privacy Policy
Version of 3 November 2026 (version 2) · in force from 3 November 2026
This is an English translation of the Polish Privacy Policy. If the two versions differ, the Polish version prevails.
In short (the text below is binding): we collect only what streaming requires — your e-mail address, account data, connections to platforms, your streams and recordings, and the technical data needed for security. We do not sell data and we do not show ads. The website and the panel use no advertising or tracking cookies. Our server is in Germany. Questions and requests: [email protected].
1. Who is the data controller
- The controller of your personal data is Maciej Poczek, running a business under the name VIDEOMAJSTER MACIEJ POCZEK, ul. Korkowa 35/114, 04-502 Warsaw, Poland, tax ID (NIP) 8262190454, REGON 147173672 (“we”).
- For anything concerning your data, write to [email protected]. We have not appointed a data protection officer.
- This policy covers the website pirxstream.pl and the panel mix.pirxstream.pl (together: the “Service”). Capitalised terms have the meaning given in the Terms of Service (available in Polish).
2. What data, why, on what legal basis and for how long
The legal bases are Article 6(1) of the GDPR: (a) consent, (b) contract — data needed to provide the service, (c) legal obligation, (f) our legitimate interest.
| Data | Purpose | Basis | Retention |
|---|---|---|---|
| Account: e-mail address, password (stored only as an argon2id hash — we do not know it), display name, panel language and theme, dates of sign-up and address confirmation, date and version of the accepted Terms | creating and running the Account, signing in, contacting you about the Account | (b); date of acceptance of the Terms — (f) proof of the contract | until the Account is deleted (see section 7) |
| Platform connections: account identifier with the provider (Google, Facebook, Twitch), e-mail address of that account, access tokens (encrypted), granted scopes, history of connecting and disconnecting; manually entered stream keys (encrypted) | signing in with Google or Facebook, streaming to your channels | (b) | until the platform is disconnected or the Account is deleted |
| Streams: video and audio from sources and Guests, titles, descriptions, mixer settings, overlays, statistics (viewer count, duration, data sent) | producing the Stream and sending it to external Platforms | (b) | live video and audio — only while the Stream lasts; settings and statistics — until the Account is deleted |
| Recordings | storing recordings you can download | (b) | depending on the plan: 7 days (trial and Basic), 30 days + 180-day archive (Pro — including an Account created during the beta, which uses the Pro plan), 90 days + 365-day archive (Max); or until you delete them earlier |
| Guests: name given when joining from an invitation, video and audio; consent to recording and publishing their image and voice and consent to remote camera adjustment — wording and text version, date, the Guest’s name, and every withdrawal | the Guest taking part in a Stream organised by the User — we process this data on the User’s behalf (see “Data of Guests and people in Streams” below); the consent record — so the User can show that the Guest gave it | the basis is set by the User as controller; our own purposes (moderation, security) — (f) | video and audio — only while the Stream lasts (unless the User records it); name and consent record — until the Stream or the User’s Account is deleted |
| Platform chat: author name, avatar address and message text fetched from YouTube or Twitch | showing the chat in the panel during the Stream | (b) towards the User; (f) towards message authors | until the User’s Account is deleted |
| Payments: customer and subscription identifiers in Stripe, plan, payment status and dates; invoice data | billing the plan, invoices | (b); invoices and accounting — (c) | billing data — until the Account is deleted; invoices and accounting records — 5 years from the end of the tax year |
| Viewers of paid Streams and donors: e-mail address, amount, message to the creator, Stripe payment identifiers | selling access to the Stream and passing a tip to the creator | (b) | until the creator’s Account is deleted; accounting data — as above |
| Payout account (Stripe Connect): account identifier in Stripe and its verification status (identity verification itself is carried out by Stripe) | payouts from paid access and tips | (b) | until the Account is deleted |
| Trial protection: at sign-up we store hashes (SHA-256) of the IP address, the browser name and a device fingerprint — computed in the browser from characteristics such as screen resolution, time zone, language, graphics card model and text rendering | detecting additional Accounts created to obtain another trial | (f) — preventing abuse | until the Account is deleted |
| Security: IP address and browser name on requests to the server, failed sign-in counters | protection against intrusion and overload, diagnosing failures | (f) | server logs — 30 days; sign-in counters — in server memory, a few minutes |
| Moderation: selected frames of the Stream’s video, analysis result, stored frames flagged by the system, decisions and appeals | detecting prohibited content, handling reports and appeals | (c) — DSA; (f) — security of the Service | frames analysed on the fly are not stored; frames flagged by the system — 90 days from flagging; events, decisions and appeals — until the Account is deleted |
| Content reports: reporter’s data (name, e-mail), content of the report, IP address when reported through the Service | handling the report (Article 16 DSA) | (c) | until the case is closed and the appeal period has passed |
| Bug reports and browser errors: content of the report, page address, browser name, error description; for a report reward — the date it was granted, who granted it, its length and dates | fixing the Service; granting the report reward (§ 7(8) of the Terms) | (f); reward — (b) | until the Account is deleted; reports passed to the task system — until the issue is resolved |
| Panel events: e.g. start and end of a Stream, settings changes | Account history, technical support, abuse detection | (f) | until the Account is deleted |
| E-mail: recipient address, subject, type and delivery status of messages from us; your notification settings | sending messages about the Account (address confirmation, password reset, payments, beta tests, report reward) and getting-started tips | (b); getting-started tips — (f), with an unsubscribe link in each message | until the Account is deleted |
| Marketing messages: e-mail address, date consent was given and withdrawn | sending you e-mails about PirxStream news, promotions and offers — only if you tick the separate, optional consent box (at sign-up, on the document acceptance screen or in Settings → Notifications) | (a) — you may withdraw consent at any time by unticking that box in Settings or via the “Unsubscribe” link in a message; not consenting does not limit your use of the Service | until consent is withdrawn or the Account is deleted |
| Correspondence with us | replying, complaints, defence against claims | (b), (c), (f) | until the matter is closed, then until claims are time-barred |
| Beta launch notice (newsletter): e-mail address, the page you signed up on, the wording of the consent, dates of sign-up, of sending the confirmation link, of confirmation and of unsubscribing | e-mailing you about the beta launch and PirxStream news — also to people without an Account. The sign-up takes effect only after you click the link in the confirmation email; until then we send nothing but that one email | (a) — withdraw consent at any time with the unsubscribe link in every message or by writing to us; after you unsubscribe we keep the address with the dates of consent and unsubscribing as proof that we sent lawfully — (f) | unconfirmed sign-up — 30 days after the link was sent; confirmed — until you unsubscribe; after unsubscribing — 3 years |
| Waiting list for Pirx devices: e-mail address, chosen model, entry source, IP address | notifying you when the devices are available | (a) — you may withdraw consent at any time by writing to us | until consent is withdrawn or the pre-sale ends |
Data of Guests and people in Streams. The User who organises a Stream decides whom to invite, whether to record it and where to send it. If, in doing so, the User processes other people’s data as their controller, the User is responsible for informing them and for the legal basis, and we process that data on the User’s behalf under the data processing agreement in Annex 2 to the Terms of Service. We are a separate controller of that data only for moderation, the security of the Service and handling reports. If you are a Guest and want to exercise your rights, contact the person who invited you; you can also write to us — we will forward your request to them within 3 business days.
Guest consents when joining. Before joining a Stream, the Guest ticks consent to their image and voice being recorded and published in that Stream — without it they cannot join, because taking part in a Stream means exactly showing them. Separately and optionally, the Guest may allow the director to adjust their camera remotely (zoom, focus, light, lens); without that consent only the Guest controls the camera, and the director can only ask for consent, which the Guest accepts or declines. The Guest always sees whether the director can control their camera and turns it off with one tap. Switching to the front camera (the Guest’s face) always requires confirmation on the Guest’s device. We record every consent and its withdrawal with the date and the wording of the text. The Guest can withdraw consent at any time by leaving the Stream and writing to the person who invited them, or to us.
Providing data is voluntary, but without an e-mail address and a password (or signing in with Google or Facebook) you cannot create an Account, and without connecting a platform we cannot stream to your channel.
3. Who processes data on our behalf
Your data is processed on our behalf by service providers with whom we have data processing agreements:
- Hetzner Online GmbH (Germany) — the server running the Service, the database, the mixer, moderation and visit statistics;
- Cloudflare, Inc. (USA, with data centres in the EU) — network traffic intermediation and attack protection, storage of recordings (Cloudflare R2), handling of incoming mail to [email protected];
- Resend (Plus Five Five, Inc., USA) — sending e-mail (sending servers in Ireland);
- Atlassian (Australia/USA) — the task system that receives bug reports;
- Wfirma sp. z o.o. (Poland) — the accounting system in which we issue invoices and keep our books;
- Stripe Payments Europe, Limited (Ireland) — payment processing. For payments, Stripe also acts as an independent controller (e.g. of card data and identity verification) — see the Stripe privacy policy;
- providers of libraries loaded by the panel (Tailwind Labs, jsDelivr, unpkg, Cloudflare cdnjs) — they receive the IP address and browser name when files are downloaded.
The platforms you stream to (Google/YouTube, Meta/Facebook, Twitch and others) are independent controllers: we send them your Stream together with its title and description, and we fetch chat and statistics from them. We also disclose data to public authorities when the law requires it.
We do not sell data and we do not share it with advertisers. The mixer, Guest connections, video moderation and visit statistics run on our own server, without third-party companies.
4. Transfers outside the European Economic Area
Some providers (Cloudflare, Resend, Atlassian, the platforms you stream to) are based in the USA or other countries outside the EEA. Transfers are based on the European Commission’s adequacy decision (EU-US Data Privacy Framework) for companies participating in that framework, or on standard contractual clauses approved by the Commission. You can obtain a copy of the safeguards by writing to us.
5. Data from Google and YouTube
- When you sign in with Google, we receive your Google account identifier, e-mail address, name and profile picture — we use them to create your Account and sign you in.
- When you connect a YouTube channel, we obtain access with the
youtubescope (manage your YouTube account). We use it only to create and start your live broadcasts, set their title, description and visibility, and fetch the chat and statistics of your broadcasts. We publish nothing without your action in the panel. - PirxStream’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use this data for advertising, do not sell it and do not let humans read it, except when you ask for technical support, when security requires it, or when the law requires it.
- Use of YouTube is subject to the YouTube Terms of Service and the Google Privacy Policy. You can revoke PirxStream’s access to your Google account in the panel or at myaccount.google.com/permissions — we then delete the access tokens.
6. Cookies, browser storage and visit statistics
- The website pirxstream.pl sets no cookies.
- The panel mix.pirxstream.pl sets only cookies strictly necessary for it to work, so we do not ask for consent to them:
zirael_session— keeping you signed in (up to 30 days from your last activity);zirael_oauth_csrf,oauth_popup,oauth_return_to— secure sign-in and account connection with Google, Facebook and Twitch (a few minutes);zirael_last_mix,zirael_theme— the last opened mixer and the chosen panel theme;pirx_lang,pirx_waluta— the chosen panel language and pricing currency (up to one year);zirael_share,zirael_payout_id— handling share links and returning from a Stripe payout.
- The mixer keeps interface settings in browser storage (localStorage), e.g. panel layout, keyboard shortcuts and the state of the audio mixer. This data does not leave your device.
- On payment pages a Stripe script runs that may set its own cookies to prevent fraud — the rules are described in Stripe’s cookie policy.
- Visit statistics are counted with our own tool (Umami) on our server. It stores no cookies or identifiers in the browser; it collects the address of the visited page, the referring page, the device and browser type, the language and the approximate country. Identifiers and tokens are removed from panel page addresses before sending. Basis: (f) — knowing how the website is used.
7. Deleting your Account
- When you delete your Account in the panel settings, you immediately lose access to it, all sign-in sessions are invalidated, and recordings are deleted according to the schedule in section 2.
- From the moment the Account is deleted, the remaining Account data is restricted: we keep it until permanent deletion and do not use it for any other purpose — in particular, we send no messages, and the e-mail address is removed from the Account immediately. We permanently delete it at your request sent to [email protected] — within 30 days of receiving it. Where the table in section 2 says “until the Account is deleted”, it means such permanent deletion. We do not delete data we must keep by law (invoices and accounting records), or data needed to establish, pursue or defend claims — until such claims are time-barred.
8. Your rights
You have the right to:
- access your data and receive a copy of it;
- rectification of inaccurate data;
- erasure of data (“the right to be forgotten”);
- restriction of processing;
- data portability for data we process on the basis of a contract or consent — in a commonly used format;
- object to processing based on our legitimate interest (basis (f));
- withdraw consent at any time, without affecting the lawfulness of processing before withdrawal;
- lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warsaw, Poland, uodo.gov.pl).
Right to object. You may at any time object, on grounds relating to your particular situation, to the processing of your data based on our legitimate interest (basis (f)). We then stop processing it for that purpose, unless we demonstrate compelling legitimate grounds that override your interests, or the data is needed to establish, pursue or defend claims. Objecting to onboarding tips always works — use the link in the message or write to us.
To exercise your rights, write to [email protected] from your Account’s e-mail address. We reply within one month. We may ask you to confirm your identity if the request comes from a different address.
9. Automated decisions
We do not make decisions about you based solely on automated processing that would produce legal effects or similarly significantly affect you. The moderation system only flags suspicious parts of the video — a human makes the decision. Hashes of technical data from sign-up may automatically flag an Account for review; a human decides whether to limit the trial.
10. Security
Connections to the Service are encrypted (HTTPS). We store passwords as argon2id hashes, and platform tokens and stream keys encrypted. Only people who need it to maintain the Service have access to the server and the database.
11. Changes to this policy
We announce material changes to this policy in advance by e-mail and in the panel. Changes to the list of providers in section 3 are announced at least 14 days before they take effect (Annex 2 to the Terms of Service, point 6). The current version is always available at pirxstream.pl/polityka-prywatnosci/ (Polish, binding) and pirxstream.pl/en/privacy-policy/ (English translation), with the version date at the top.