Privacy policy

02Who is responsible

The controller under the General Data Protection Regulation (GDPR) is PXStudio, owner Steffen Meurer, Wittener Bruch 42, 58453 Witten, Germany. Email: [email protected]. Further details are in our Imprint.

We have not appointed a data protection officer because we are not legally required to do so (Article 37 GDPR, section 38 of the German Federal Data Protection Act, BDSG). For all privacy matters, contact us at the address above.

This policy covers our website, the studio, hosted overlays and widgets, the chat bot PXStudioBot, account services and support.

03Our role and your stream

For our own purposes (accounts, billing, support, security, our website and our newsletter) we decide how data is processed and act as controller.

When you use PX Studio to show or process information about your viewers for your own stream, you decide which widgets, integrations and bot features run and what they show. For this processing you are the controller and we act as your processor under Article 28 GDPR. Where Article 28 applies, a data processing agreement is required; contact us to conclude it. You are responsible for having a lawful basis and for informing your viewers.

Platforms such as Twitch, Kick, Google/YouTube, TikTok, Discord and Ko-fi process data under their own responsibility and their own privacy notices.

04Hosting, server logs and security

Hosting: PX Studio runs on servers of IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany, in data centres in Germany. IONOS is our only hosting provider: the application, the database, uploads, backups (including the separate off-site backup copy) and our outgoing email run there. IONOS processes data on our behalf as our processor.

Server logs: Every request involves your IP address, the date and time, the requested address, the response status, the amount of data and, where your browser sends them, the referring page and browser information. Our application also logs errors and security events, which can contain account or request identifiers. We use this to deliver pages and overlays, keep sessions working, find faults, plan capacity and prevent misuse. Legal basis: Article 6(1)(b) GDPR where needed for the service you request, otherwise Article 6(1)(f) GDPR (our legitimate interest in secure and reliable operation). Short-lived rate limits can use IP addresses or account identifiers.

Email: We send emails (sign-in links, confirmations, acknowledgements and replies) through the mail servers of IONOS in Germany. The recipient address, the content and delivery information are processed for delivery.

Security: Connections are encrypted with HTTPS. We use access controls, hashed session and sign-in tokens, permission checks and logging of privileged access. This does not mean that every stored record is anonymised or encrypted, and no system is absolutely secure.

05Visiting our website

You can read our landing page, legal pages, status page and forms without an account. Besides the server logs described above, these pages set no cookies and store nothing on your device unless you sign in, use a form that needs it, save a privacy choice pick a light or dark theme in the docs (kept only in your browser) or move between docs pages, where the position of the docs navigation is kept for the current browser tab only. They load fonts, images and scripts only from our own server.

If you allow it, the landing page counts visits anonymously (see Website statistics). You can change your choice at any time with Privacy settings at the bottom of every page.

06Interactive demos on the landing page

The widgets you can try on the landing page use fictional sample data. Their state is kept only in the page's memory and is gone when you reload or leave. The demo badges and emotes are hosted by us; the demos do not connect to Twitch or other emote providers.

07Website statistics

Only if you allow Statistics under Privacy settings, a small script on the landing page reports that the page was viewed, how far it was scrolled (25, 50, 75 and 100 percent) and whether the sign-in or Discord buttons were used. We store only daily totals per event: a date, an event name and a count. We store no IP address, no identifier for you or your browser and no browsing history, and we cannot connect a count to a sign-in.

Legal basis: your consent under section 25(1) of the German Telecommunications Digital Services Data Protection Act (TDDDG), because the script reads information in your browser, and Article 6(1)(a) GDPR where personal data is involved in transmitting the request. If your browser sends a Do Not Track or Global Privacy Control signal, we do not ask and nothing is counted. You can withdraw your consent at any time under Privacy settings; this does not affect the lawfulness of counting before the withdrawal.

On the docs pages you can answer "Was this page helpful?". If you do, we add one to a daily total for that page and answer: a date, the page and yes or no. We store no IP address, no identifier and nothing on your device, and we skip it if your browser sends Do Not Track or Global Privacy Control. Legal basis: Article 6(1)(f) GDPR, our interest in improving the docs.

Separately, our server counts completed sign-ins and first beta activations as daily totals, without storing who signed in and without accessing your device. It skips this if your browser sends Do Not Track or Global Privacy Control. Legal basis: Article 6(1)(f) GDPR, our interest in understanding how the service is used.

08Account, sign-in and registration

You sign in with an emailed sign-in link or with your Twitch or Kick account. A sign-in link is valid for 15 minutes. Signing in with Twitch or Kick sends you to that platform, which then tells us your account ID, login name, display name and, where available, profile picture and email address. YouTube and Discord can be connected to an existing account but cannot be used to sign in.

When you create an account, we hold your verified sign-in details for up to 15 minutes while you review the Terms and confirm your age. When you agree, we store the Terms version, a fingerprint of its text and the time of acceptance to document the contract, and the time you confirmed that you are at least 16 years old. Accounts created before the age confirmation existed are asked once at their next sign-in; only then are their age confirmation and acceptance of the current Terms recorded.

Depending on the features you use, your account includes:

• profile, avatar and preferences, account creation and last activity;
• overlays, scenes, widget settings, custom code, layouts, notes, uploads, saved media and favourites;
• plan status, purchases, redeemed codes and beta access;
• team and moderator grants, API tokens, automations, webhook settings, Stream Deck connections and related activity records;
• connected channel identifiers, granted permissions and the access tokens needed to keep a connection working.

Legal basis: Article 6(1)(b) GDPR for providing your account and the features you use, and Article 6(1)(f) GDPR for access security and preventing misuse. An email address or a supported platform account is needed to create an account. Connections, uploads, API access and the newsletter are optional; without the related data, the related feature does not work.

09Connected platforms

When you connect a platform, you authorise PX Studio on that platform's own page. We then receive OAuth tokens: credentials that allow PX Studio to access the platform permissions you grant. We store them to keep the connection working. Connections can receive data from the platform and, depending on your settings, send data to it, for example chat replies or moderation actions of PXStudioBot. Disconnecting stops future use; it does not by itself delete events we already stored or content already published on the platform.

• Twitch and Kick: channel and stream information, followers, subscriptions and gifts, cheers or bits where supported, chat messages, roles, badges and moderation information. Twitch sends events to us through its EventSub service, Kick through webhooks: automatic notifications about channel events sent to PX Studio.
• YouTube (Google): channel identifiers and metadata, video and song information and, for bot features you switch on, live-chat messages and actions. PXStudioBot can read and send YouTube live-chat messages. These features use YouTube API Services; by using them you agree to the YouTube Terms of Service. Google's processing is explained in the Google Privacy Policy. You can revoke our access in your Google account permissions at any time.
• Ko-fi: connection details and the donation, membership or shop events Ko-fi sends to us, which can include supporter names, messages, amounts and currency.
• Discord: support tickets you open through our Discord server, including messages, attachments and transcripts, and your Discord user name if you link it to your studio account with a one-time code (only shown to our support team, never a way to sign in). Discord webhook automations send the message and event data you configure to the Discord server you choose.

Legal basis: Article 6(1)(b) GDPR for the connections you request. Viewer data follows the roles explained under Our role and your stream.

10Chat bot, moderation and viewer features

PXStudioBot can process chat messages, platform and channel IDs, viewer IDs and names, roles, command inputs, timestamps and the results of actions. Features you switch on can store moderation strikes and permits, giveaway entries and winners, loyalty balances and their history, rewards, song requests and queues, game participation, counters and usage totals.

Live chat is not stored as a full archive, but commands, moderation actions, giveaways and song requests can create lasting records. So that you can ask Pix about your chat, the last 200 messages of your channel (name, message, time, platform) are kept in memory and deleted one hour after the last message. Custom API commands, automation webhooks and external media addresses send the data you configure (for example a user name, channel, command arguments or search text) to the destinations you choose.

Bot filters can reply to messages or take moderation actions you configure; you choose these settings and remain responsible for them. We do not make decisions based solely on automated processing that have legal or similarly significant effects on you (Article 22 GDPR).

11Information about viewers and other people

Data about viewers, team members, people who send us reports and other people can come from account holders, connected platforms and their event services, chat, or support requests rather than from the person directly (Article 14 GDPR). It can include public user names and IDs, messages, roles, interactions, payment event amounts, content references and timestamps.

Overlays, alerts, leaderboards, giveaway results and chat replies can show this information to the creator's audience, and published streams and recordings can reach the public. Team members see account features according to their grants. Anyone who has an overlay or widget link can see what it shows, so keep these links private.

If a creator controls the processing, please contact that creator first. You can also contact us with enough detail to identify the channel or account, and we will help. For our own purposes, such as investigating a report or preventing misuse, the purposes and legal bases in this policy apply.

12GIFs, embedded players, emotes and other external content

Some studio and overlay features show content that is stored by other providers. When such content is shown, your browser or streaming software loads it directly from that provider, which receives your IP address, browser information and the requested address. The providers are responsible for their own processing, including any storage in the embedded player on your device. This content loads only in the studio and in overlays, when you or your overlay use the related feature; our website pages do not load it.

Legal basis: Article 6(1)(b) GDPR, because the content is part of the feature you use. Where you show such content to your viewers, the roles under Our role and your stream apply. Consider these connections when choosing media for your overlays.

13Payments and purchases

Stripe processes paid subscriptions and in-product purchases of widgets or bundles. Checkout and the billing portal are pages provided by Stripe; our website does not load Stripe scripts. We send Stripe a customer reference and the order or plan, and receive customer, subscription, payment and invoice references, status, amounts and related transaction details. We never receive your full card number.

Stripe processes payment details, billing details and fraud-prevention information under its own terms and privacy policy. Depending on the activity, Stripe acts as our processor or as an independent controller, for example for its own regulatory and fraud-prevention duties.

If you redeem a code bought on Etsy or another marketplace, we receive only the code and store the resulting entitlement; the marketplace handles its own checkout and data.

Legal basis: Article 6(1)(b) GDPR for purchases and subscriptions, Article 6(1)(c) GDPR for tax and accounting duties and Article 6(1)(f) GDPR for preventing payment fraud and handling claims.

14Contact, consumer requests and reports

• Contact form: your name, email address, subject and message. The form does not accept attachments. We send your message by email to our mailbox and do not store it in our database. If you email us directly, we process your message, any attachments and your contact details.
• Withdrawal: your name, email address and contract details, the time of receipt, your account if you are signed in, your IP address and browser information.
• Cancellation without signing in: your name, confirmation email, contract details, type of cancellation, requested end date and reason if given, the time of receipt, a submission reference and whether the acknowledgement was sent.
• Cancellation in your account: your account, email address, current plan, reason if given, time and IP address.
• Content reports: your name and email (optional for reports about child sexual abuse), the location and description of the content, the stated legal grounds, your good-faith declaration, whether the report concerns child safety, your account if you are signed in, your IP address and browser information.

We use these data to answer you, fulfil consumer and hosting-service duties, handle reports and document outcomes. Legal basis: Article 6(1)(b) GDPR, Article 6(1)(c) GDPR where a legal duty applies (for example acknowledging withdrawals, cancellations and reports) and Article 6(1)(f) GDPR for handling requests properly, preventing misuse and defending legal claims. Where necessary and lawful, we can share relevant information with the affected account holder, legal advisers or authorities. We do not publish a reporter's contact details.

Authorised staff can look at account information to solve a problem you report, for example configurations, connections, entitlements and diagnostic events. Support views hide sensitive information such as connection tokens, and privileged access is logged. Discord support tickets are also kept as transcripts in our Discord server; deleting a studio account does not delete that copy.

15Newsletter

With your consent, we send product and launch updates by email. We use double opt-in: the subscription starts only after you confirm the link we send. We store your email address, an optional plan preference, the time of sign-up and confirmation, the IP address at consent and your subscription status. Legal basis: Article 6(1)(a) GDPR.

You can unsubscribe with the link in every newsletter or by email. Withdrawing consent does not affect earlier processing. We keep a record of the unsubscription and the evidence of consent as needed to respect your choice and prove compliance (Article 6(1)(c) and (f) GDPR). The newsletter is independent of a studio account; deleting your account does not unsubscribe you.

16AI features and speech synthesis

AI features run only when you switch them on and use them:

• Pix, the assistant in the studio and the docs, runs through Anthropic (Claude). Your question, the recent conversation and, inside the studio, the overlay data Pix looks up for your request are sent to create the answer; this can include names and messages of viewers. If you connected OBS in the editor and ask Pix about your stream, performance values and output settings from your OBS (for example CPU load, frame rate, dropped frames, bitrate, resolution, encoder and the settings of PX Studio browser sources) are sent too; never your stream key, stream server or passwords. We do not keep the text of your questions.
• Speech synthesis runs either on our own server or, depending on the voice you choose, through xAI or OpenRouter (which passes the request to the model provider of the chosen voice). The text is sent to create the audio and can include viewer messages, names or other information shown in a widget. To avoid creating the same audio twice, we keep generated audio in a size-limited cache on our server; the oldest entries are removed first.

Do not put sensitive information or confidential third-party content into these features. Legal basis: Article 6(1)(b) GDPR. Where you process viewer information for your own stream, you need your own legal basis. The providers can process data outside the EU; see International transfers.

17Cookies and storage on your device

We store information on your device or read it from there only where this is strictly necessary for a service you have requested (section 25(2) no. 2 TDDDG) or where you have consented (section 25(1) TDDDG). We use no advertising or third-party analytics cookies. The cookies below are first-party cookies of pxstudio.cloud.

Your privacy choice: when you save a choice under Privacy settings, we store it in your browser's local storage (px_consent) for 12 months, so we do not ask again on every visit.

In the studio and in overlays we use your browser's local and session storage to remember settings you make and the state of the editor: for example language, keyboard shortcuts, recently opened overlays, panel positions and sizes, view options, copied layers, recent colours and emotes, chat panel tabs and filters (which can contain channel or user names), Stream Deck buttons, dismissed hints and, if you save it, your OBS connection including its password. Previews of widgets can keep their own widget data. This information stays on your device until you or the studio remove it. It is strictly necessary to provide the studio features you use.

Consent-based: the anonymous visit count on the landing page (see Website statistics) runs only after you allow Statistics under Privacy settings.

You can delete cookies and site data in your browser at any time. Without the necessary cookies, sign-in and some features do not work.

18Account statistics and service operation

To run the studio and show you your own statistics, we use account-linked information such as last sign-in and activity, beta and plan status, billing events, feature use and channel statistics. We also use it to understand how features are adopted and how reliable the service is. These records are separate from the anonymous website totals and are not used for advertising.

Legal basis: Article 6(1)(b) GDPR for statistics you request and Article 6(1)(f) GDPR for proportionate analysis to operate and improve the service.

19Recipients

Only people and providers who need the data for the purposes above receive it:

• authorised members of our team;
• IONOS SE (Germany) as our processor for hosting, backups and email;
• Stripe for payments;
• Anthropic for the Pix assistant;
• xAI, OpenRouter and the model provider it selects, for AI voices you use;
• Klipy for GIF and sticker search;
• the platforms and content providers you connect or whose content you use: Twitch, Kick, Google/YouTube, TikTok, Discord, Ko-fi, 7TV, BetterTTV, FrankerFaceZ and, if switched on, pronouns.alejo.io;
• recipients you configure yourself, for example webhook destinations or team members;
• legal advisers, courts or authorities where this is necessary and lawful.

20International transfers

Our hosting and email stay in Germany. Some providers above are based in or process data in countries outside the EU and EEA, in particular the United States (for example Stripe, Anthropic, xAI, OpenRouter, Google, Twitch and Discord). Which entity and country apply depends on the provider and the feature.

We transfer personal data to such countries only on a legal basis under Chapter V GDPR: an adequacy decision of the European Commission (for the United States, the EU-U.S. Data Privacy Framework for companies certified under it) or appropriate safeguards such as the EU standard contractual clauses. When you connect a platform or use its content, you ask us to exchange data with that platform so we can provide the feature. Ask us at [email protected] which safeguard applies to a provider and how to get a copy.

21How long we keep data

We keep personal data only as long as needed for the purpose, then delete or anonymise it, unless a legal duty or a pending claim requires us to keep it longer.

• Account and studio data: for as long as your account exists. When you delete your account, we delete its studio records and uploads; data we must keep for legal reasons is kept separately.
• Sign-in: sign-in links expire after 15 minutes, pending registrations after 15 minutes, sign-in protection cookies after 5 or 10 minutes and sessions after 90 days without use. Expired records are removed by regular clean-up.
• Stream events: removed once they are older than 30 days and not among the newest 2,000 events of the account, so the newest 2,000 can stay longer. Daily statistics and bot records are separate and are not covered by this rule.
• Bot records: loyalty histories, giveaways, song queues, game and moderation records stay until the feature, a clean-up or the deletion of your account removes them. Short-lived permits and strikes expire on their own.
• Generated speech audio: in a size-limited cache; the oldest entries are removed first.
• Newsletter: while you are subscribed. Unconfirmed sign-ups are deleted once the confirmation link is more than 30 days old. The unsubscription record and consent evidence are kept as long as needed to prove compliance.
• Contact, consumer requests, reports and support: as long as needed to handle the matter and any follow-up, and then until the relevant limitation periods end (generally three years from the end of the year, section 195 BGB).
• Accounting and tax records: for the statutory periods, generally eight years for invoices and accounting vouchers and ten years for books and annual accounts (section 147 of the German Tax Code, section 257 of the German Commercial Code), and six years for relevant business letters.
• Server logs: rotated automatically and kept only as long as needed for security and fault finding; entries related to a security incident can be kept until it is resolved.
• Backups: rolling backups, normally kept for 14 days. Deleted data can remain in a backup until that backup is replaced.
• Data in your browser: until you delete it or it expires as described under Cookies and storage on your device.

22Your rights

Under the GDPR you have the right of access (Article 15), rectification (Article 16), erasure (Article 17), restriction of processing (Article 18) and data portability (Article 20). You can withdraw consent at any time with effect for the future (Article 7(3)), for example under Privacy settings or with the unsubscribe link.

Right to object (Article 21 GDPR): Where we process data on the basis of legitimate interests (Article 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation. We then stop, unless we can show compelling legitimate grounds that override your interests, or the processing serves legal claims. You can object to direct marketing at any time without giving reasons.

In your account settings you can use Download my data and Delete account. The export leaves out sign-in secrets but does not limit your right to ask for other data. Self-service deletion is not available while a paid subscription is still active; contact us and we will handle cancellation and deletion. Some records need separate handling, for example payment records at Stripe, newsletter entries and Discord transcripts.

Send requests to [email protected]. We may ask for information to confirm your identity. We answer within one month; for complex requests this can be extended by two further months, in which case we tell you why within the first month.

You can also complain to a data protection supervisory authority, in particular in the member state where you live or work or where the alleged infringement took place. The authority responsible for us is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), Kavalleriestraße 2-4, 40213 Düsseldorf, Germany.

23Minimum age and changes to this policy

PX Studio is intended for people aged 16 or older, as set out in our Terms of service. We ask you to confirm this before an account is created or, for older accounts, at the next sign-in, and we store the time of that confirmation. We do not ask for your date of birth or an ID. If you believe that we process a child's data unlawfully, contact us.

We update this policy when our processing changes. The date at the top shows the current version. If a change needs your consent, we ask for it before the new processing starts.